From: syzbot <syzbot+d97580a8cceb9b03c13e@syzkaller.appspotmail.com>
To: kasong@tencent.com, linux-kernel@vger.kernel.org,
ryncsn@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] [cgroups?] kernel BUG in swap_cgroup_record (2)
Date: Mon, 12 Jan 2026 10:28:01 -0800 [thread overview]
Message-ID: <69653d31.050a0220.eaf7.00ca.GAE@google.com> (raw)
In-Reply-To: <20260112173928.74176-1-ryncsn@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+d97580a8cceb9b03c13e@syzkaller.appspotmail.com
Tested-by: syzbot+d97580a8cceb9b03c13e@syzkaller.appspotmail.com
Tested on:
commit: f417b7ff Add linux-next specific files for 20260109
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15f7b922580000
kernel config: https://syzkaller.appspot.com/x/.config?x=63a1fc1b4011ac76
dashboard link: https://syzkaller.appspot.com/bug?extid=d97580a8cceb9b03c13e
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=179939fc580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2026-01-12 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260112173928.74176-1-ryncsn@gmail.com>
2026-01-12 18:28 ` syzbot [this message]
[not found] <20260112163611.11083-2-ryncsn@gmail.com>
2026-01-12 17:23 ` [syzbot] [mm?] [cgroups?] kernel BUG in swap_cgroup_record (2) syzbot
[not found] <20260110040418.602215-1-kartikey406@gmail.com>
2026-01-10 6:40 ` syzbot
[not found] <20260110021726.601463-1-kartikey406@gmail.com>
2026-01-10 3:10 ` syzbot
[not found] <20260109162319.596850-1-kartikey406@gmail.com>
2026-01-09 17:08 ` syzbot
2026-01-09 8:57 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=69653d31.050a0220.eaf7.00ca.GAE@google.com \
--to=syzbot+d97580a8cceb9b03c13e@syzkaller.appspotmail.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryncsn@gmail.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