public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: syzbot <syzbot+556fda2d78f9b0daa141@syzkaller.appspotmail.com>
Cc: 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, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] general protection fault in lock_vma_under_rcu
Date: Thu, 5 Jun 2025 11:34:12 -0700	[thread overview]
Message-ID: <CAJuCfpGur7p19=HKkmqfD-KXf6FEbvwCV1ewFgBCGPDkoY0Wdw@mail.gmail.com> (raw)
In-Reply-To: <68342b47.a70a0220.253bc2.0090.GAE@google.com>

On Mon, May 26, 2025 at 1:50 AM syzbot
<syzbot+556fda2d78f9b0daa141@syzkaller.appspotmail.com> wrote:
>
> 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

Yeah, the fix was folded into the original patch

#syz fix: mm: replace vm_lock and detached flag with a reference count

>
> 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

      reply	other threads:[~2025-06-05 18:34 UTC|newest]

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

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='CAJuCfpGur7p19=HKkmqfD-KXf6FEbvwCV1ewFgBCGPDkoY0Wdw@mail.gmail.com' \
    --to=surenb@google.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=syzbot+556fda2d78f9b0daa141@syzkaller.appspotmail.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