linux-kernel - Re: Problems with nfsroot due to ip= cmdline changes

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: <20080106093211.GB3172@verge.net.au>
Date:	Sun, 6 Jan 2008 18:32:11 +0900
From:	Simon Horman <horms@...ge.net.au>
To:	Ville Syrjälä <syrjala@....fi>,
	linux-kernel@...r.kernel.org,
	"David S. Miller" <davem@...emloft.net>
Cc:	Amos Waterland <apw@...ibm.com>
Subject: Re: Problems with nfsroot due to ip= cmdline changes

On Sat, Jan 05, 2008 at 06:56:23PM +0200, Ville Syrjälä wrote:
> I recently rebased my kernel tree and discovered that my nfsroot setup
> no longer worked. Here's the relevat part of my cmdline:
> 
> ip=192.168.2.200:192.168.2.185:192.168.2.1:255.255.255.0::eth0:off nfsroot=192.168.2.185:/my_nfsroot,v3,tcp root=/dev/nfs
> 
> I discovered that now I had to change the autoconfiguration option to
> "on" in order to make nfsroot work. I only want to specify the IP
> address manually so I don't really want autoconfiguration. The current
> code works since it will not try autoconfiguration when all options are
> specified manually but the current behaviour does not really match the
> documentation ie. now the autoconf parameter can disable the whole IP
> configuration step even though the documentation says it will only
> disable autoconfiguration.
> 
> Looks like these are the relevant commits:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=a6c05c3d064dbb83be88cba3189beb5db9d2dfc3
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=9cecd07c3f7a818a5865daad8cb5be408508dc99

Hi,

I believe that this patch from Amos Waterland resolves the problem that
you are seeing: http://lkml.org/lkml/2008/1/5/247

-- 
Horms

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