From: syzbot <syzbot+4d2aaeff9eb5a2cfec70@syzkaller.appspotmail.com>
To: almaz.alexandrovich@paragon-software.com,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ntfs3?] kernel panic: stack is corrupted in vprintk_emit
Date: Wed, 04 Sep 2024 07:19:02 -0700 [thread overview]
Message-ID: <000000000000151aa206214bdb58@google.com> (raw)
In-Reply-To: <12d6f5c8-a480-435a-8490-09e31d403e78@paragon-software.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file fs/ntfs3/super.c
Hunk #1 FAILED at 1472.
1 out of 1 hunk FAILED
Tested on:
commit: 689ecd06 fs/ntfs3: Rename ntfs3_setattr into ntfs_seta..
git tree: https://github.com/Paragon-Software-Group/linux-ntfs3.git master
kernel config: https://syzkaller.appspot.com/x/.config?x=7229118d88b4a71b
dashboard link: https://syzkaller.appspot.com/bug?extid=4d2aaeff9eb5a2cfec70
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=12041339980000
next parent reply other threads:[~2024-09-04 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <12d6f5c8-a480-435a-8490-09e31d403e78@paragon-software.com>
2024-09-04 14:19 ` syzbot [this message]
[not found] <20240910070746.7269-1-almaz.alexandrovich@paragon-software.com>
2024-09-10 7:25 ` [syzbot] [ntfs3?] kernel panic: stack is corrupted in vprintk_emit syzbot
[not found] <20240904142214.13333-1-almaz.alexandrovich@paragon-software.com>
2024-09-04 14:37 ` syzbot
[not found] <20240902124544.6293-1-almaz.alexandrovich@paragon-software.com>
2024-09-02 13:20 ` syzbot
[not found] <20240902124358.6201-1-almaz.alexandrovich@paragon-software.com>
2024-09-02 13:04 ` syzbot
[not found] <41ccdc3a-7259-4fcd-88bb-07590d278d19@paragon-software.com>
2024-09-02 12:29 ` syzbot
2024-08-16 13:07 syzbot
2024-08-27 7:27 ` Edward Adam Davis
2024-08-27 7:50 ` 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=000000000000151aa206214bdb58@google.com \
--to=syzbot+4d2aaeff9eb5a2cfec70@syzkaller.appspotmail.com \
--cc=almaz.alexandrovich@paragon-software.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