From: Timothy Shimmin <tes@sgi.com>
To: Jianjun Kong <jianjun@zeuux.org>,
Dave Chinner <david@fromorbit.com>,
stable@kernel.org, linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH] XFS fix remount rw with unrecognized options
Date: Fri, 17 Oct 2008 09:48:07 +1100 [thread overview]
Message-ID: <48F7C4A7.5090708@sgi.com> (raw)
In-Reply-To: <20081016223637.GB31761@disturbed>
Dave Chinner wrote:
> On Thu, Oct 16, 2008 at 09:41:12PM +0800, Jianjun Kong wrote:
>> And the code above "return 0" can not be executed, so delete them.
>> __________________________________________
>> #if 0
>> printk(KERN_INFO
>> "XFS: mount option \"%s\" not supported for remount\n", p);
>> return -EINVAL;
>> #else
>> return 0;
>> -----------------------------------------
>
> That ifdef was added to stub out the behaviour we *actually want*
> remount to have when it encounters an invalid remount option.
> The reason for leaving it is in the next release we should have all
> the other problems we discovered by doing this fixed, so that
> code will be re-enabled. Hence the temporary #if 0 around it.
>
> So at this point, don't remove it.
>
> Cheers,
>
> Dave.
Exactly.
I don't want it removed.
Extra code for comparing existing mount state with new mount state
needs to be done and this code can be reactivated when we sort
this stuff out later.
This patch should be just the fix for the current regression.
Thanks,
--Tim
next prev parent reply other threads:[~2008-10-16 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 0:29 [PATCH] XFS fix remount rw with unrecognized options Tim Shimmin
2008-10-16 13:41 ` Jianjun Kong
2008-10-16 13:55 ` Klaus Strebel
2008-10-16 14:07 ` Jianjun Kong
2008-10-16 13:59 ` Américo Wang
2008-10-16 22:36 ` Dave Chinner
2008-10-16 22:48 ` Timothy Shimmin [this message]
2008-10-16 17:35 ` [stable] " Greg KH
2008-10-16 18:10 ` Christoph Hellwig
2008-10-16 22:39 ` Greg KH
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=48F7C4A7.5090708@sgi.com \
--to=tes@sgi.com \
--cc=david@fromorbit.com \
--cc=jianjun@zeuux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=xfs@oss.sgi.com \
/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