From: Dmitry Vyukov <dvyukov@google.com>
To: twuufnxlz@gmail.com
Cc: akpm@linux-foundation.org, hughd@google.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org,
syzbot+4a2376bc62e59406c414@syzkaller.appspotmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] fs/hfsplus: expand s_vhdr_buf size to avoid slab oob
Date: Thu, 4 Jul 2024 16:05:20 +0200 [thread overview]
Message-ID: <20240704140520.1178714-1-dvyukov@google.com> (raw)
In-Reply-To: <20230926102454.992535-2-twuufnxlz@gmail.com>
Hi Edward,
Was this patch lost? I don't see it merged anywhere.
This bug is still present in most kernels out there.
next prev parent reply other threads:[~2024-07-04 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000820e380606161640@google.com>
2023-09-26 10:24 ` Edward AD
2024-07-04 14:05 ` Dmitry Vyukov [this message]
2025-05-04 9:52 ` [syzbot] [hfs?] [mm?] KASAN: slab-out-of-bounds Read in generic_perform_write 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=20240704140520.1178714-1-dvyukov@google.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+4a2376bc62e59406c414@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=twuufnxlz@gmail.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