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  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:	Wed, 25 Apr 2007 11:52:52 +0300
From:	Ismail Dönmez <>
To:	Thomas Graf <>
Cc:	David Miller <>,
Subject: Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e

On Tuesday 24 April 2007 00:23:13 Ismail Dönmez wrote:
> On Tuesday 24 April 2007 00:17:40 Thomas Graf wrote:
> > * Ismail D?nmez <> 2007-04-23 22:09
> >
> > > Yes I know the fix is in but I wondered why its creating such problems
> > > with 2.6.18 kernel, guess it depends on some other commits.
> >
> > As long as you apply the complete patch including the additional
> > sanity check for RTN_MAX it should work perfectly fine on 2.6.18.
> The sanity check part doesn't seem to apply to 2.6.18.
> > I can't think of any connection between the patch and the errors
> > you are seeing.
> >
> > Are you absolutely sure the errors you see are directly connected
> > to applying the patch?
> Yes actually I am but I'll re-test and see. Thanks.

I was able to reproduce the same problem with Linus' GIT tree too. Since I 
started to see these after I applied the commit 
a0ee18b9b7d3847976c6fb315c06a34fb296de0e to 2.6.18 tree, there is a big 
possiblity that the commit is the culprit.

I attach the relevant dmesg messages. Problem happened after 12 hours of 
uptime and and net connection gets stable again after 1-2 minutes.


Life is a game, and if you aren't in it to win,
what the heck are you still doing here?

-- Linus Torvalds (talking about open source development)

View attachment "dmesg.txt" of type "text/plain" (1349 bytes)

Powered by blists - more mailing lists