From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: Leon Romanovsky <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Honggang LI <honli@redhat.com>,
Gal Pressman <galpress@amazon.com>
Subject: Re: RDMA device renames and node description
Date: Tue, 18 Feb 2020 16:08:33 -0400 [thread overview]
Message-ID: <20200218200833.GH31668@ziepe.ca> (raw)
In-Reply-To: <1fcc873b-3f67-2325-99cc-21d90edd2058@intel.com>
On Tue, Feb 18, 2020 at 12:11:47PM -0500, Dennis Dalessandro wrote:
> > First option is to rely on distro and every distro behaves differently
> > in such cases, some of them won't change anything till their last user
> > dies :) and others more dynamic with more up-to-date packages already
> > adopted our default.
>
> This is the issue I see. The problem is when the distro doesn't know any
> better and pulls in a new rdma-core and breaks things unintentionally. Up to
> date is good, but up to date that brings with it what is essentially an ABI
> breakage is not.
The point of having the distros update is to get the breakage
fixed. Fedora, Ubuntu, etc should all track upstream and resolve
breakage through their bug process.
Remember, at the time this was set out nobody came forward to say that
there was distro-included userspace that (wrongly) hard coded
names. Now it is a bit late to backtrack - we need to move forward
with fixed userspace..
Jason
next prev parent reply other threads:[~2020-02-18 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 18:13 RDMA device renames and node description Dennis Dalessandro
2020-02-18 14:04 ` Leon Romanovsky
2020-02-18 17:11 ` Dennis Dalessandro
2020-02-18 20:08 ` Jason Gunthorpe [this message]
2020-02-19 7:11 ` Leon Romanovsky
2020-02-19 14:14 ` Dennis Dalessandro
2020-02-19 14:35 ` Gal Pressman
2020-02-19 15:10 ` Leon Romanovsky
2020-02-19 16:54 ` Jason Gunthorpe
2020-02-19 14:48 ` Leon Romanovsky
2020-02-19 15:34 ` Dennis Dalessandro
2020-02-19 16:58 ` Jason Gunthorpe
2020-02-19 19:35 ` Dennis Dalessandro
2020-02-19 23:18 ` Ira Weiny
2020-02-20 2:26 ` Dennis Dalessandro
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=20200218200833.GH31668@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dennis.dalessandro@intel.com \
--cc=galpress@amazon.com \
--cc=honli@redhat.com \
--cc=leon@kernel.org \
--cc=linux-rdma@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;
as well as URLs for NNTP newsgroup(s).