netdev - Re: WARNING: at kernel/softirq.c:159 _local_bh_enable

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]

Message-ID: <1879896900.614230.1330503539675.JavaMail.root@zimbra-prod-mbox-5.vmware.com>
Date:	Wed, 29 Feb 2012 00:18:59 -0800 (PST)
From:	Shreyas Bhatewara <sbhatewara@...are.com>
To:	Francois Romieu <romieu@...zoreil.com>
Cc:	Jongman Heo <jongman.heo@...sung.com>, netdev@...r.kernel.org,
	"Scott J. Goldman" <scottjg@...are.com>,
	VMware PV-Drivers <pv-drivers@...are.com>
Subject: Re: WARNING: at kernel/softirq.c:159
 _local_bh_enable_ip+0x35/0x71()



----- Original Message -----
> (Heo, your mua broke threading)
> 
> Jongman Heo <jongman.heo@...sung.com> :
> > Francois Romieu<romieu@...zoreil.com>
> > > > Jongman Heo <jongman.heo@...sung.com> :
> > > > Following warning triggered with my VMware Linux guest, when
> > > > NFS connection is requested from outside.
> > > 
> > > I'd try reverting 39d4a96fd7d2926e46151adbd18b810aeeea8ec0.
> [...]
> > I confirm that reverting the commit fixes the warning.
> 
> Shreyas, can you provide a proper fix for this bug (see
> http://www.spinics.net/lists/netdev/msg189554.html for details).
> 
> As far as I understand it you can not claim a fake transport layer
> header
> size for udp and blindly check the available buffer size through
> pskb_may_pull later. With a 32 bits HIGHMEM guest config (yuck...) it
> ends
> up enabling bh within a network device start_xmit context.
> 
> --
> Ueimor
> 

Just sent a patch to fix the transport header size.

Thanks.
Shreyas
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html