From: syzbot <syzbot+b0373017f711c06ada64@syzkaller.appspotmail.com>
To: kapoorarnav43@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] WARNING in ni_rename
Date: Mon, 30 Jun 2025 07:32:04 -0700 [thread overview]
Message-ID: <68629fe4.a70a0220.2f4de1.002b.GAE@google.com> (raw)
In-Reply-To: <840cee6a-44db-4c88-8501-6291f0c26486n@googlegroups.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/ntfs3/frecord.c
patch: **** unexpected end of file in patch
Tested on:
commit: 1343433e Add linux-next specific files for 20250630
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=a3d8d413c6928dae
dashboard link: https://syzkaller.appspot.com/bug?extid=b0373017f711c06ada64
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=1362988c580000
next parent reply other threads:[~2025-06-30 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <840cee6a-44db-4c88-8501-6291f0c26486n@googlegroups.com>
2025-06-30 14:32 ` syzbot [this message]
2025-07-08 21:45 [syzbot] [ntfs3?] WARNING in ni_rename Moon Hee Lee
2025-07-08 22:11 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-07-08 8:39 Moon Hee Lee
2025-07-08 9:06 ` syzbot
2025-07-08 7:54 Moonhee Lee
2025-07-08 8:13 ` syzbot
2025-07-08 8:21 ` Moon Hee Lee
2025-07-08 8:38 ` syzbot
[not found] <8b0a6266-d5c9-43e0-994d-df557fbf8f0fn@googlegroups.com>
2025-06-30 23:50 ` syzbot
[not found] <e4eb2024-f891-4548-ac08-4f224877c902n@googlegroups.com>
2025-06-30 23:45 ` syzbot
[not found] <0620687c-30d7-405d-b4f3-636546ef1823n@googlegroups.com>
2025-06-30 11:55 ` syzbot
[not found] <e13eff57-579f-4eca-9bc3-9f6ec2d5f42fn@googlegroups.com>
2025-06-30 11:21 ` syzbot
2025-06-29 9:46 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=68629fe4.a70a0220.2f4de1.002b.GAE@google.com \
--to=syzbot+b0373017f711c06ada64@syzkaller.appspotmail.com \
--cc=kapoorarnav43@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 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.