Re: [PATCH mm-unstable 1/1] fs/proc/task_mmu: advance seq_file position on interrupted VMA lookup
From: Andrew Morton
Date: Fri Nov 13 2026 - 03:25:50 EST
On Thu, 12 Nov 2026 22:01:01 +0800 "Adrian Huang (Lenovo)" <adrianhuang0701@xxxxxxxxx> wrote:
> Commit 5631da56c9a8 ("fs/proc/task_mmu: read proc/pid/maps under
> per-vma lock") introduced the possibility of returning -EINTR
> from proc_get_vma() when the VMA lookup is interrupted.
OK, but what's causing the interruption?
> When this happens in m_next(), proc_get_vma() returns an error
> pointer without updating the position index. Consequently,
> seq_read_iter() reports:
>
> seq_file: buggy .next function m_next did not update position index
>
> The above buggy message is reproduced by the following command:
>
> # stress-ng --vma 0 -t 60
afaict "stress-ng -t" can send SIGALRM, but mmap_read_lock_killable()
only responds to fatal signals.
So please clarify: exactly what is causing this to happen?