From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH printk] printk_ringbuffer: Fix get_data() size sanity check
Date: Wed, 25 Mar 2026 15:22:29 +0106 [thread overview]
Message-ID: <87fr5o570i.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <acPpiJMU_pBRf8G7@pathway.suse.cz>
On 2026-03-25, Petr Mladek <pmladek@suse.com> wrote:
>> --- a/kernel/printk/printk_ringbuffer.c
>> +++ b/kernel/printk/printk_ringbuffer.c
>> @@ -1302,10 +1302,6 @@ static const char *get_data(struct prb_data_ring *data_ring,
>> return NULL;
>> }
>>
>> - /* Sanity check. Data-less blocks were handled earlier. */
>> - if (WARN_ON_ONCE(!data_check_size(data_ring, *data_size) || !*data_size))
>> - return NULL;
>> -
>> /* A valid data block will always be aligned to the ID size. */
>> if (WARN_ON_ONCE(blk_lpos->begin != ALIGN(blk_lpos->begin, sizeof(db->id))) ||
>> WARN_ON_ONCE(blk_lpos->next != ALIGN(blk_lpos->next, sizeof(db->id)))) {
>> @@ -1319,6 +1315,10 @@ static const char *get_data(struct prb_data_ring *data_ring,
>> /* Subtract block ID space from size to reflect data size. */
>> *data_size -= sizeof(db->id);
>>
>> + /* Sanity check. Data-less blocks were handled earlier. */
>> + if (WARN_ON_ONCE(!data_check_size(data_ring, *data_size) || !*data_size))
>
> The check of "!*data_size" is wrong after sizeof(db->id) subtractions.
It is not wrong. It is checking something else.
> The question is whether we still need it. As the comment says, the
> data-less block were handled earlier. And it seems that data_alloc()
> explicitly creates data-less blocks when the given size is 0.
> And prb_reserve_in_last() only allows to increase the size.
>
> IMHO, we could remove it. Wrong values will be handled by the above check:
>
> /* A valid data block will always have at least an ID. */
> if (WARN_ON_ONCE(*data_size < sizeof(db->id)))
> return NULL;
>
> A zero size datablock which is not handled using the explicit
> data-less block is not expected after all.
Well, the point of the WARN is to catch when things are broken. If for
some reason a data block of textlen 0 exists, it is a bug. I think we
should still catch it. I do not know if there are places in the code
that assume if it is a data block, it must have a textlen > 0. Probably
not, but still, it should not exist.
John
next prev parent reply other threads:[~2026-03-25 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 13:49 John Ogness
2026-03-25 13:56 ` Petr Mladek
2026-03-25 14:16 ` John Ogness [this message]
2026-03-26 9:34 ` Petr Mladek
2026-03-26 10:40 ` John Ogness
2026-03-26 12:20 ` Petr Mladek
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=87fr5o570i.fsf@jogness.linutronix.de \
--to=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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
all inboxes | Powered by JetHome®