From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH common 1/2] fix #2831: never set bridge_fd to 0 with STP on
Date: Fri, 16 Jul 2021 12:54:43 +0200 [thread overview]
Message-ID: <54f874cb-063e-75b2-2a9e-4e6629ceff1a@proxmox.com> (raw)
In-Reply-To: <20210716074050.3981444-1-f.gruenbichler@proxmox.com>
On 16.07.21 09:40, Fabian Grünbichler wrote:
> it's an invalid combination that causes the network reload/setup to
> fail. unfortunately, this is not caught by ifupdown2 itself, but only
> rejected by the kernel with ERANGE over netlink.
>
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
>
> Notes:
> these range checks are there in the kernel since 2011..
>
> src/PVE/INotify.pm | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
>
applied, thanks!
prev parent reply other threads:[~2021-07-16 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 7:40 [pve-devel] " Fabian Grünbichler
2021-07-16 7:40 ` [pve-devel] [PATCH common 2/2] interfaces: improve bridge_fd handling Fabian Grünbichler
2021-07-16 10:56 ` Thomas Lamprecht
2021-07-16 10:54 ` Thomas Lamprecht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54f874cb-063e-75b2-2a9e-4e6629ceff1a@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.gruenbichler@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox