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]

Date:	Fri, 27 Apr 2012 12:19:56 -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 12:16 PM, David Miller <davem@...emloft.net> wrote:
>
> BTW, I want to clarify that my position is that userland might have
> been the best place to handle this rather than the kernel.

It definitely is not.

You are ignoring the fact that the user-land workaround resulted in an
independent bug in *another* user-land project.

Your whole argument was apparently that "that point in user-land is
the only place that knows the details". But that argument is bogus
crap - and we can *see* that it is bogus crap by the fact that there
was *another* user-land place that had this problem, but didn't
realize it.

That's why fixing it in user land was always wrong. There isn't just a
single user of this interface!

Btw, I think I may have an alternate fix. Which is to simply add a
"packetized" mode to pipes.

                   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/