linux-kernel - Re: [xfs-masters] Re: 2.6.18-rc6-mm2

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: <20060914204801.e37a112b.akpm@osdl.org>
Date:	Thu, 14 Sep 2006 20:48:01 -0700
From:	Andrew Morton <akpm@...l.org>
To:	David Chinner <dgc@....com>
Cc:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	linux-kernel@...r.kernel.org, xfs-masters@....sgi.com,
	Linus Torvalds <torvalds@...l.org>
Subject: Re: [xfs-masters] Re: 2.6.18-rc6-mm2

On Fri, 15 Sep 2006 12:57:45 +1000
David Chinner <dgc@....com> wrote:

> On Thu, Sep 14, 2006 at 07:01:38PM +0200, Michal Piotrowski wrote:
> > >>
> > >> I'll build system with gcc 3.4
> > >
> > >It's not a compiler issue.
> > >
> > >Binary search should solve this mystery.
> > 
> > I was wrong - it's in vanilla tree
> > (http://www.stardust.webpages.pl/files/mm/2.6.18-rc6-mm2/mm-dmesg1).
> > 
> > cat hunt | head -n 3
> > origin.patch
> > BAD
> > libata-ignore-cfa-signature-while-sanity-checking-an-atapi-device.patch
> 
> Not sure what this means....

"BAD" is a bisection point, as per
http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt.  So
just 2.6.18-rc6+origin.patch exhibits the failure.  That is mainline.

> > I can reproduce this bug with all CONFIG_DEBUG_*=y.
> > (only
> > CONFIG_DEBUG_SYNCHRO_TEST=m
> > CONFIG_RCU_TORTURE_TEST=m
> > as modules)
> 
> I notice you're running i386 with 4k stacks - I wonder if you're blowing the
> stack by running xfs on loopback. I've been testing on x86_64 and ia64
> which don't have those issues. Can you try with 8K stacks instead of
> 4k stacks?

hm, that wouldn't be good.

Enabling CONFIG_DEBUG_STACK_USAGE will make the fourth column in the
sysrq-T output display the minimum-ever free stack space for each task.

sleep         S ffff810100f0bea8     0 18893  22372                     (NOTLB)

                                     ^ this number.
-
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/