From: syzbot <syzbot+b9529ebe6a9394ddf825@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, neganhat@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [ecryptfs?] KASAN: slab-out-of-bounds Read in ecryptfs_verify_auth_tok_from_key
Date: Wed, 16 Sep 2026 19:48:01 -0700 [thread overview]
Message-ID: <6aab54e1.b398a7c9.1f86be.000c.GAE@google.com> (raw)
In-Reply-To: <CAFJkwZxO+=cYaCFSAEejhBgJeiJczxuua1y0+Dcs1Fj5Sg_vaw@mail.gmail.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
error: corrupt patch at line 4
Tested on:
commit: 238650ef Merge tag 'powerpc-7.3-4' of git://git.kernel..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=e909ffe6b35dddb7
dashboard link: https://syzkaller.appspot.com/bug?extid=b9529ebe6a9394ddf825
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=103258c9580000
next parent reply other threads:[~2026-09-17 2:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFJkwZxO+=cYaCFSAEejhBgJeiJczxuua1y0+Dcs1Fj5Sg_vaw@mail.gmail.com>
2026-09-17 2:48 ` syzbot [this message]
[not found] <CAFJkwZw8hjL7xSTayRqbVS37RYYENU5XFTgT0b90J05dG3gVXg@mail.gmail.com>
2026-09-17 4:39 ` syzbot
[not found] <CAFJkwZzcu4-z0b+nc4Ki0DjaL3=DWfE7mXgfjL0VK6RL8AK36w@mail.gmail.com>
2026-09-17 3:52 ` syzbot
[not found] <CAFJkwZx1RyUmXg4RNqQPKVCdyu4-N_4G_JhtL7xGihU5RFnnqw@mail.gmail.com>
2026-09-17 3:31 ` syzbot
[not found] <CAFJkwZxNQWU=x4gLojE-jhi82Y4hFj=p2wrK6QK2EBCf69r3nQ@mail.gmail.com>
2026-09-17 3:06 ` syzbot
[not found] <CAFJkwZw6b0pX7rft72ke0A3d1UauhQR5kh+tWXg9xKT4CDikEg@mail.gmail.com>
2026-09-17 2:56 ` syzbot
2026-09-16 15:53 syzbot
2026-09-17 1:53 ` Edward Adam Davis
2026-09-17 2:10 ` syzbot
2026-09-17 2:22 ` Edward Adam Davis
2026-09-17 2:46 ` syzbot
2026-09-17 3:39 ` Edward Adam Davis
2026-09-17 4:15 ` 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=6aab54e1.b398a7c9.1f86be.000c.GAE@google.com \
--to=syzbot+b9529ebe6a9394ddf825@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neganhat@gmail.com \
--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
all inboxes | Powered by JetHome®