netdev - Re: [PANIC] lro + iscsi or lro + skb text search causes panic

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]

Date:	Tue, 27 Jan 2009 14:01:56 +1100
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
Cc:	David Miller <davem@...emloft.net>,
	"michaelc@...wisc.edu" <michaelc@...wisc.edu>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"tgraf@...g.ch" <tgraf@...g.ch>, "kkeil@...e.de" <kkeil@...e.de>
Subject: Re: [PANIC] lro + iscsi or lro + skb text search causes panic

On Mon, Jan 26, 2009 at 05:40:08PM -0800, Brandeburg, Jesse wrote:
>
> 1-3 (both, :-)) doesn't seem to work here, I applied this and still got a 
> panic when doing a quick test before I went home today.
> 
> I can get panic trace from netconsole tomorrow.

OK, looking at the original trace it looks like none of the bugs
I've fixed actually explain it.  The crash looks more like a ref
count bug, which means that the issue isn't so much about the
skb_seq_read interface (which should be fixed in any case), but
in the iSCSI code itself.

More digging is required.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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