From: syzbot <syzbot+eadd98df8bceb15d7fed@syzkaller.appspotmail.com>
To: kartikey406@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] memory leak in btrfs_read_chunk_tree
Date: Wed, 10 Dec 2025 05:23:02 -0800 [thread overview]
Message-ID: <69397436.050a0220.4004e.0118.GAE@google.com> (raw)
In-Reply-To: <20251210130029.3262481-1-kartikey406@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+eadd98df8bceb15d7fed@syzkaller.appspotmail.com
Tested-by: syzbot+eadd98df8bceb15d7fed@syzkaller.appspotmail.com
Tested on:
commit: 0048fbb4 Merge tag 'locking-futex-2025-12-10' of git:/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13543a1a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=9a0268003e02068d
dashboard link: https://syzkaller.appspot.com/bug?extid=eadd98df8bceb15d7fed
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=12843a1a580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-12-10 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251210130029.3262481-1-kartikey406@gmail.com>
2025-12-10 13:23 ` syzbot [this message]
[not found] <0555a467-5aae-044b-908d-f501b44804b1@gmail.com>
2025-12-10 11:13 ` [syzbot] [btrfs?] memory leak in btrfs_read_chunk_tree syzbot
[not found] <CABBwEEg0KephZmQYmhdsUSppa1mUiu4-YQkPc29abHxqffq2sA@mail.gmail.com>
2025-12-09 17:09 ` syzbot
[not found] <CABBwEEgifDp4eHi8d8Xv-0x+qnc1gOTo5x3BFk7+McjFRctHKA@mail.gmail.com>
2025-12-09 16:55 ` syzbot
2025-12-08 8:58 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=69397436.050a0220.4004e.0118.GAE@google.com \
--to=syzbot+eadd98df8bceb15d7fed@syzkaller.appspotmail.com \
--cc=kartikey406@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