From: Alexey Dobriyan <adobriyan@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] sysfs: upgrade OOB write by buggy .show hook into WARNing
Date: Thu, 7 May 2026 16:51:10 +0300 [thread overview]
Message-ID: <a9b349db-230d-4cd7-bc65-23257d005a5a@p183> (raw)
In-Reply-To: <2026050720-plating-cling-153a@gregkh>
On Thu, May 07, 2026 at 11:05:16AM +0200, Greg Kroah-Hartman wrote:
> On Thu, May 07, 2026 at 12:01:43PM +0300, Alexey Dobriyan wrote:
> > --- a/fs/sysfs/file.c
> > +++ b/fs/sysfs/file.c
> > @@ -70,9 +70,8 @@ static int sysfs_kf_seq_show(struct seq_file *sf, void *v)
> > * The code works fine with PAGE_SIZE return but it's likely to
> > * indicate truncated result or overflow in normal use cases.
> > */
> > - if (count >= (ssize_t)PAGE_SIZE) {
> > - printk("fill_read_buffer: %pS returned bad count\n",
> > - ops->show);
> > + if (count >= PAGE_SIZE) {
> > + WARN(1, "OOB write or bad count %zd at %pS\n", count, ops->show);
>
> This is going to be interesting to see what triggers, so I'll go queue
> this up soon.
>
> And this implies you did hit this on ext4?
The check was triggered by out-of-tree module.
ext4 is me testing the patch with a custom written buggy hook.
/sys/alexey
next prev parent reply other threads:[~2026-05-07 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 15:04 sysfs: upgrade OOB write by buggy .show hook into WARNing Alexey Dobriyan
2026-05-07 9:01 ` [PATCH] " Alexey Dobriyan
2026-05-07 9:05 ` Greg Kroah-Hartman
2026-05-07 13:51 ` Alexey Dobriyan [this message]
2026-05-07 9:28 ` Danilo Krummrich
2026-05-07 13:52 ` Alexey Dobriyan
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=a9b349db-230d-4cd7-bc65-23257d005a5a@p183 \
--to=adobriyan@gmail.com \
--cc=dakr@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rafael@kernel.org \
/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