From: Richard Weinberger <richard@nod.at>
To: rockdotlee@gmail.com
Cc: linux-mtd@lists.infradead.org, dedekind1@gmail.com,
adrian.hunter@intel.com
Subject: Re: [PATCH] ubifs: Change log level in ubifs_xattr_get
Date: Wed, 10 Jan 2018 15:39:21 +0100 [thread overview]
Message-ID: <3873582.N8pb6r5EOO@blindfold> (raw)
In-Reply-To: <1515578741-6612-1-git-send-email-rockdotlee@gmail.com>
Rock Lee,
Am Mittwoch, 10. Januar 2018, 11:05:41 CET schrieb rockdotlee@gmail.com:
> From: Rock Lee <rockdotlee@gmail.com>
>
> Just print warning message when xattr value size is bigger than the
> buffer size. There is a situation that other modules, like overlayfs,
> try to get xattr value with a small buffer, if they get -ERANGE, they
> will try again with the proper buffer size. No need to report a error
> message, warning message is enough.
>
> Signed-off-by: Rock Lee <rockdotlee@gmail.com>
> ---
> fs/ubifs/xattr.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ubifs/xattr.c b/fs/ubifs/xattr.c
> index 5ddc89d..bc20530 100644
> --- a/fs/ubifs/xattr.c
> +++ b/fs/ubifs/xattr.c
> @@ -381,7 +381,7 @@ ssize_t ubifs_xattr_get(struct inode *host, const char
> *name, void *buf, if (buf) {
> /* If @buf is %NULL we are supposed to return the length */
> if (ui->data_len > size) {
> - ubifs_err(c, "buffer size %zd, xattr len %d",
> + ubifs_warn(c, "buffer size %zd, xattr len %d",
> size, ui->data_len);
Hmm, if this can be triggered that easy I suggest getting completely rid of
this message.
Thanks,
//richard
next prev parent reply other threads:[~2018-01-10 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 10:05 [PATCH] ubifs: Change log level in ubifs_xattr_get rockdotlee
2018-01-10 14:39 ` Richard Weinberger [this message]
2018-01-11 1:47 ` Rock Lee
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=3873582.N8pb6r5EOO@blindfold \
--to=richard@nod.at \
--cc=adrian.hunter@intel.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=rockdotlee@gmail.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