From: syzbot <syzbot+012c6245eaea0e23f7f9@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hughd@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, ziy@nvidia.com
Subject: Re: [syzbot] [mm?] general protection fault in shmem_mapping
Date: Fri, 14 Feb 2025 17:15:03 -0800 [thread overview]
Message-ID: <67afea97.050a0220.21dd3.005f.GAE@google.com> (raw)
In-Reply-To: <72BB1BE7-6EBD-45DC-ACD5-B931F5C20E0C@nvidia.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+012c6245eaea0e23f7f9@syzkaller.appspotmail.com
Tested-by: syzbot+012c6245eaea0e23f7f9@syzkaller.appspotmail.com
Tested on:
commit: df5d6180 Add linux-next specific files for 20250210
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=13bd19a4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2cd616b6e736ca7
dashboard link: https://syzkaller.appspot.com/bug?extid=012c6245eaea0e23f7f9
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=11a7a098580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-02-15 1:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 15:48 [syzbot] [mm?] general protection fault in shmem_mapping syzbot
2025-02-14 18:57 ` Zi Yan
2025-02-14 23:26 ` Zi Yan
2025-02-14 23:26 ` syzbot
2025-02-14 23:28 ` Zi Yan
2025-02-14 23:45 ` syzbot
2025-02-15 0:13 ` [syzbot] " syzbot
2025-02-15 0:48 ` Zi Yan
2025-02-15 1:15 ` syzbot [this message]
[not found] <2B47C642-0140-4981-BE7F-1E02676166B8@nvidia.com>
2025-02-15 0:42 ` syzbot
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=67afea97.050a0220.21dd3.005f.GAE@google.com \
--to=syzbot+012c6245eaea0e23f7f9@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=ziy@nvidia.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 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.