linux-kernel - Re: [BUG] linux-next: 20141127 boot hang

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: <20141129214448.625baea8@canb.auug.org.au>
Date:	Sat, 29 Nov 2014 21:44:48 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Jeremiah Mahler <jmmahler@...il.com>
Cc:	linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk>,
	Theodore Ts'o <tytso@....edu>,
	Christoph Hellwig <hch@...radead.org>,
	linux-fsdevel@...r.kernel.org, Tejun Heo <tj@...nel.org>
Subject: Re: [BUG] linux-next: 20141127 boot hang

Hi Jeremiah,

On Sat, 29 Nov 2014 01:15:10 -0800 Jeremiah Mahler <jmmahler@...il.com> wrote:
>
> all,
> 
> On Fri, Nov 28, 2014 at 03:32:50PM -0800, Jeremiah Mahler wrote:
> > On Thu, Nov 27, 2014 at 03:16:19PM -0800, Jeremiah Mahler wrote:
> > > 
> > > I just tried the latest linux-next 20141127 (commit 3bcf494d225fd19) and
> > > it hangs very early in the boot sequence, after decompressing the kernel
> > > and after fsck (see attached screen shot).  I have tried it with two
> > > different machines and they both have the same problem.  It worked with
> > > version 20141126.
> > > 
> > []
> > 
> > My bisect results so far indicate that the bug was introduced by this
> > merge commit.
> > 
> >   commit 0305904a7416ced1358c5ff575e58135453bfc1d
> >   Merge: 38a4751 2ef5864
> >   Author: Stephen Rothwell <sfr@...b.auug.org.au>
> >   Date:   Thu Nov 27 14:53:44 2014 +1100
> >   
> >       Merge remote-tracking branch 'block/for-next'
> >       
> >       Conflicts:
> >           fs/fs-writeback.c
> > 
> []
> 
> Something is definitely broken at this merge commit.  I haven't
> quite figured out how to bisect the patches inside the merge commit.
> Any suggestions are welcome.

It could easily actually be the merge itself. There was a conflict in
that merge that I fixed up as best I could and asked others to check
the resolution.

I know that Cristoph thinks that the lazytime stuff is not ready for
-next yet, but are there any other comments?

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped