The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: David Laight <david.laight.linux@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
	David Ahern <dsahern@kernel.org>,
	 Ido Schimmel <idosch@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	 Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
	 netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com,  stable@vger.kernel.org,
	Stanislav Fomichev <sdf@fomichev.me>
Subject: Re: [PATCH net 1/2] ipv4: mcast: getsockopt: do not overwrite past optlen
Date: Thu, 13 Aug 2026 07:49:17 -0700	[thread overview]
Message-ID: <an3Y2JUyT-DNcYar@gmail.com> (raw)
In-Reply-To: <20260811185127.0343b75b@pumpkin>

On Tue, Aug 11, 2026 at 06:51:27PM +0100, David Laight wrote:
> I would suggest (again) that these changes be done starting with the syscall
> 'glue' and adding an extra getsockopt_new() to the function call table(s).
> Then changing the protocols one by one to provide the new function and
> finally deleting the old entry.
> That way each protocol code only needs changing once.

Isn't this basically what we're doing today, without a new syscall?

> I'd also wrap the copy_to_iter() in an inline function so that most code
> doesn't have to care about the implementation.

That sounds doable. What would this inline function look like?
Would you mind sharing what you have in mind?

Thanks for the discussion,
--breno

  reply	other threads:[~2026-08-13 14:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06  9:41 [PATCH net 0/2] net: mcast: do not write past optlen in the source filter getsockopt Breno Leitao
2026-08-06  9:42 ` [PATCH net 1/2] ipv4: mcast: getsockopt: do not overwrite past optlen Breno Leitao
2026-08-07 16:44   ` David Laight
2026-08-10 12:48     ` Breno Leitao
2026-08-10 21:21       ` David Laight
2026-08-11 12:19         ` Breno Leitao
2026-08-11 15:15           ` Jakub Kicinski
2026-08-11 17:51             ` David Laight
2026-08-13 14:49               ` Breno Leitao [this message]
2026-08-13 14:46             ` Breno Leitao
2026-08-06  9:42 ` [PATCH net 2/2] ipv6: mcast: do not write past optlen in the source filter getsockopt Breno Leitao
2026-08-07 16:44   ` David Laight
2026-08-07 14:38 ` [PATCH net 0/2] net: " Simon Horman

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=an3Y2JUyT-DNcYar@gmail.com \
    --to=leitao@debian.org \
    --cc=davem@davemloft.net \
    --cc=david.laight.linux@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=stable@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