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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120223.150846.2241731542881529513.davem@davemloft.net>
Date:	Thu, 23 Feb 2012 15:08:46 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	romieu@...zoreil.com
Cc:	sbhatewara@...are.com, jongman.heo@...sung.com,
	netdev@...r.kernel.org, scottjg@...are.com, pv-drivers@...are.com
Subject: Re: WARNING: at kernel/softirq.c:159
 _local_bh_enable_ip+0x35/0x71()

From: Francois Romieu <romieu@...zoreil.com>
Date: Thu, 23 Feb 2012 11:42:37 +0100

> 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.

Right, lying about the transport header size is going to give you nothing
but trouble, you absolutely cannot do this or networking breaks, and your
transmit handler doesn't run in a context where you can legally "fix"
things up.

We recently fixed even IPoIB in this regard.
--
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