Re: linux-next: Tree for Jan 20 -- Kernel panic - Unable to mount root fs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2015-01-20, 21:58:31 +0000, Al Viro wrote:
> On Tue, Jan 20, 2015 at 10:38:58PM +0100, Sabrina Dubroca wrote:
> 
> > [    1.538646] fn_lookup bsg/0:0:0:0 -2, ffff88001f718000 bsg/0:0:0:0
> > [    1.539704] fn_lookup bsg 0, ffff88001f718000 bsg
> > [    1.540559] fn_lookup bsg/0:0:0:0 -2, ffff88001f718000 bsg/0:0:0:0
> > [    1.552611] fn_lookup bsg/1:0:0:0 -2, ffff88001f718000 bsg/1:0:0:0
> > [    1.553689] fn_lookup bsg 0, ffff88001f718000 bsg
> > [    1.554505] fn_lookup bsg/1:0:0:0 -2, ffff88001f718000 bsg/1:0:0:0
> > [    1.557554] fn_lookup sda 0, ffff88001f718000 sda
> > [    1.558368] fn_lookup sda 0, ffff88001f718000 sda
> > [    1.564190] fn_lookup sda1 0, ffff88001f718000 sda1
> > [    1.565008] fn_lookup sda1 0, ffff88001f718000 sda1
> > [    1.570751] fn_lookup /dev/ram -2, ffff88001f71a300 /dev/ram
> > [    1.571786] fn_lookup /dev/root -2, ffff88001f71b480 /dev/root
> 
> Nuts...  Is reverting just this (do_path_lookup()) part of commit sufficient
> to recover the normal behaviour?

Yes.

-- 
Sabrina
--
To unsubscribe from this list: send the line "unsubscribe linux-next" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux