From: Matthew Wilcox <willy@infradead.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org,
syzbot+5b19bad23ac7f44bf8b8@syzkaller.appspotmail.com,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Subject: Re: [PATCH] mm: fix vma_start_write_killable() signal handling
Date: Wed, 26 Nov 2025 15:01:40 +0000 [thread overview]
Message-ID: <aScWVB_l-Hh5zGCe@casper.infradead.org> (raw)
In-Reply-To: <CAJuCfpEge7MJD1joXz=tKgcD7DQgPggjCKF9PLPr3NZEaw=ouw@mail.gmail.com>
On Wed, Nov 26, 2025 at 06:26:26AM -0800, Suren Baghdasaryan wrote:
> > > if (err) {
> > > + if (refcount_sub_and_test(VMA_LOCK_OFFSET, &vma->vm_refcnt)) {
> > > + /* Oh cobblers. While we got a fatal signal, we
> > > + * raced with the last user. Pretend we didn't notice
> > > + * the signal
> > > + */
> > > + refcount_set(&vma->vm_refcnt, VMA_LOCK_OFFSET);
> > > + goto acquired;
> >
> > Wait, why do we consider this as a successful acquisition? The
> > vm_refcnt is 0, so this is similar situation to an earlier:
>
> > if (!refcount_add_not_zero(VMA_LOCK_OFFSET, &vma->vm_refcnt))
> > return 0;
> >
> > IOW, the vma is not referenced, so we failed to lock it. I think the
> > fix should be:
Yes, I also wondered about doing it that way. Of course, we hold the
write lock, and we found the VMA, so I don't think this can actually
occur?
> After sleeping on it, I don't think we should be masking EINTR error.
> __vma_enter_locked() result might be the only place where an outer
> loop is checking for fatal signals, so returning "failure to lock"
> instead of -EINTR might cause the loop to continue. I think this fix
> would be better:
>
> * If vma is detached then only vma_mark_attached() can raise the
> * vm_refcnt. mmap_write_lock prevents racing with vma_mark_attached().
> */
> - if (!refcount_add_not_zero(VMA_LOCK_OFFSET, &vma->vm_refcnt))
> + if (!refcount_add_not_zero(VMA_LOCK_OFFSET, &vma->vm_refcnt)) {
> + if (fatal_signal_pending(current))
> + return -EINTR;
This part seems too much to me. We don't need to check for signals
often, just when we'd otherwise sleep.
> rwsem_acquire(&vma->vmlock_dep_map, 0, 0, _RET_IP_);
> err = rcuwait_wait_event(&vma->vm_mm->vma_writer_wait,
> refcount_read(&vma->vm_refcnt) == tgt_refcnt,
> state);
> if (err) {
> + if (refcount_sub_and_test(VMA_LOCK_OFFSET, &vma->vm_refcnt)) {
> + /*
> + * No more users but fatal signal is present,
> + * still return the error.
> + */
> + }
Umm. Does the last owner of a vm_refcnt not need to do anything like
free the vma?
> rwsem_release(&vma->vmlock_dep_map, _RET_IP_);
> return err;
> }
next prev parent reply other threads:[~2025-11-26 15:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 3:42 Matthew Wilcox (Oracle)
2025-11-26 4:28 ` Suren Baghdasaryan
2025-11-26 14:26 ` Suren Baghdasaryan
2025-11-26 14:40 ` Vlastimil Babka
2025-11-26 15:01 ` Matthew Wilcox [this message]
2025-11-26 14:36 ` Vlastimil Babka
2025-11-26 15:02 ` Lorenzo Stoakes
2025-11-26 15:05 ` Matthew Wilcox
2025-11-26 15:20 ` Lorenzo Stoakes
2025-11-26 15:49 ` Suren Baghdasaryan
2025-11-26 16:00 ` Lorenzo Stoakes
2025-11-26 16:11 ` Suren Baghdasaryan
2025-11-26 16:04 ` Vlastimil Babka
2025-11-26 16:06 ` Matthew Wilcox
2025-11-26 16:18 ` Lorenzo Stoakes
2025-11-26 18:06 ` Suren Baghdasaryan
2025-11-26 18:11 ` Lorenzo Stoakes
2025-11-26 15:53 ` Vlastimil Babka
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=aScWVB_l-Hh5zGCe@casper.infradead.org \
--to=willy@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=surenb@google.com \
--cc=syzbot+5b19bad23ac7f44bf8b8@syzkaller.appspotmail.com \
--cc=vbabka@suse.cz \
/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