From: Yuehaibing <yuehaibing@huawei.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: <adilger.kernel@dilger.ca>, <linux-ext4@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] ext4: Fix build error while CONFIG_PRINTK is n
Date: Thu, 2 Apr 2020 10:29:10 +0800 [thread overview]
Message-ID: <b9e56f54-2180-4a2c-3e0b-47e85dec221b@huawei.com> (raw)
In-Reply-To: <20200401212859.GN768293@mit.edu>
On 2020/4/2 5:28, Theodore Y. Ts'o wrote:
> On Wed, Apr 01, 2020 at 03:30:38PM +0800, YueHaibing wrote:
>> fs/ext4/balloc.c: In function ‘ext4_wait_block_bitmap’:
>> fs/ext4/balloc.c:519:3: error: implicit declaration of function ‘ext4_error_err’; did you mean ‘ext4_error’? [-Werror=implicit-function-declaration]
>> ext4_error_err(sb, EIO, "Cannot read block bitmap - "
>> ^~~~~~~~~~~~~~
>>
>> Add missing stub helper and fix ext4_abort.
>>
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Fixes: 2ea2fc775321 ("ext4: save all error info in save_error_info() and drop ext4_set_errno()")
>> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
>
> Thanks; the patch isn't quite correct, though. This is what I merged
> into my tree's version of the "save all error info..." commit.
>
> - Ted
>
Ok, good to know this and thansk!
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index eacd2f9cc833..91eb4381cae5 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -2848,6 +2848,11 @@ do { \
> no_printk(fmt, ##__VA_ARGS__); \
> __ext4_error_inode(inode, "", 0, block, 0, " "); \
> } while (0)
> +#define ext4_error_inode_err(inode, func, line, block, err, fmt, ...) \
> +do { \
> + no_printk(fmt, ##__VA_ARGS__); \
> + __ext4_error_inode(inode, "", 0, block, err, " "); \
> +} while (0)
> #define ext4_error_file(file, func, line, block, fmt, ...) \
> do { \
> no_printk(fmt, ##__VA_ARGS__); \
> @@ -2858,10 +2863,15 @@ do { \
> no_printk(fmt, ##__VA_ARGS__); \
> __ext4_error(sb, "", 0, 0, 0, " "); \
> } while (0)
> -#define ext4_abort(sb, fmt, ...) \
> +#define ext4_error_err(sb, err, fmt, ...) \
> +do { \
> + no_printk(fmt, ##__VA_ARGS__); \
> + __ext4_error(sb, "", 0, err, 0, " "); \
> +} while (0)
> +#define ext4_abort(sb, err, fmt, ...) \
> do { \
> no_printk(fmt, ##__VA_ARGS__); \
> - __ext4_abort(sb, "", 0, " "); \
> + __ext4_abort(sb, "", 0, err, " "); \
> } while (0)
> #define ext4_warning(sb, fmt, ...) \
> do { \
>
> .
>
prev parent reply other threads:[~2020-04-02 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 7:30 YueHaibing
2020-04-01 21:28 ` Theodore Y. Ts'o
2020-04-02 2:29 ` Yuehaibing [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=b9e56f54-2180-4a2c-3e0b-47e85dec221b@huawei.com \
--to=yuehaibing@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®