From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: compat: autofs v5 packet size ambiguity - update Date: Wed, 22 Feb 2012 09:45:56 -0800 Message-ID: <4F4529D4.6070008@zytor.com> References: <20120221.221609.218135609185671883.davem@davemloft.net> <1329889428.2193.45.camel@perseus.themaw.net> <4F4484F0.9070501@zytor.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Linus Torvalds Cc: Ian Kent , David Miller , linux-kernel@vger.kernel.org, autofs@vger.kernel.org, Thomas Meyer , Al Viro On 02/22/2012 08:10 AM, Linus Torvalds wrote: > > But yeah, writing fixed-size data and then having a reader that reads > fixed-size data is just not a very good approach. It's doubly bad when > the "fixed size" isn't an explicit size that is documented in the > protocol, but depends on data structures. > Incidentally, a valid user space workaround for this problem would be to just read all the data off the pipe but consider the packet length to be NAME_MAX rather than NAME_MAX+1; then simply discard all-zero ints received on input since a packet always starts with the autofs version number. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.