From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Joanne Koong <joannelkoong@gmail.com>,
"amurray @ thegoodpenguin . co . uk"
<amurray@thegoodpenguin.co.uk>,
brauner@kernel.org, chao@kernel.org, djwong@kernel.org,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH 0/2] printk_ringbuffer: Fix regression in get_data() and clean up data size checks
Date: Mon, 10 Nov 2025 13:25:18 +0100 [thread overview]
Message-ID: <aRHZrgMXUeMMY_gf@pathway.suse.cz> (raw)
In-Reply-To: <20251107194720.1231457-1-pmladek@suse.com>
On Fri 2025-11-07 20:47:18, Petr Mladek wrote:
> This is outcome of the long discussion about the regression caused
> by 67e1b0052f6bb82 ("printk_ringbuffer: don't needlessly wrap data blocks around"),
> see https://lore.kernel.org/all/69096836.a70a0220.88fb8.0006.GAE@google.com/
>
> The 1st patch fixes the regression as agreed, see
> https://lore.kernel.org/all/87ecqb3qd0.fsf@jogness.linutronix.de/
>
> The 2nd patch adds a helper function to unify the checks whether
> a more space is needed. I did my best to address all the concerns
> about various proposed variants.
>
> Note that I called the new helper function "need_more_space()" in the end.
> It avoids all the problems with "before" vs. "lt" vs "le",
> and "_safe" vs. "_sane" vs. "_bounded".
>
> IMHO, the name "need_more_space()" fits very well in all three
> locations, surprisingly even in data_realloc(). But it is possible
> that you disagree. Let me know if you hate it ;-)
>
>
> The patchset applies on top of printk/linux.git, branch for-6.19.
> It should apply on top of linux-next as well.
>
> Petr Mladek (2):
> printk_ringbuffer: Fix check of valid data size when blk_lpos
> overflows
> printk_ringbuffer: Create a helper function to decide whether a more
> space is needed
>
> kernel/printk/printk_ringbuffer.c | 40 +++++++++++++++++++++++++------
> 1 file changed, 33 insertions(+), 7 deletions(-)
JFYI, the patchset has been comitted into printk/linux.git,
branch for-6.19.
Note that I have updated the Subject and a comment in the 2nd patch
as suggested by John, see
https://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git/commit/?h=for-6.19&id=394aa576c0b783ae728d87ed98fe4f1831dfd720
Best Regards,
Petr
next prev parent reply other threads:[~2025-11-10 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 19:47 Petr Mladek
2025-11-07 19:47 ` [PATCH 1/2] printk_ringbuffer: Fix check of valid data size when blk_lpos overflows Petr Mladek
2025-11-10 9:13 ` John Ogness
2025-11-07 19:47 ` [PATCH 2/2] printk_ringbuffer: Create a helper function to decide whether a more space is needed Petr Mladek
2025-11-10 9:21 ` John Ogness
2025-11-10 12:25 ` Petr Mladek [this message]
2025-12-09 17:18 ` [f2fs-dev] [PATCH 0/2] printk_ringbuffer: Fix regression in get_data() and clean up data size checks patchwork-bot+f2fs
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=aRHZrgMXUeMMY_gf@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=amurray@thegoodpenguin.co.uk \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=joannelkoong@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@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
Powered by JetHome