On Thu, Apr 03, 2014 at 09:49:55PM +0200, Thomas Bächler wrote: > Commit 9e30cc9595303b27b48 removed an internal mount. This > has the side-effect that rootfs now has FSID 0. Many > userspace utilities assume that st_dev in struct stat > is never 0, so this change breaks a number of tools in > early userspace. > > Since we don't know how many userspace programs are affected, > make sure that FSID is at least 1. > > References: http://article.gmane.org/gmane.linux.kernel/1666905 > References: http://permalink.gmane.org/gmane.linux.utilities.util-linux-ng/8557 > Cc: 3.14 <stable@xxxxxxxxxxxxxxx> > Signed-off-by: Thomas Bächler <thomas@xxxxxxxxxxxxx> Provided Alexandre confirms the fix. Acked-by: Tejun Heo <tj@xxxxxxxxxx> > --- > fs/super.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > 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 */ Maybe a comment saying that userland considers fsid 0 to be invalid would be nice? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html