From: Leon Romanovsky <leon@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ksummit-discuss@lists.linux-foundation.org
Subject: Re: [Ksummit-discuss] [MAINTAINERS SUMMIT] Driver and/or module versions
Date: Sun, 25 Jun 2017 21:19:54 +0300 [thread overview]
Message-ID: <20170625181954.GU1248@mtr-leonro.local> (raw)
In-Reply-To: <CA+55aFx9A=5cc0QZ7CySC4F2K7eYaEfzkdYEc9JaNgCcV25=rg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
On Sun, Jun 25, 2017 at 10:32:52AM -0700, Linus Torvalds wrote:
> On Sun, Jun 25, 2017 at 12:24 AM, Leon Romanovsky <leon@kernel.org> wrote:
> > There is a steady flow of patches which bump driver and module versions.
> >
> > * Can we come with unified policy about those patches?
>
> We pretty much *have* a unified policy, it's just that I think rdma is crazy.
>
> The unified policy is pretty much that version codes do not matter, do
> not exist, and do not get updated.
I'm pretty sure that not everyone is aware of it. Those examples of
"accepted" patches are not from RDMA and maybe it will be awkward to hear,
but in RDMA subsystem we don't allow such patches [1].
My attempt to enforce such policy in other subsystem didn't work [2] and
in addition to that failed attempt, I bombarded internally with customers'
requests who have cargo cult to update those versions anyway ("like everyone else").
This is why I'm proposing to ban those patches and remove their exposure for
the drivers/* completely.
>
> Things are supposed to be backwards and forwards compatible, because
> we don't accept breakage in user space anyway. So versioning is
> pointless, and only causes problems.
>
> It causes problems not just because of the conflict issues, but
> because it's fundamentally wrong, and makes driver writers think that
> it's ok to change interfaces and use versioning to show they changed.
> It's *not* OK.
Great, so why are we continuing to allow patches with MODULE_VERSION and
DRIVER_VERSION changes?
>
> Sometimes you have feature masks (which just mean that it's ok to
> _add_ interfaces rather than change them, and make it possible for
> user space to check if the new interface exists), but even that is
> generally the exception rather than the rule and should be used very
> very carefully and preferably not at all.
[1] https://patchwork.kernel.org/patch/9735855/
[2] https://lkml.org/lkml/2016/7/15/17
>
> Linus
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-25 18:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 7:24 Leon Romanovsky
2017-06-25 17:32 ` Linus Torvalds
2017-06-25 18:19 ` Leon Romanovsky [this message]
2017-06-25 18:37 ` Linus Torvalds
2017-06-25 19:05 ` Leon Romanovsky
2017-06-25 21:32 ` Alexandre Belloni
2017-06-26 4:51 ` Leon Romanovsky
2017-06-26 6:47 ` Geert Uytterhoeven
2017-06-26 5:00 ` Greg KH
2017-06-26 6:03 ` Leon Romanovsky
2017-06-26 15:21 ` Levin, Alexander (Sasha Levin)
2017-06-26 18:25 ` Leon Romanovsky
2017-06-30 16:21 ` Darren Hart
2017-07-03 20:41 ` Jiri Kosina
2017-07-03 21:25 ` Darren Hart
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=20170625181954.GU1248@mtr-leonro.local \
--to=leon@kernel.org \
--cc=ksummit-discuss@lists.linux-foundation.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