mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Ahern <dsahern@kernel.org>
To: Matt Muggeridge <Matt.Muggeridge@hpe.com>, idosch@idosch.org
Cc: davem@davemloft.net, edumazet@google.com, horms@kernel.org,
	kuba@kernel.org, linux-api@vger.kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pabeni@redhat.com, stable@vger.kernel.org
Subject: Re: [PATCH net 1/1] net/ipv6: Netlink flag for new IPv6 Default Routes
Date: Wed, 6 Nov 2024 11:59:30 -0700	[thread overview]
Message-ID: <f4d16944-1b60-4824-8d63-fc2d5de1722c@kernel.org> (raw)
In-Reply-To: <20241106025056.11241-1-Matt.Muggeridge@hpe.com>

On 11/5/24 7:50 PM, Matt Muggeridge wrote:
> I'm a little surprised by this consideration. If we account for poorly
> written buggy user-programs, doesn't this open any API to an explosion
> of new attributes or other odd extensions? I'd imagine the same argument

yes, it does and there are many examples. UAPIs are hard to get right
yet persistent forever, so I do agree with Ido's push back on making
sure it is needed.


      parent reply	other threads:[~2024-11-06 18:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05  3:18 [PATCH net 0/1] " Matt Muggeridge
2024-11-05  3:18 ` [PATCH net 1/1] " Matt Muggeridge
2024-11-05 14:37   ` Nicolas Dichtel
2024-11-06  1:44     ` Matt Muggeridge
2024-11-05 18:15   ` Ido Schimmel
2024-11-06  2:50     ` Matt Muggeridge
2024-11-06 12:37       ` Ido Schimmel
2024-11-07  3:53         ` Matt Muggeridge
2024-11-07  9:52           ` Ido Schimmel
2024-11-08  2:20             ` Matt Muggeridge
2024-11-14 20:42             ` Matt Muggeridge
2024-11-06 18:59       ` David Ahern [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=f4d16944-1b60-4824-8d63-fc2d5de1722c@kernel.org \
    --to=dsahern@kernel.org \
    --cc=Matt.Muggeridge@hpe.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=idosch@idosch.org \
    --cc=kuba@kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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

all inboxes | Powered by JetHome®