From: syzbot <syzbot+d66de4cbf532749df35f@syzkaller.appspotmail.com>
To: bragathemanick0908@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [btrfs?] memory leak in btrfs_ref_tree_mod
Date: Sun, 12 Nov 2023 01:58:03 -0800 [thread overview]
Message-ID: <000000000000eb9afb0609f196ea@google.com> (raw)
In-Reply-To: <143960be-a7d7-44fc-a69f-60e1d12eacdb@gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/btrfs/ref-verify.c
Hunk #1 FAILED at 791.
Hunk #2 FAILED at 800.
2 out of 2 hunks FAILED
Tested on:
commit: 1b907d05 Merge tag '6.7-rc-smb3-client-fixes-part2' of..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=2bf8962e4f7984f4
dashboard link: https://syzkaller.appspot.com/bug?extid=d66de4cbf532749df35f
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=1652c75b680000
next parent reply other threads:[~2023-11-12 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <143960be-a7d7-44fc-a69f-60e1d12eacdb@gmail.com>
2023-11-12 9:58 ` syzbot [this message]
[not found] <ceaf0f0d-d943-4c1a-a531-5193ea64dd29@gmail.com>
2023-11-16 10:22 ` [syzbot] [btrfs?] memory leak in btrfs_ref_tree_mod syzbot
[not found] <739186bcb83d46101812b06d7e9abb80@foxhound.fi>
2023-11-13 12:28 ` syzbot
[not found] <7f87b3b9-6876-40d7-b159-94f2119851f9@gmail.com>
2023-11-12 11:52 ` syzbot
[not found] <441aa0e4-b676-4d0a-a35e-c2f7a912f987@gmail.com>
2023-11-12 10:31 ` syzbot
[not found] <077cd80b-022f-4401-a32a-33c452bd0179@gmail.com>
2023-11-12 9:23 ` syzbot
2023-08-15 9:15 syzbot
2023-11-12 13:08 ` Bragatheswaran Manickavel
2023-11-12 13:45 ` 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=000000000000eb9afb0609f196ea@google.com \
--to=syzbot+d66de4cbf532749df35f@syzkaller.appspotmail.com \
--cc=bragathemanick0908@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