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 16:32:30 +0900 [thread overview]
Message-ID: <87bk37t3zl.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <000001dad1ca$6b61c720$42255560$@samsung.com> (Sungjong Seo's message of "Tue, 9 Jul 2024 15:37:07 +0900")
"Sungjong Seo" <sj1557.seo@samsung.com> writes:
>> 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.
> You're right, if you can access to sysfs on a system, this might not
> be useful. However, when analyzing problems based on logs, s_dev can be
> very helpful for identifying devices. This is because, in systems like
> Android, a filesystem gets mounted on a device node with a nickname
> like public:179,1.
>
> I think it would be really useful if applied to representative filesystems
> for removable storage devices such as fat and exfat. So I will send the
> similar PR to exfat as well.
So this is for the naming policy like android? And why don't you care
the other places (like vfs) that using ->s_id?
Because I dislike to use the inconsitent stuff, some logs are "sda3" and
some logs are "sda3[8:3]".
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
next prev parent reply other threads:[~2024-07-09 7:32 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
2024-07-09 6:37 ` Sungjong Seo
2024-07-09 7:32 ` OGAWA Hirofumi [this message]
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=87bk37t3zl.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