From: syzbot <syzbot+1c70732df5fd4f0e4fbb@syzkaller.appspotmail.com>
To: eraykrdg1@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] memory leak in adfs_init_fs_context
Date: Sat, 13 Dec 2025 15:12:02 -0800 [thread overview]
Message-ID: <693df2c2.050a0220.326d2b.000a.GAE@google.com> (raw)
In-Reply-To: <CAHxJ8O8braxW=W1O+zXD1_z-raZiWd64awv8p69Da6TEiy1oyA@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+1c70732df5fd4f0e4fbb@syzkaller.appspotmail.com
Tested-by: syzbot+1c70732df5fd4f0e4fbb@syzkaller.appspotmail.com
Tested on:
commit: 4a298a43 Merge tag 'smp-urgent-2025-12-12' of git://gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=103d71b4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d60836e327fd6756
dashboard link: https://syzkaller.appspot.com/bug?extid=1c70732df5fd4f0e4fbb
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=104109c2580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-12-13 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHxJ8O8braxW=W1O+zXD1_z-raZiWd64awv8p69Da6TEiy1oyA@mail.gmail.com>
2025-12-13 23:12 ` syzbot [this message]
[not found] <CAHxJ8O_8-_ypES0GoCMjomJGqe7dOaXVri6DRqSwsxk52=7+XA@mail.gmail.com>
2025-12-15 0:11 ` [syzbot] [fs?] memory leak in adfs_init_fs_context syzbot
[not found] <CAHxJ8O8yTfCHD3n2P_w1G0hsgzxnsanVc=_ZAR+yeU4NwPbzSg@mail.gmail.com>
2025-12-14 22:44 ` syzbot
[not found] <CAHxJ8O_ye+G1u-ML820NOsHyAKYn4h2h7VGrd_8hAUVwyxxdAQ@mail.gmail.com>
2025-12-14 22:19 ` syzbot
[not found] <CAHxJ8O-gpHe-WzaN5pZFmsVLa_5DdY_0aKTJ6wrUaCkWEyNOSQ@mail.gmail.com>
2025-12-14 21:15 ` syzbot
2025-12-13 19:01 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=693df2c2.050a0220.326d2b.000a.GAE@google.com \
--to=syzbot+1c70732df5fd4f0e4fbb@syzkaller.appspotmail.com \
--cc=eraykrdg1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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