From: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Suresh Jayaraman <sjayaraman-IBi9RG/b67k@public.gmane.org>
Cc: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] cifs: reinstate the forcegid option
Date: Thu, 04 Oct 2012 15:50:57 +0100 [thread overview]
Message-ID: <1349362257.3691.6.camel@localhost> (raw)
In-Reply-To: <506D8C16.6070408-IBi9RG/b67k@public.gmane.org>
On Thu, 2012-10-04 at 18:46 +0530, Suresh Jayaraman wrote:
> On 10/04/2012 01:32 AM, Jeff Layton wrote:
> > Apparently this was lost when we converted to the standard option
> > parser.
> >
> > Cc: Sachin Prabhu <sprabhu-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > Reported-by: Gregory Lee Bartholomew <gregory.lee.bartholomew-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> > Signed-off-by: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> > ---
>
> Oops, atleast a couple of options have been reported missing and fixed
> so far. Time to audit the new parsing code so that we fix them
> proactively before we get reports from users..?
>
I am taking another look at the code to compare the options supported
against the old parser with the new parser. Some gotchas which tripped
me last time were checks for shortened options which also matched the
longer versions of the mount options.
We should also start thinking about paring down the number of mount
options which in my opinion are on the high side.
Sachin Prabhu
next prev parent reply other threads:[~2012-10-04 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 20:02 [PATCH] cifs: reinstate the forcegid option Jeff Layton
[not found] ` <1349294556-20656-1-git-send-email-jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2012-10-04 12:20 ` Sachin Prabhu
2012-10-04 13:16 ` Suresh Jayaraman
[not found] ` <506D8C16.6070408-IBi9RG/b67k@public.gmane.org>
2012-10-04 14:20 ` Scott Lovenberg
2012-10-04 14:50 ` Sachin Prabhu [this message]
2012-10-04 15:41 ` Sachin Prabhu
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=1349362257.3691.6.camel@localhost \
--to=sprabhu-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sjayaraman-IBi9RG/b67k@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.