From: syzbot <syzbot+e3385f43b2897a19be24@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, jannh@google.com,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, lorenzo.stoakes@oracle.com,
syzkaller-bugs@googlegroups.com, vbabka@suse.cz
Subject: Re: [syzbot] [mm?] general protection fault in sys_mremap
Date: Wed, 02 Apr 2025 04:46:03 -0700 [thread overview]
Message-ID: <67ed237b.050a0220.297a31.0019.GAE@google.com> (raw)
In-Reply-To: <b648feeb-d33d-4476-bdac-1d1a28eb72a1@lucifer.local>
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
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=167a694c580000
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.
next prev parent reply other threads:[~2025-04-02 11:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 0:00 [syzbot] [mm?] general protection fault in sys_mremap 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 [this message]
2025-04-02 11:49 ` Lorenzo Stoakes
2025-04-02 12:51 ` syzbot
2025-04-02 13:02 ` Lorenzo Stoakes
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=67ed237b.050a0220.297a31.0019.GAE@google.com \
--to=syzbot+e3385f43b2897a19be24@syzkaller.appspotmail.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=lorenzo.stoakes@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.