From: Wei Gao <wegao@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>
Cc: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Penglei Jiang <superman.xpt@gmail.com>,
Mark Brown <broonie@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Brahmajit Das <brahmajit.xyz@gmail.com>,
Andrei Vagin <avagin@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Andrii Nakryiko <andrii@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Wei Gao <wegao@suse.com>
Subject: [PATCH] fs/proc: Use inode_get_dev() for device numbers in procmap_query
Date: Wed, 16 Jul 2025 10:27:32 -0400 [thread overview]
Message-ID: <20250716142732.3385310-1-wegao@suse.com> (raw)
This ensures consistency and proper abstraction when accessing device
information associated with an inode.
Signed-off-by: Wei Gao <wegao@suse.com>
---
fs/proc/task_mmu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
index 751479eb128f..b113a274f814 100644
--- a/fs/proc/task_mmu.c
+++ b/fs/proc/task_mmu.c
@@ -518,8 +518,8 @@ static int do_procmap_query(struct proc_maps_private *priv, void __user *uarg)
const struct inode *inode = file_user_inode(vma->vm_file);
karg.vma_offset = ((__u64)vma->vm_pgoff) << PAGE_SHIFT;
- karg.dev_major = MAJOR(inode->i_sb->s_dev);
- karg.dev_minor = MINOR(inode->i_sb->s_dev);
+ karg.dev_major = MAJOR(inode_get_dev(inode));
+ karg.dev_minor = MINOR(inode_get_dev(inode));
karg.inode = inode->i_ino;
} else {
karg.vma_offset = 0;
--
2.49.0
next reply other threads:[~2025-07-16 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 14:27 Wei Gao [this message]
2025-07-16 17:06 ` kernel test robot
2025-07-16 20:39 ` Wei Gao
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=20250716142732.3385310-1-wegao@suse.com \
--to=wegao@suse.com \
--cc=Jason@zx2c4.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=avagin@gmail.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=brahmajit.xyz@gmail.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=david@redhat.com \
--cc=joey.gouly@arm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=ryan.roberts@arm.com \
--cc=superman.xpt@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
all inboxes | Powered by JetHome®