linux-kernel - Re: [PATCH v2] Introduce a version6 of autofs interface, to fix design error.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFwvFaxBT8Mdp5s4-6Gxy7nM4WVzbWna4RF_OUK3hnx+jQ@mail.gmail.com>
Date:	Fri, 27 Apr 2012 11:42:58 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	David Miller <davem@...emloft.net>
Cc:	mjt@....msk.ru, linux-kernel@...r.kernel.org,
	autofs@...r.kernel.org, raven@...maw.net, thomas@...3r.de,
	stable@...nel.org
Subject: Re: [PATCH v2] Introduce a version6 of autofs interface, to fix
 design error.

On Fri, Apr 27, 2012 at 11:34 AM, David Miller <davem@...emloft.net> wrote:
>
> If systemd wants to use version 5 of this thing, it has to have the
> same workaround code automountd has.  It is systemd (and now the
> kernel) which is broken.

There's no question that systemd is broken.

But those broken binaries are out in the wild. End of story.

> We should have never touched version 5 of the data-structure.  Having
> 5 years of workaround precedence in userspace proves this.

Umm. The thing is, those broken binaries *work* on 32-bit.  They were
*tested* on 32-bit. They were *shipped* on 32-bit.

And we really do want to make it just work for people to build 64-bit
kernels. It is simply not acceptably to say "hey, you have 32-bit user
land, so use a 32-bit kernel". It's not a different ABI, never has
been.

It's entirely pointless to talk about some next version. THAT FIXES
NOTHING. What's so hard to understand? This is an existing problem,
and making a v6 DOES NOT FIX ANYTHING AT ALL.

And people who bring it up as a "fix" are entirely missing the point.

Seriously.

                      Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/