mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josh Law <joshlaw48@gmail.com>
To: Kees Cook <kees@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@intel.com>
Cc: akpm@linux-foundation.org, James.Bottomley@hansenpartnership.com,
	linux-kernel@vger.kernel.org, andy.shevchenko@gmail.com
Subject: Re: [RFC] [QUESTION] Stuff to do for string
Date: Thu, 23 Apr 2026 00:27:16 +0100	[thread overview]
Message-ID: <82482AE8-553E-4884-83D4-AE443EC9FDC5@gmail.com> (raw)
In-Reply-To: <017A12AC-0FCC-42F0-86C4-7413CE977025@kernel.org>

[Snip! :)]

>Traditionally, patches for these kinds of changes (i.e. strlcat) get split
>per subsystem or per driver, since they're not 1:1 mechanical conversions.
>
>And while I did a couple conversions recently (since I was already looking
>at the code), it's not on my active TODO right now. Feel free to tackle
>it!
>
>You can reference https://github.com/KSPP/linux/issues/370 with a Link tag
>too.

Yes, im tackling it, maybe patch series for each subsystem (e.g: 10/10
series for all files that has the function), is it fine if you do the
documentation removal at the end? (Lol you can *totally* claim all the
credit if 
you do it last)

But, the thing I am heavily intrigued in is the memscan() nuking, only like
14 files call it, it's an easy job!

But my server is not the greatest, so it takes a while for me to do
major patches like these.

Also, removing a whole function in the kernel sounds cool, (There even
was a whole YouTube video about it!)

For now, while I get my server upgraded, I'll review patches for
string, as I understand it.



Kees. Anything for this file on your TODO list you think?

  reply	other threads:[~2026-04-22 23:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 14:57 Josh Law
2026-04-22 16:12 ` Andy Shevchenko
2026-04-22 16:28   ` Josh Law
2026-04-22 16:51     ` Andy Shevchenko
2026-04-22 16:56       ` Josh Law
2026-04-22 19:23         ` Andy Shevchenko
2026-04-22 19:25           ` Josh Law
2026-04-22 23:13           ` Kees Cook
2026-04-22 23:27             ` Josh Law [this message]
2026-04-23  6:24 ` Krzysztof Kozlowski
2026-04-23  6:29   ` Josh Law
2026-04-23  6:44     ` Krzysztof Kozlowski
2026-04-23  6:46       ` Josh Law
2026-04-23  6:53         ` Krzysztof Kozlowski
2026-04-23  6:56           ` Josh Law
2026-04-23  7:11             ` Krzysztof Kozlowski
2026-04-23  7:37               ` Andy Shevchenko
2026-04-23 12:32                 ` Steven Rostedt

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=82482AE8-553E-4884-83D4-AE443EC9FDC5@gmail.com \
    --to=joshlaw48@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy.shevchenko@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®