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  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:	Sun, 23 Dec 2012 14:19:56 +0100
From:	Sedat Dilek <>
To:	Borislav Petkov <>,
	Sedat Dilek <>,,
	LKML <>,
	David Miller <>
Subject: Re: [3.8-rc1] Networking problems after pulling-in net.git#master

On Sun, Dec 23, 2012 at 1:40 PM, Sedat Dilek <> wrote:
> On Sun, Dec 23, 2012 at 1:26 PM, Sedat Dilek <> wrote:
>> On Sun, Dec 23, 2012 at 12:42 PM, Borislav Petkov <> wrote:
>>> On Sun, Dec 23, 2012 at 04:14:39AM +0100, Sedat Dilek wrote:
>>>> Hi,
>>>> after reading the thread "Regression in 3.8-rc1: "BUG: sleeping
>>>> function called from invalid context"" [1] I decided to pull-in
>>>> net.git#master (up to commit 9b1536c490d5: "bridge: call
>>>> br_netpoll_disable in br_add_if") on top of Linus upstream.
>>>> With this kernel I can't neither ping my router nor does DNS work.
>>>> IIRC there were 6 commits, not sure which of them is culprit.
>>>> I tried the v3.8-rc1-raring from [2] which works nicely here on
>>>> Ubuntu/precise AMD64.
>>>> Can't say if NetworkManager is involved or not.
>>> Does that mean that with Linus upstream, i.e. 3.8-rc1, you can ping your
>>> router, etc?
>>> If so, you could bisect the 6 commits...
>> Nah, he said that b-word :-).
>> The machine I am working on has some hardware damage (keyboard gets
>> not detected on bios start or even within daily-work, recently I could
>> not type further while writing an email, so raping that machine is not
>> a good idea. I could bisect within a reduced localmodconfig setup. No
>> big promises...)
> Starting bisect session with a "localmodconfig" setup... (bad: last
> commit and good: v3.8-rc1)...

The culprit commit here seems to be...

commit 9650388b5c56578fdccc79c57a8c82fb92b8e7f1
Author: Eric Dumazet <>
Date:   Fri Dec 21 07:32:10 2012 +0000

    ipv4: arp: fix a lockdep splat in arp_solicit()

...see also attached git-bisect log-files.

For the sake of completeness I have attached also my kernel-config
file and an output of lspci.

While my last steps of bisecting I also hit a MEI problem on restart,
I have seen a fix "[PATCH] mei: fix mismatch in mutex unlock-lock in
mei_amthif_read()" for this on LKML [1].

Hope this helps you to track down the problem.

Feel free to add any credits...

- Sedat -


> - Sedat -
> [1]
> [2]
>> - Sedat -
>>> Thanks.
>>> --
>>> Regards/Gruss,
>>>     Boris.
>>> Sent from a fat crate under my desk. Formatting is fine.
>>> --

View attachment "git-bisect-log.txt" of type "text/plain" (739 bytes)

View attachment "git-bisect-view--stat.txt" of type "text/plain" (4611 bytes)

View attachment "git-bisect-visualize.txt" of type "text/plain" (4529 bytes)

Download attachment "dot-config_localmodconfig" of type "application/octet-stream" (107837 bytes)

View attachment "lspci-nnvv.txt" of type "text/plain" (24708 bytes)

Powered by blists - more mailing lists