linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: syzbot <syzbot+e3385f43b2897a19be24@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, jannh@google.com,
	liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, syzkaller-bugs@googlegroups.com,
	vbabka@suse.cz
Subject: Re: [syzbot] [mm?] general protection fault in sys_mremap
Date: Wed, 2 Apr 2025 14:02:54 +0100	[thread overview]
Message-ID: <bee2d5f5-db93-42f1-829e-3fd250649ca8@lucifer.local> (raw)
In-Reply-To: <67ed32b6.050a0220.297a31.001a.GAE@google.com>

On Wed, Apr 02, 2025 at 05:51:02AM -0700, syzbot wrote:
> Hello,
>
> syzbot has tested the proposed patch but the reproducer is still triggering an issue:
> unregister_netdevice: waiting for DEV to become free
>
> unregister_netdevice: waiting for batadv0 to become free. Usage count = 3

OK so this looks like a broken test box.

For belts and suspenders purposes, I confirmed this repro, and the previously
reported one both work fine on mm-stable.

All is good, the issue is resolved :) just a matter of waiting for the merge to
mainline for this.

#syz fix: mm/mremap: do not set vrm->vma NULL immediately prior to checking it

>
>
> Tested on:
>
> commit:         e20706d5 mseal sysmap: add arch-support txt
> git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git/ mm-stable
> console output: https://syzkaller.appspot.com/x/log.txt?x=13bf9998580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=ccf540055069887f
> dashboard link: https://syzkaller.appspot.com/bug?extid=e3385f43b2897a19be24
> compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
>
> Note: no patches were applied.


  reply	other threads:[~2025-04-02 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02  0:00 syzbot
2025-04-02 10:01 ` syzbot
2025-04-02 10:19   ` Lorenzo Stoakes
2025-04-02 10:20     ` syzbot
2025-04-02 10:22       ` Lorenzo Stoakes
2025-04-02 11:46         ` syzbot
2025-04-02 11:49           ` Lorenzo Stoakes
2025-04-02 12:51             ` syzbot
2025-04-02 13:02               ` Lorenzo Stoakes [this message]
2025-04-02 22:31     ` Andrew Morton

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=bee2d5f5-db93-42f1-829e-3fd250649ca8@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=jannh@google.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzbot+e3385f43b2897a19be24@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.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