netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Kathara Sasikumar <katharasasikumar007@gmail.com>
Cc: alex.aring@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, david.hunter.linux@gmail.com,
	linux-bluetooth@vger.kernel.org, linux-wpan@vger.kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	shuah@kernel.org, skhan@linuxfoundation.org
Subject: Re: [PATCH] net: 6lowpan: replace sprintf() with scnprintf() in debugfs
Date: Sat, 6 Dec 2025 13:57:21 +0000	[thread overview]
Message-ID: <aTQ2QQKfzekZEduc@horms.kernel.org> (raw)
In-Reply-To: <20251205175324.619870-1-katharasasikumar007@gmail.com>

On Fri, Dec 05, 2025 at 05:53:24PM +0000, Kathara Sasikumar wrote:
> sprintf() does not perform bounds checking on the destination buffer and
> is deprecated in the kernel as documented in
> Documentation/process/deprecated.rst.

Hi Kathara,

Thanks for your patch.

While I do see this mentioned at [1], and I do agree with the approach
taken here, I don't see it mentioned in deprecated.rst in net-next or
Linus' tree.

[1] https://lwn.net/Articles/69419/
[2] https://lore.kernel.org/netdev/20251017094954.1402684-1-wintera@linux.ibm.com/

> 
> Replace it with scnprintf() to ensure the write stays within bounds.
> 
> No functional change intended.
> 
> Signed-off-by: Kathara Sasikumar <katharasasikumar007@gmail.com>

This patch looks like it should be targeted at net-next,
and that should be done like this.

Subject: [PATCH net-next] ...

But unfortunately net-next is currently closed.

## Form letter - net-next-closed

The merge window for v6.19 has begun and therefore net-next has closed
for new drivers, features, code refactoring and optimizations. We are
currently accepting bug fixes only.

Please repost when net-next reopens.

Due to a combination of the merge-window, travel commitments of the
maintainers, and the holiday season, net-next will re-open after
2nd January.

RFC patches sent for review only are welcome at any time.

See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle

-- 
pw-bot: changes-requested

      reply	other threads:[~2025-12-06 13:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-05 17:53 [PATCH] net: 6lowpan: replace sprintf() with scnprintf() in debugfs Kathara Sasikumar
2025-12-06 13:57 ` Simon Horman [this message]

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=aTQ2QQKfzekZEduc@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=alex.aring@gmail.com \
    --cc=davem@davemloft.net \
    --cc=david.hunter.linux@gmail.com \
    --cc=edumazet@google.com \
    --cc=katharasasikumar007@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).