From: Rami Rosen <rami.rosen@intel.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com,
ronen.arad@intel.com, Rami Rosen <rami.rosen@intel.com>
Subject: [PATCH net-next] bridge: Fix setting a flag in br_fill_ifvlaninfo_range().
Date: Fri, 15 May 2015 17:27:27 +0300 [thread overview]
Message-ID: <1431700047-22560-1-git-send-email-rami.rosen@intel.com> (raw)
This patch fixes setting of vinfo.flags in the br_fill_ifvlaninfo_range(). The
assignment of vinfo.flags &= ~BRIDGE_VLAN_INFO_RANGE_BEGIN has no effect without
this patch, as vinfo.flags value is overriden by the
vinfo.flags = flags | BRIDGE_VLAN_INFO_RANGE_END assignement, which follows
it immedialtely.
Signed-off-by: Rami Rosen <rami.rosen@intel.com>
---
net/bridge/br_netlink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/bridge/br_netlink.c b/net/bridge/br_netlink.c
index 6b67ed3..fec65bb 100644
--- a/net/bridge/br_netlink.c
+++ b/net/bridge/br_netlink.c
@@ -167,7 +167,7 @@ static int br_fill_ifvlaninfo_range(struct sk_buff *skb, u16 vid_start,
vinfo.flags &= ~BRIDGE_VLAN_INFO_RANGE_BEGIN;
vinfo.vid = vid_end;
- vinfo.flags = flags | BRIDGE_VLAN_INFO_RANGE_END;
+ vinfo.flags &= flags | BRIDGE_VLAN_INFO_RANGE_END;
if (nla_put(skb, IFLA_BRIDGE_VLAN_INFO,
sizeof(vinfo), &vinfo))
goto nla_put_failure;
--
1.9.3
next reply other threads:[~2015-05-15 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 14:27 Rami Rosen [this message]
2015-05-15 18:45 ` [PATCH net-next] bridge: Fix setting a flag in br_fill_ifvlaninfo_range() Arad, Ronen
2015-05-15 19:11 ` roopa
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=1431700047-22560-1-git-send-email-rami.rosen@intel.com \
--to=rami.rosen@intel.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ronen.arad@intel.com \
--cc=roopa@cumulusnetworks.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;
as well as URLs for NNTP newsgroup(s).