kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1251274

Title:
  Kernel command line does not correctly parse ip field if nfsroot

Status in tools for generating an initramfs:
  New
Status in klibc:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Kernel image linux-image-3.8.0.31-generic
  Ubuntu 12.04.3 LTS

  I'm setting up machines with nfsroot.
  dhcp works fine, but a static address fails to set resolvconf. 

  The document https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt
  states that there are between one and nine fields in the kernel command line option 'ip=' separated by colons.

  The last two are dns0 and dns1
  e.g.
  APPEND root=/dev/nfs nfsroot=10.0.0.1:/exports/nfsroot initrd=boot/initrd.img ip=10.0.0.200:10.0.0.1:10.0.0.1:255.0.0.0:itx1c:eth0:off:10.0.0.1:0.0.0.0 rootwait=1 nfsdebug=1 nfsrootdebug=1 rw

  I find that if I supply one or both dns addresses, then the boot fails
  with the message

  ipconfig: too many options for eth0
  and then when configure_networking (from scripts/functions in /usr/share/initramsfs-tools/) runs (called by scripts/nfs) says it can't create it's temp file 
  /tmp/net-eth0:off:10.0.0.1:0.0.0.0
  After that we get a kernel panic as init completes badly.

  Clearly the command line parsing does not meet the spec in the above
  reference.

  I'm sure I can work round this by not supplying dns addresses in the
  command line and re-writing /etc/resolv.conf elsewhere, but this needs
  fixing properly.

  I'm not sure if the ip= line is parsed elsewhere so I don't have
  enough information to offer a proper fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1251274/+subscriptions