mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Zarochentsev <zam@namesys.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Re: [RFC] MS_VERBOSE handling in get_sb_bdev()
Date: Fri, 15 Oct 2004 11:03:39 +0400	[thread overview]
Message-ID: <20041015070339.GE25932@backtop.namesys.com> (raw)
In-Reply-To: <416ECA78.6020405@osdl.org>

On Thu, Oct 14, 2004 at 11:50:32AM -0700, Randy.Dunlap wrote:
> Alex Zarochentsev wrote:
> >Hello,
> >
> >Anybody knows why the "silent" agrument of the fs' ->fill_super() routines 
> >is
> >passed as ((flags & MS_VERBOSE) ? 1 : 0) ?.  It should be !(flags & 
> >MS_VERBOSE)
> >instead, yes?
> >
> >I don't belive the bug is not known... 
> 
> I saw several of those about 1 year ago when I updated Al's
> fs option patches and got them merged.
> 
> They should be fixed IMO, but it's low priority, they work ("it ain't
> broke so don't fix it"), and maybe someone else thinks that there is
> no problem at all, i.e., they aren't broken at all...

The kernel (2.6.9-rc4) patch is simple
==================================
--- linux/fs/super.c.orig	2004-10-14 18:12:50.213426568 +0400
+++ linux/fs/super.c	2004-10-14 18:13:46.923805280 +0400
@@ -692,7 +692,7 @@ struct super_block *get_sb_bdev(struct f
 		strlcpy(s->s_id, bdevname(bdev, b), sizeof(s->s_id));
 		s->s_old_blocksize = block_size(bdev);
 		sb_set_blocksize(s, s->s_old_blocksize);
-		error = fill_super(s, data, flags & MS_VERBOSE ? 1 : 0);
+		error = fill_super(s, data, !(flags & MS_VERBOSE));
 		if (error) {
 			up_write(&s->s_umount);
 			deactivate_super(s);
==================================

there is another bug in the mount utility, it seems to me.  mount never sets
MS_VERBOSE.  I think it should be set when the mount does not do "fs probing"
as in "mount -t auto ".

> -- 
> ~Randy

-- 
Alex.

      reply	other threads:[~2004-10-15  7:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 16:06 Alex Zarochentsev
2004-10-14 18:50 ` Randy.Dunlap
2004-10-15  7:03   ` Alex Zarochentsev [this message]

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=20041015070339.GE25932@backtop.namesys.com \
    --to=zam@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome