From: syzbot <syzbot+fa88eb476e42878f2844@syzkaller.appspotmail.com>
To: kapoorarnav43@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [fs?] KASAN: use-after-free Read in hpfs_get_ea
Date: Fri, 18 Jul 2025 18:19:02 -0700 [thread overview]
Message-ID: <687af286.a00a0220.3af5df.0033.GAE@google.com> (raw)
In-Reply-To: <8b62af1c-64f0-4742-a96b-34d23635c089n@googlegroups.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/hpfs/ea.c
Hunk #1 succeeded at 135 with fuzz 1.
patch: **** malformed patch at line 61: + }
Tested on:
commit: 414aaef1 Merge tag 'riscv-for-linus-6.16-rc7' of git:/..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f09d04131ef56b22
dashboard link: https://syzkaller.appspot.com/bug?extid=fa88eb476e42878f2844
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=1165038c580000
next parent reply other threads:[~2025-07-19 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8b62af1c-64f0-4742-a96b-34d23635c089n@googlegroups.com>
2025-07-19 1:19 ` syzbot [this message]
2025-07-20 12:34 [PATCH] hpfs: add checks for ea addresses Antoni Pokusinski
2025-07-20 13:49 ` [syzbot] [fs?] KASAN: use-after-free Read in hpfs_get_ea syzbot
[not found] <CAMp3bLWE1Q17He7mzu8S-VTe9Sackn8YryD6L0msjyPpifmyBg@mail.gmail.com>
2025-07-20 7:49 ` syzbot
[not found] <CAMp3bLXKFqL5nkRkTVBNOKv968bK61yAT=b1wkoz+SZqtk0yiQ@mail.gmail.com>
2025-07-20 7:12 ` syzbot
[not found] <CAMp3bLVwzu1F+BAYf=UbNXqDq-8H6NjtxUXe+ChNO9_bu7tN8g@mail.gmail.com>
2025-07-19 8:21 ` syzbot
[not found] <62d528e9-2414-4e50-8e3f-c4cac3526858n@googlegroups.com>
2025-07-18 13:27 ` syzbot
[not found] <df725c07-3ee4-477d-b4d6-21fb4afc61a8n@googlegroups.com>
2025-07-18 12:40 ` syzbot
-- strict thread matches above, loose matches on Subject: below --
2025-07-17 19:14 syzbot
2025-10-14 11:12 ` Tetsuo Handa
2025-10-14 12:23 ` 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=687af286.a00a0220.3af5df.0033.GAE@google.com \
--to=syzbot+fa88eb476e42878f2844@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.