linux-kernel - Re: [BUG-rc8]: Kernel bootprocess

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]

Date:	Thu, 3 Sep 2009 13:52:46 +0530
From:	Tej <bewith.tej@...il.com>
To:	Frans Pop <elendil@...net.nl>
Cc:	linux-kernel@...r.kernel.org, ebiederm@...ssion.com
Subject: Re: [BUG-rc8]: Kernel bootprocess

On Wed, Sep 2, 2009 at 8:06 PM, Frans Pop<elendil@...net.nl> wrote:
> Tej wrote:
>> Recently upgraded to 2.6.3-rc8. While doing I could not able to boot,
>> and boot process stop at dmesg saying something:
>> ADDR_CONF (NETDEV CHANGE): eth0 interface become ready.
>>
>> message seems success only but affter pressing alt+ctl+del. machine
>> boot without xserver and complete / with readonly filesystem. So I
>> couldn't capture whole dmesg.
>>
>> Now: I have bisected the problem (twice), and bisect result goes to
>> 0db501bd0610ee0c0aca84d927f90bcccd09e2bd is first bad commit
>> Author: Eric W. Biederman <ebiederm@...ssion.com>
>>     inotify: Ensure we alwasy write the terminating NULL.
>
> Can you try with the current git mainline, or current snapshot kernel?
> There have been a couple of inotify fixes committed since rc8.

It Worked Properly.
Last Commit Pulled: 37d0892c5a94e208cf863e3b7bac014edee4346d

thanks,

>
> Cheers,
> FJP
>
--
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/