From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] [GFS2] bz253289 Add NULL entry to token table
Date: Sat, 18 Aug 2007 16:00:04 +0100 [thread overview]
Message-ID: <1187449204.3354.0.camel@menhir.chygwyn.com> (raw)
In-Reply-To: <20070818012206.GH24772@ether.msp.redhat.com>
Hi,
Now in the -nmw git tree. Thanks,
Steve.
On Fri, 2007-08-17 at 20:22 -0500, Benjamin Marzinski wrote:
> match_token() was returning garbage data instead of a fail value. This data
> happened to match a valid option id for an option that required an argument (in
> this case, lockproto=%s) For match_token() to correctly fail if the option
> doesn't match any of the tokens, the token table must end with a NULL entry.
> This patch adds the NULL entry.
>
> Signed-off-by: Benjamin E. Marzinski <bmarzins@redhat.com>
> plain text document attachment (mount_panic.patch)
> diff -urpN --exclude-from=gfs2-2.6-nmw/Documentation/dontdiff gfs2-2.6-nmw/fs/gfs2/mount.c gfs2-2.6-nmw-patched/fs/gfs2/mount.c
> --- gfs2-2.6-nmw/fs/gfs2/mount.c 2007-08-13 16:18:01.000000000 -0500
> +++ gfs2-2.6-nmw-patched/fs/gfs2/mount.c 2007-08-17 12:04:36.000000000 -0500
> @@ -42,6 +42,7 @@ enum {
> Opt_nosuiddir,
> Opt_data_writeback,
> Opt_data_ordered,
> + Opt_err,
> };
>
> static match_table_t tokens = {
> @@ -64,7 +65,8 @@ static match_table_t tokens = {
> {Opt_suiddir, "suiddir"},
> {Opt_nosuiddir, "nosuiddir"},
> {Opt_data_writeback, "data=writeback"},
> - {Opt_data_ordered, "data=ordered"}
> + {Opt_data_ordered, "data=ordered"},
> + {Opt_err, NULL}
> };
>
> /**
> @@ -237,6 +239,7 @@ int gfs2_mount_args(struct gfs2_sbd *sdp
> case Opt_data_ordered:
> args->ar_data = GFS2_DATA_ORDERED;
> break;
> + case Opt_err:
> default:
> fs_info(sdp, "unknown option: %s\n", o);
> error = -EINVAL;
prev parent reply other threads:[~2007-08-18 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 1:22 [Cluster-devel] [PATCH] [GFS2] bz253289 Add NULL entry to token table Benjamin Marzinski
2007-08-18 15:00 ` Steven Whitehouse [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=1187449204.3354.0.camel@menhir.chygwyn.com \
--to=swhiteho@redhat.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;
as well as URLs for NNTP newsgroup(s).