linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+556fda2d78f9b0daa141@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, asml.silence@gmail.com,
	axboe@kernel.dk,  eadavis@qq.com, io-uring@vger.kernel.org,
	linux-kernel@vger.kernel.org,  linux-mm@kvack.org,
	shivankg@amd.com, surenb@google.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in lock_vma_under_rcu
Date: Mon, 26 May 2025 01:50:15 -0700	[thread overview]
Message-ID: <68342b47.a70a0220.253bc2.0090.GAE@google.com> (raw)
In-Reply-To: <67bd7af0.050a0220.bbfd1.009e.GAE@google.com>

This bug is marked as fixed by commit:
mm: fix a crash due to vma_end_read() that should have been removed

But I can't find it in the tested trees[1] for more than 90 days.
Is it a correct commit? Please update it by replying:

#syz fix: exact-commit-title

Until then the bug is still considered open and new crashes with
the same signature are ignored.

Kernel: Linux
Dashboard link: https://syzkaller.appspot.com/bug?extid=556fda2d78f9b0daa141

---
[1] I expect the commit to be present in:

1. for-kernelci branch of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git

2. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git

3. master branch of
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git

4. main branch of
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git

The full list of 10 trees can be found at
https://syzkaller.appspot.com/upstream/repos


  parent reply	other threads:[~2025-05-26  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25  8:10 [syzbot] [io-uring?] [mm?] " syzbot
2025-02-25  8:50 ` Shivank Garg
2025-05-26  8:50 ` syzbot [this message]
2025-06-05 18:34   ` [syzbot] " Suren Baghdasaryan

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=68342b47.a70a0220.253bc2.0090.GAE@google.com \
    --to=syzbot+556fda2d78f9b0daa141@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=eadavis@qq.com \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=shivankg@amd.com \
    --cc=surenb@google.com \
    --cc=syzkaller-bugs@googlegroups.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