From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Sungjong Seo <sj1557.seo@samsung.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fat: print s_dev via fat_msg
Date: Tue, 09 Jul 2024 14:33:25 +0900 [thread overview]
Message-ID: <87frsjt9i2.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <20240709041734.3719513-1-sj1557.seo@samsung.com> (Sungjong Seo's message of "Tue, 9 Jul 2024 13:17:34 +0900")
Sungjong Seo <sj1557.seo@samsung.com> writes:
> To clarify MAJOR/MINOR number of a mounted device, fat_msg prints prefix
> that includes them.
Hm, why do we need the major/minor (why can't use sysfs to resolve if
need), and why do you care only fat?
Thanks.
> Signed-off-by: Sungjong Seo <sj1557.seo@samsung.com>
> ---
> fs/fat/fat.h | 2 +-
> fs/fat/misc.c | 4 +++-
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/fs/fat/fat.h b/fs/fat/fat.h
> index 66cf4778cf3b..538bcb3e28e1 100644
> --- a/fs/fat/fat.h
> +++ b/fs/fat/fat.h
> @@ -435,7 +435,7 @@ void __fat_fs_error(struct super_block *sb, int report, const char *fmt, ...);
> #define fat_fs_error_ratelimit(sb, fmt, args...) \
> __fat_fs_error(sb, __ratelimit(&MSDOS_SB(sb)->ratelimit), fmt , ## args)
>
> -#define FAT_PRINTK_PREFIX "%sFAT-fs (%s): "
> +#define FAT_PRINTK_PREFIX "%sFAT-fs (%s[%d:%d]): "
> #define fat_msg(sb, level, fmt, args...) \
> do { \
> printk_index_subsys_emit(FAT_PRINTK_PREFIX, level, fmt, ##args);\
> diff --git a/fs/fat/misc.c b/fs/fat/misc.c
> index c7a2d27120ba..6672cefc5484 100644
> --- a/fs/fat/misc.c
> +++ b/fs/fat/misc.c
> @@ -9,6 +9,7 @@
>
> #include "fat.h"
> #include <linux/iversion.h>
> +#include <linux/blkdev.h>
>
> /*
> * fat_fs_error reports a file system problem that might indicate fa data
> @@ -59,7 +60,8 @@ void _fat_msg(struct super_block *sb, const char *level, const char *fmt, ...)
> va_start(args, fmt);
> vaf.fmt = fmt;
> vaf.va = &args;
> - _printk(FAT_PRINTK_PREFIX "%pV\n", level, sb->s_id, &vaf);
> + _printk(FAT_PRINTK_PREFIX "%pV\n", level, sb->s_id,
> + MAJOR(sb->s_dev), MINOR(sb->s_dev), &vaf);
> va_end(args);
> }
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2024-07-09 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240709041754epcas1p4ee6f7b1fd0dbf287e756b709aba321c8@epcas1p4.samsung.com>
2024-07-09 4:17 ` [PATCH] fat: print s_dev via fat_msg Sungjong Seo
2024-07-09 5:33 ` OGAWA Hirofumi [this message]
2024-07-09 6:37 ` Sungjong Seo
2024-07-09 7:32 ` OGAWA Hirofumi
2024-07-09 11:35 ` Sungjong Seo
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=87frsjt9i2.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.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