[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120417105107.GA8614@1wt.eu>
Date: Tue, 17 Apr 2012 12:51:07 +0200
From: Willy Tarreau <w@....eu>
To: Michael Kerrisk <mtk.manpages@...il.com>
Cc: netdev <netdev@...r.kernel.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
linux-api@...r.kernel.org, yoshfuji@...ux-ipv6.org,
David Miller <davem@...emloft.net>,
Jan Engelhardt <jengelh@...ozas.de>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [patch] Fix handling of overlength pathname in AF_UNIX sun_path
Hi Michael,
On Tue, Apr 17, 2012 at 10:44:15PM +1200, Michael Kerrisk wrote:
(...)
> The accompanying patch changes unix_mkname() to ensure that a terminating
> null byte is always located within the first 108 bytes of sun_path.
> It does change the ABI for the former case where a pathname ran to 108
> bytes without a null terminator: for that case, the call now fails with
> the error -EINVAL. What are people's thoughts on applying this?
My personal opinion is that (as you said), the risk of breaking existing
apps is already fairly low, but we must not deliberately break existing
apps. Eventhough there are currently a log, this is exactly what sysctls
are made for. I would personally like to have a default limit to 107 chars
+ one zero, with a sysctl option to revert to current behaviour if ever it
broke an application. In my opinion it's exactly comparable to the risk of
breaking apps with mmap_min_addr : very low risk but must be covered by a
workaround (sysctl).
Just my 2 cents,
Willy
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists