linux-kernel - Re: [PATCH] init: don't try mounting device as nfs root unless type fully matches

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]

Date:	Mon, 7 May 2012 10:56:25 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Sasha Levin <levinsasha928@...il.com>
Cc:	torvalds@...ux-foundation.org, chuck.lever@...cle.com,
	linux@...ik.name, Trond.Myklebust@...app.com,
	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	mingo@...e.hu
Subject: Re: [PATCH] init: don't try mounting device as nfs root unless type
 fully matches


* Ingo Molnar <mingo@...nel.org> wrote:

> 
> * Sasha Levin <levinsasha928@...il.com> wrote:
> 
> > Currently, we'll try mounting any device who's major device number is
> > UNNAMED_MAJOR as NFS root. This would happen for non-NFS devices as well (such
> > as 9p devices) but it wouldn't cause any issues since mounting the device
> > as NFS would fail quickly and the code proceeded to doing the proper mount:
> > 
> >        [  101.522716] VFS: Unable to mount root fs via NFS, trying floppy.
> >        [  101.534499] VFS: Mounted root (9p filesystem) on device 0:18.
> > 
> > Commit 6829a048 ("NFS: Retry mounting NFSROOT") has introduced retries when
> > mounting NFS root, which means that now we don't immediately fail and instead
> > it takes an additional 90+ seconds until we stop retrying, which has revealed
> > the issue this patch fixes.
> 
> Just wondering, which tree is commit 6829a048 included in? It 
> does not appear to be mainline AFAICS.

appears to be:

43717c7daebf NFS: Retry mounting NFSROOT

The commit ID you cited is apparently one that got exposed to 
linux-next but got rebased subsequently, before it went 
upstream, or so.

Thanks,

	Ingo
--
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/