From: Brian Norris <computersforpeace@gmail.com>
To: Daniel Golle <daniel@makrotopia.org>
Cc: hujianyang@huawei.com, linux-mtd@lists.infradead.org,
dedekind1@gmail.com
Subject: Re: [PATCH v3] ubifs: respect MS_SILENT mount flag
Date: Fri, 30 May 2014 16:20:39 -0700 [thread overview]
Message-ID: <20140530232039.GH3599@ld-irv-0074> (raw)
In-Reply-To: <20140530220149.GA30631@earthship.lan>
Hi Daniel,
On Sat, May 31, 2014 at 12:01:56AM +0200, Daniel Golle wrote:
> When attempting to mount a non-ubifs formatted volume, lots of error
> messages (including a stack dump) are thrown to the kernel log even if
> the MS_SILENT mount flag is set.
> Fix this by introducing adding an additional state-variable in
> struct ubifs_info and suppress error messages in ubifs_read_node if
> MS_SILENT is set.
>
> Signed-off-by: Daniel Golle <daniel@makrotopia.org>
> ---
> v3: use state variable in ubifs_info instead of
Instead of what?? I'm dying to know!
(Just kidding; I can read your previous conversations. Hint: the answer
is "a function argument.")
> fs/ubifs/io.c | 14 ++++++++------
> fs/ubifs/super.c | 4 ++++
> fs/ubifs/ubifs.h | 9 +++++++++
> 3 files changed, 21 insertions(+), 6 deletions(-)
>
[...]
> diff --git a/fs/ubifs/ubifs.h b/fs/ubifs/ubifs.h
> index e8c8cfe..6aa1550 100644
> --- a/fs/ubifs/ubifs.h
> +++ b/fs/ubifs/ubifs.h
> @@ -52,6 +52,14 @@
> pr_warn("UBIFS warning (pid %d): %s: " fmt "\n", \
> current->pid, __func__, ##__VA_ARGS__)
>
> +/*
> + * A variant of 'ubifs_err()' which takes the UBIFS file-sytem description
> + * object as an argument.
> + */
> +#define ubifs_errc(c, fmt, ...) \
> + if (!(c)->probing) \
> + ubifs_err(fmt, ##__VA_ARGS__)
Nitpick: might you want to wrap the whole condition in do { } while (0),
so that a user can't shoot themselves in the foot with something like:
if (condition)
ubifs_errc(c, "hello world");
else
do_something_else();
which will expand to the following unexpected code:
if (condition)
if (!c->probing)
ubifs_err("hello world");
else
do_something_else();
> +
> /* UBIFS file system VFS magic number */
> #define UBIFS_SUPER_MAGIC 0x24051905
>
Brian
next prev parent reply other threads:[~2014-05-30 23:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 1:55 [PATCH] ubifs: respect MS_SILENT mount flag Daniel Golle
2014-05-27 12:18 ` Artem Bityutskiy
2014-05-27 14:11 ` [PATCH v2] " Daniel Golle
2014-05-27 14:56 ` Artem Bityutskiy
2014-05-27 16:04 ` Daniel
2014-05-28 2:11 ` hujianyang
2014-05-28 8:01 ` Artem Bityutskiy
2014-05-28 8:07 ` Bityutskiy, Artem
2014-05-28 8:14 ` Artem Bityutskiy
2014-05-28 8:28 ` Artem Bityutskiy
2014-05-28 8:42 ` hujianyang
2014-05-28 9:29 ` Artem Bityutskiy
2014-05-30 22:01 ` [PATCH v3] " Daniel Golle
2014-05-30 23:20 ` Brian Norris [this message]
2014-05-30 23:32 ` [PATCH v4] " Daniel Golle
2014-05-31 0:01 ` [PATCH v5] " Daniel Golle
2014-06-02 7:59 ` Artem Bityutskiy
2014-06-02 13:51 ` [PATCH v6] " Daniel Golle
2014-06-02 15:01 ` Artem Bityutskiy
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=20140530232039.GH3599@ld-irv-0074 \
--to=computersforpeace@gmail.com \
--cc=daniel@makrotopia.org \
--cc=dedekind1@gmail.com \
--cc=hujianyang@huawei.com \
--cc=linux-mtd@lists.infradead.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