All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: Dave Reisner <d@falconindy.com>, linux-kernel@vger.kernel.org
Cc: tj@kernel.org
Subject: Re: Initramfs FSID altered in 3.14
Date: Thu, 03 Apr 2014 20:13:50 +0200	[thread overview]
Message-ID: <533DA4DE.40408@archlinux.org> (raw)
In-Reply-To: <20140403175744.GE585@rampage>

[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]

Am 03.04.2014 19:57, schrieb Dave Reisner:
> Hi,
> 
> [This is a repost of a G+ post at Tejun's request]
> 
> With Linux 3.14, you might notice in /proc/self/mountinfo that your
> root's parent FSID is now 0, instead of the 1 that it's been for the
> last N years. Tejun wrote the change (9e30cc9595303b27b48) that caused
> this, but the change comes in a rather innocuous way. Instead of an
> internal kernel mount of sysfs being assigned 0, it's now the initramfs.
> 
> So far, this has already caused switch_root and findmnt (from
> util-linux) to break, cp (from coreutils) to break when using the -x
> flag in early userspace, and it's also been pointed out that systemd's
> readahead code makes assumptions about a device number of 0.
> 
> Are we now supposed to go and change all the assumptions in userspace
> about 0 being special? I'm conflicted. The kernel isn't supposed to
> break userspace, but it seems to me that FSIDs were never something to
> rely on -- similar to the block device numbering scheme.

Most of these bugs were not caused by rootfs' FSID being different from
1, but rather because there was a file system with FSID 0.

Only util-linux/switch_root assumed that rootfs always had exactly FSID
1 - which is IMO a wrong assumption.

However, tt seems that people have been assuming that st_dev > 0 for a
while. If we want to revert this in the kernel, this patch (untested)
should be sufficient:

diff --git a/fs/super.c b/fs/super.c
index 80d5cf2..d9fddde 100644
--- a/fs/super.c
+++ b/fs/super.c
@@ -802,7 +802,7 @@ void emergency_remount(void)
 static DEFINE_IDA(unnamed_dev_ida);
 static DEFINE_SPINLOCK(unnamed_dev_lock);/* protects the above */
-static int unnamed_dev_start = 0; /* don't bother trying below it */
+static int unnamed_dev_start = 1; /* don't bother trying below it */
 int get_anon_bdev(dev_t *p)
 {



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-04-03 18:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 17:57 Initramfs FSID altered in 3.14 Dave Reisner
2014-04-03 18:13 ` Thomas Bächler [this message]
2014-04-03 19:16   ` Tejun Heo
2014-04-03 19:20     ` Theodore Ts'o
2014-04-03 22:02       ` Alexandre Demers
2014-04-03 19:49     ` [PATCH] fs: Don't return 0 from get_anon_bdev Thomas Bächler
2014-04-03 19:51       ` Tejun Heo
2014-04-03 19:51         ` Tejun Heo
2014-04-03 19:55         ` [PATCHv2] " Thomas Bächler
2014-04-03 20:32           ` Greg KH
2014-04-03 20:32             ` Greg KH
2014-04-03 20:21       ` [PATCH] " H. Peter Anvin
2014-04-03 23:41       ` Alexandre Demers
2014-04-03 18:57 ` Initramfs FSID altered in 3.14 Pádraig Brady
2014-04-03 19:13 ` Tejun Heo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=533DA4DE.40408@archlinux.org \
    --to=thomas@archlinux.org \
    --cc=d@falconindy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.