netdev - Re: Oops in tun: bisected to Limit amount of queued packets per device

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: <m2ws9c2zs7.fsf@igel.home>
Date:	Wed, 22 Apr 2009 22:34:32 +0200
From:	Andreas Schwab <schwab@...ux-m68k.org>
To:	Herbert Xu <herbert@...dor.apana.org.au>
Cc:	Christian Borntraeger <borntraeger@...ibm.com>,
	"David S. Miller" <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: Oops in tun: bisected to  Limit amount of queued packets per device

Herbert Xu <herbert@...dor.apana.org.au> writes:

> On Thu, Apr 09, 2009 at 09:52:01AM +0200, Christian Borntraeger wrote:
>> 
>> with my kvm test scenario on s390 I get the following oops:
>> Unable to handle kernel pointer dereference at virtual kernel address 0000000400000000
>> Oops: 003b [#1] SMP
>> Modules linked in: kvm dm_multipath sunrpc qeth_l2 dm_mod qeth ccwgroup
>> CPU: 0 Not tainted 2.6.29-kvm-06607-ga317a1e-dirty #8
>> Process kuli (pid: 14827, task: 00000000b3df8138, ksp: 00000000b4703a98)
>> Krnl PSW : 0404e00180000000 0000000000171278 (__lock_acquire+0x3d4/0x191c)
>
> This is weird.  It looks like it's dying on the wake_up_interruptible_sync
> in tun_sock_write_space.  However, I can't see how that can cause this.

Any news on this?  It is still badly broken in 2.6.30-rc3.

Andreas.

-- 
Andreas Schwab, schwab@...ux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
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