From: David Miller <davem@davemloft.net>
To: torvalds@linux-foundation.org
Cc: mschmidt@redhat.com, netdev@vger.kernel.org,
stephen@networkplumber.org, alexander.h.duyck@intel.com,
michael.riesch@omicron.at
Subject: Re: [PATCH net] rtnetlink: fix userspace API breakage for iproute2 < v3.9.0
Date: Thu, 12 Jun 2014 10:47:35 -0700 (PDT) [thread overview]
Message-ID: <20140612.104735.11248268473559858.davem@davemloft.net> (raw)
In-Reply-To: <CA+55aFxQMw0s1N2SspU-DWbZ-h4mho4dVFrX5qm=ZHKrsUGbmw@mail.gmail.com>
From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Thu, 12 Jun 2014 10:44:49 -0700
> David, I have to agree with Michal. If the user-space tool did what it
> had to do for old kernels, then new kernels should support the old
> semantics.
>
> You can't call it a "bug" - user space does what it does and it was
> tested and worked.
>
> And sure, it might have been a bug/misfeature of the old kernel, but
> we have to live with what we have done, not blame others. Once user
> space starts depending on our bugs, it's *our* problem.
>
> Saying "fix your sh*t" is wrong, when we caused it to begin with.
Yeah I guess you're right and I'll end up applying Michal's patch.
next prev parent reply other threads:[~2014-06-12 17:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 12:15 [PATCH net] rtnetlink: fix userspace API breakage for iproute2 < v3.9.0 Michal Schmidt
2014-05-31 0:42 ` David Miller
2014-06-03 12:21 ` Michal Schmidt
2014-06-12 14:13 ` Michal Schmidt
2014-06-12 17:43 ` David Miller
2014-06-12 17:44 ` Linus Torvalds
2014-06-12 17:47 ` David Miller [this message]
2014-06-12 18:01 ` Linus Torvalds
2014-06-12 18:22 ` David Miller
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=20140612.104735.11248268473559858.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexander.h.duyck@intel.com \
--cc=michael.riesch@omicron.at \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=torvalds@linux-foundation.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).