linux-kernel - Re: 2.6.34.1+hacks: kernel deadlock related to file-IO?

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: <20100727231427.1f3eb97b@nehalam>
Date:	Tue, 27 Jul 2010 23:14:27 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Ben Greear <greearb@...delatech.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.34.1+hacks:  kernel deadlock related to file-IO?

On Tue, 27 Jul 2010 17:14:53 -0700
Ben Greear <greearb@...delatech.com> wrote:

> On 07/27/2010 04:51 PM, Stephen Hemminger wrote:
> > On Tue, 27 Jul 2010 16:11:47 -0700
> > Ben Greear<greearb@...delatech.com>  wrote:
> >
> >> NOTE:  This is from a hacked 2.6.34.1 kernel, with
> >> a module of my own devising loaded and in active use.
> >
> > Ben please don't ask LKML for help with problems when
> > you have a binary only module loaded...
> 
> Yeah, I know..but I spent all day hacking .34 enough to
> run lockdep and get those backtraces..and they *might* be
> valid.  There's a small chance someone else has seen similar
> things but not reported it for whatever reason, so maybe
> they will chime in.
> 
> And finally, I will attempt to reproduce with some official
> kernels, and will report what I find one way or another.
> 
> The .34 kernel has been a real bitch to get stable  (You
> know things must be bad when my name's on -stable patches),
> so I wouldn't be surprised if I'm hitting another real bug.

Understand your pain. The hardest problem is often finding a reproducible case.
If the problem is not reproducible it is hard to add trace info
or use bisection.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/