From: Randy Dunlap <rdunlap@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-ext4@vger.kernel.org, Jan Kara <jack@suse.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] ext2: fix debug reference to ext2_xattr_cache
Date: Tue, 17 Mar 2020 08:19:48 -0700 [thread overview]
Message-ID: <9b4e1fa7-b4f8-b2a9-8269-04daeb3dfaaa@infradead.org> (raw)
In-Reply-To: <20200317114712.GH22684@quack2.suse.cz>
On 3/17/20 4:47 AM, Jan Kara wrote:
> On Fri 13-03-20 20:42:05, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>>
>> Fix a debug-only build error in ext2/xattr.c:
>>
>> When building without extra debugging, (and with another patch that uses
>> no_printk() instead of <empty> for the ext2-xattr debug-print macros,
>> this build error happens:
>>
>> ../fs/ext2/xattr.c: In function ‘ext2_xattr_cache_insert’:
>> ../fs/ext2/xattr.c:869:18: error: ‘ext2_xattr_cache’ undeclared (first use in this function); did you mean ‘ext2_xattr_list’?
>> atomic_read(&ext2_xattr_cache->c_entry_count));
>>
>> Fix by moving struct mb_cache from fs/mbcache.c to <linux/mbcache.h>,
>> and then using the correct struct name in the debug-print macro.
>>
>> This wasn't converted when ext2 xattr cache was changed to use mbcache.
>>
>> Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Jan Kara <jack@suse.com>
>> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
>> Cc: linux-ext4@vger.kernel.org
>> Cc: linux-fsdevel@vger.kernel.org
>
> Thanks for the patch! I don't think exporting 'struct mb_cache' just for
> this is reasonable. I've committed a patch which just removes the entry
> count from the debug message (attached).
>
Sure, that's good. I have a patch like that one on my system also. :)
>
>> ---
>> This is ancient, from the beginning of git history.
>>
>> Or just kill of that print of c_entry_count...
>>
>> fs/ext2/xattr.c | 2 +-
>> fs/mbcache.c | 34 ----------------------------------
>> include/linux/mbcache.h | 35 ++++++++++++++++++++++++++++++++++-
>> 3 files changed, 35 insertions(+), 36 deletions(-)
--
~Randy
prev parent reply other threads:[~2020-03-17 15:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-14 3:42 [PATCH] ext2: fix debug reference to ext2_xattr_cache Randy Dunlap
2020-03-17 11:47 ` Jan Kara
2020-03-17 15:19 ` Randy Dunlap [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=9b4e1fa7-b4f8-b2a9-8269-04daeb3dfaaa@infradead.org \
--to=rdunlap@infradead.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).