From: Suren Baghdasaryan <surenb@google.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: akpm@linux-foundation.org, Liam.Howlett@oracle.com,
lorenzo.stoakes@oracle.com, david@redhat.com, peterx@redhat.com,
jannh@google.com, hannes@cmpxchg.org, mhocko@kernel.org,
paulmck@kernel.org, shuah@kernel.org, adobriyan@gmail.com,
brauner@kernel.org, josef@toxicpanda.com, yebin10@huawei.com,
linux@weissschuh.net, willy@infradead.org, osalvador@suse.de,
andrii@kernel.org, ryan.roberts@arm.com,
christophe.leroy@csgroup.eu, tjmercier@google.com,
kaleshsingh@google.com, aha310510@gmail.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 6/8] fs/proc/task_mmu: remove conversion of seq_file position to unsigned
Date: Wed, 9 Jul 2025 22:49:40 -0700 [thread overview]
Message-ID: <CAJuCfpG+rzpEqDYAOr+CH-4remxJzuGKEH-=zpf_bWcah-1atw@mail.gmail.com> (raw)
In-Reply-To: <0e0312c9-9a89-4a1b-a135-4425ea95d6f6@suse.cz>
On Tue, Jul 8, 2025 at 10:37 AM Vlastimil Babka <vbabka@suse.cz> wrote:
>
> On 7/4/25 08:07, Suren Baghdasaryan wrote:
> > Back in 2.6 era, last_addr used to be stored in seq_file->version
> > variable, which was unsigned long. As a result, sentinels to represent
> > gate vma and end of all vmas used unsigned values. In more recent
> > kernels we don't used seq_file->version anymore and therefore conversion
> > from loff_t into unsigned type is not needed. Similarly, sentinel values
> > don't need to be unsigned. Remove type conversion for set_file position
> > and change sentinel values to signed.
> >
> > Signed-off-by: Suren Baghdasaryan <surenb@google.com>
>
> Reviewed-by: Vlastimil Babka <vbabka@suse.cz>
>
> Some stuff in the code gave me a pause but it's out of scope here so just in
> case someone wants to do some extra churn...
>
> > ---
> > fs/proc/task_mmu.c | 14 +++++++-------
> > 1 file changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
> > index 751479eb128f..b8bc06d05a72 100644
> > --- a/fs/proc/task_mmu.c
> > +++ b/fs/proc/task_mmu.c
> > @@ -135,7 +135,7 @@ static struct vm_area_struct *proc_get_vma(struct proc_maps_private *priv,
> > if (vma) {
> > *ppos = vma->vm_start;
> > } else {
> > - *ppos = -2UL;
> > + *ppos = -2;
> > vma = get_gate_vma(priv->mm);
> > }
> >
> > @@ -145,11 +145,11 @@ static struct vm_area_struct *proc_get_vma(struct proc_maps_private *priv,
> > static void *m_start(struct seq_file *m, loff_t *ppos)
> > {
> > struct proc_maps_private *priv = m->private;
> > - unsigned long last_addr = *ppos;
> > + loff_t last_addr = *ppos;
> > struct mm_struct *mm;
> >
> > /* See m_next(). Zero at the start or after lseek. */
> > - if (last_addr == -1UL)
> > + if (last_addr == -1)
> > return NULL;
> >
> > priv->task = get_proc_task(priv->inode);
> > @@ -170,9 +170,9 @@ static void *m_start(struct seq_file *m, loff_t *ppos)
> > return ERR_PTR(-EINTR);
> > }
> >
> > - vma_iter_init(&priv->iter, mm, last_addr);
> > + vma_iter_init(&priv->iter, mm, (unsigned long)last_addr);
>
> I wonder if this should rather be done only after dealing with the -2 case
> below. It seems wrong to init the iterator with a bogus address. What if it
> acquires some sanity checks?
>
> > hold_task_mempolicy(priv);
>
> It seems suboptimal to do that mempolicy refcount dance for numa_maps sake
> even if we're reading a different /proc file... maybe priv could have a flag
> to determine?
>
> > - if (last_addr == -2UL)
> > + if (last_addr == -2)
> > return get_gate_vma(mm);
>
> I think only after the above it makes sense to init the iterator?
Yes makes sense but let me do that outside of this patchset as it's
rather unrelated.
>
> > return proc_get_vma(priv, ppos);
> > @@ -180,8 +180,8 @@ static void *m_start(struct seq_file *m, loff_t *ppos)
> >
> > static void *m_next(struct seq_file *m, void *v, loff_t *ppos)
> > {
> > - if (*ppos == -2UL) {
> > - *ppos = -1UL;
> > + if (*ppos == -2) {
> > + *ppos = -1;
> > return NULL;
> > }
> > return proc_get_vma(m->private, ppos);
>
next prev parent reply other threads:[~2025-07-10 5:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 6:07 [PATCH v6 0/8] use per-vma locks for /proc/pid/maps reads and PROCMAP_QUERY Suren Baghdasaryan
2025-07-04 6:07 ` [PATCH v6 1/8] selftests/proc: add /proc/pid/maps tearing from vma split test Suren Baghdasaryan
2025-07-04 6:07 ` [PATCH v6 2/8] selftests/proc: extend /proc/pid/maps tearing test to include vma resizing Suren Baghdasaryan
2025-07-04 6:07 ` [PATCH v6 3/8] selftests/proc: extend /proc/pid/maps tearing test to include vma remapping Suren Baghdasaryan
2025-07-04 6:07 ` [PATCH v6 4/8] selftests/proc: test PROCMAP_QUERY ioctl while vma is concurrently modified Suren Baghdasaryan
2025-07-04 6:07 ` [PATCH v6 5/8] selftests/proc: add verbose more for tests to facilitate debugging Suren Baghdasaryan
2025-07-04 6:07 ` [PATCH v6 6/8] fs/proc/task_mmu: remove conversion of seq_file position to unsigned Suren Baghdasaryan
2025-07-07 15:01 ` Lorenzo Stoakes
2025-07-08 17:37 ` Vlastimil Babka
2025-07-10 5:49 ` Suren Baghdasaryan [this message]
2025-07-04 6:07 ` [PATCH v6 7/8] fs/proc/task_mmu: read proc/pid/maps under per-vma lock Suren Baghdasaryan
2025-07-07 16:51 ` Lorenzo Stoakes
2025-07-07 23:10 ` Suren Baghdasaryan
2025-07-09 8:57 ` Vlastimil Babka
2025-07-09 14:43 ` Suren Baghdasaryan
2025-07-09 15:03 ` Vlastimil Babka
2025-07-09 15:06 ` Suren Baghdasaryan
2025-07-09 16:11 ` Liam R. Howlett
2025-07-09 17:47 ` Suren Baghdasaryan
2025-07-10 7:03 ` Suren Baghdasaryan
2025-07-10 17:02 ` Suren Baghdasaryan
2025-07-10 17:42 ` Vlastimil Babka
2025-07-15 8:16 ` Vlastimil Babka
2025-07-15 9:40 ` Lorenzo Stoakes
2025-07-15 9:52 ` David Hildenbrand
2025-07-15 10:16 ` Lorenzo Stoakes
2025-07-15 10:23 ` Vlastimil Babka
2025-07-15 10:31 ` Lorenzo Stoakes
2025-07-15 10:51 ` Lorenzo Stoakes
2025-07-15 17:05 ` Andrii Nakryiko
2025-07-15 17:10 ` Lorenzo Stoakes
2025-07-15 17:20 ` Lorenzo Stoakes
2025-07-15 17:29 ` Andrii Nakryiko
2025-07-15 20:18 ` Suren Baghdasaryan
2025-07-16 1:50 ` Suren Baghdasaryan
2025-07-15 20:13 ` Suren Baghdasaryan
2025-07-16 14:00 ` Lorenzo Stoakes
2025-07-16 14:07 ` Vlastimil Babka
2025-07-16 14:27 ` Suren Baghdasaryan
2025-07-07 18:20 ` Liam R. Howlett
2025-07-07 23:12 ` Suren Baghdasaryan
2025-07-09 10:03 ` Vlastimil Babka
2025-07-09 14:43 ` Suren Baghdasaryan
2025-07-04 6:07 ` [PATCH v6 8/8] fs/proc/task_mmu: execute PROCMAP_QUERY ioctl under per-vma locks Suren Baghdasaryan
2025-07-07 16:54 ` Lorenzo Stoakes
2025-07-07 18:26 ` Liam R. Howlett
2025-07-15 8:10 ` [PATCH v6 0/8] use per-vma locks for /proc/pid/maps reads and PROCMAP_QUERY Lorenzo Stoakes
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='CAJuCfpG+rzpEqDYAOr+CH-4remxJzuGKEH-=zpf_bWcah-1atw@mail.gmail.com' \
--to=surenb@google.com \
--cc=Liam.Howlett@oracle.com \
--cc=adobriyan@gmail.com \
--cc=aha310510@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=brauner@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=jannh@google.com \
--cc=josef@toxicpanda.com \
--cc=kaleshsingh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@weissschuh.net \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=paulmck@kernel.org \
--cc=peterx@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=tjmercier@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yebin10@huawei.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