linux-kernel - Re: [PATCH] 2.6.19-rc4 - netlink messages created with bad flags in soft

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 1 Nov 2006 08:10:25 -0500
From:	Andy Gospodarek <andy@...yhouse.net>
To:	David Miller <davem@...emloft.net>
Cc:	andy@...yhouse.net, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org
Subject: Re: [PATCH] 2.6.19-rc4 - netlink messages created with bad flags in soft_irq context

On Tue, Oct 31, 2006 at 10:00:47PM -0800, David Miller wrote:
> From: Andy Gospodarek <andy@...yhouse.net>
> Date: Tue, 31 Oct 2006 17:06:00 -0500
> 
> > I've got a kernel built where 
> > 
> > CONFIG_DEBUG_SPINLOCK_SLEEP=y
> > 
> > is in the config and I've noticed some interesting behavior when
> > bringing up bonds in balance-alb mode.  When I start to enslave devices
> > to a bond I get the following in the ring buffer:
> > 
> > BUG: sleeping function called from invalid context at mm/slab.c:3007
> > in_atomic():1, irqs_disabled():0
> 
> As Herbert mentioned, the bonding layer calls into the networking
> in atomic contexts when that is illegal.
> -

Thanks for the feedback.  If it seems the bonding driver is one of the
only culprits, I'll investigate a solution that is specific to bonding
(maybe a workqueue for such calls...) rather that one that effects the
entire stack.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/