This is a note to let you know that I've just added the patch titled
netpoll: netpoll_poll_dev() should access dev->flags
to the 3.2-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
netpoll-netpoll_poll_dev-should-access-dev-flags.patch
and it can be found in the queue-3.2 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 16d7c5c85644e3646505c7d5b1f109b577ff89fc Mon Sep 17 00:00:00 2001
From: Eric Dumazet <[email protected]>
Date: Tue, 14 Feb 2012 10:11:59 +0000
Subject: netpoll: netpoll_poll_dev() should access dev->flags
From: Eric Dumazet <[email protected]>
[ Upstream commit 58e05f357a039a94aa36475f8c110256f693a239 ]
commit 5a698af53f (bond: service netpoll arp queue on master device)
tested IFF_SLAVE flag against dev->priv_flags instead of dev->flags
Signed-off-by: Eric Dumazet <[email protected]>
Cc: WANG Cong <[email protected]>
Acked-by: Neil Horman <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
net/core/netpoll.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/net/core/netpoll.c
+++ b/net/core/netpoll.c
@@ -194,7 +194,7 @@ static void netpoll_poll_dev(struct net_
poll_napi(dev);
- if (dev->priv_flags & IFF_SLAVE) {
+ if (dev->flags & IFF_SLAVE) {
if (dev->npinfo) {
struct net_device *bond_dev = dev->master;
struct sk_buff *skb;
Patches currently in stable-queue which might be from [email protected] are
queue-3.2/gro-more-generic-l2-header-check.patch
queue-3.2/netpoll-netpoll_poll_dev-should-access-dev-flags.patch
queue-3.2/3c59x-shorten-timer-period-for-slave-devices.patch
queue-3.2/ipv4-reset-flowi-parameters-on-route-connect.patch
queue-3.2/tcp_v4_send_reset-binding-oif-to-iif-in-no-sock-case.patch
queue-3.2/net_sched-bug-in-netem-reordering.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
