linux-kernel - Re: linux-next: Tree for January 15 (Call Trace in fs/dcache.c + autofs4)

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] [day] [month] [year] [list]

Message-ID: <AANLkTim00wGO3eMs4bF8rmCJ8aVcd5Png9zzyus4gjd1@mail.gmail.com>
Date:	Sat, 15 Jan 2011 14:50:09 +0100
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	Al Viro <viro@...iv.linux.org.uk>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: linux-next: Tree for January 15 (Call Trace in fs/dcache.c + autofs4)

On Sat, Jan 15, 2011 at 12:44 PM, Sedat Dilek
<sedat.dilek@...glemail.com> wrote:
> On Sat, Jan 15, 2011 at 12:34 PM, Al Viro <viro@...iv.linux.org.uk> wrote:
>> On Sat, Jan 15, 2011 at 12:16:29PM +0100, Sedat Dilek wrote:
>>
>>> Which version do you mean by "mainline"? 2.6.37-git12?
>>> And with "[mismerge][foldme] breakage in __do_follow_link()" patch [1]?
>>> I have to look by pulling-in(to) Linus-tree (linux-next) which patches
>>> are not merged already.
>>
>> -git12 would do.  Without any extra patches.  Can you reproduce the
>> ext3 oops on that alone?
>>
>
> Just a short answer (on the go... weekend shopping)...
> Currently, I am on a lame IBM T40p (Pentium-M) and doing a "full" build.
> Unfortunately, I started a next linux-next build with the two patches
> from vfs-2.6#for-next.
> When I return I will try this kernel.
> If things aren't OK, I do a mainline build afterwards (w/o any patches).
>
> - Sedat -
>

root@...x:~# dmesg | grep -i 'error|fail|warn|trace'

WOW, zero... NULL... nada... njet...

Even the ACPI warnings are gone (bye-bye warnings):

[    0.000000] ACPI Warning: 32/64X length mismatch in Gpe1Block: 0/32
(20100428/tbfadt-526)
[    0.000000] ACPI Warning: Optional field Gpe1Block has zero address
or length: 0x000000000000102C/0x0 (20100428/tbfadt-557)

update-grub looks also fine (see attached file), now.

Al, you want me still to build a 2.6.37-git12 kernel?

- Sedat -

View attachment "update-grub_vfs-26-for-next.txt" of type "text/plain" (77663 bytes)