Re: [PATCH v2] fs: select: fix information leak to userspace
[Posted December 1, 2010 by corbet]
| From: |
| Andrew Morton <akpm-AT-linux-foundation.org> |
| To: |
| Andreas Dilger <adilger.kernel-AT-dilger.ca> |
| Subject: |
| Re: [PATCH v2] fs: select: fix information leak to userspace |
| Date: |
| Tue, 23 Nov 2010 12:18:40 -0800 |
| Message-ID: |
| <20101123121840.e9d17d91.akpm@linux-foundation.org> |
| Cc: |
| wharms-AT-bfs.de,
=?ISO-8859-1?Q?Am=E9rico?= Wang <xiyou.wangcong-AT-gmail.com>,
Eric Dumazet <eric.dumazet-AT-gmail.com>,
Vasiliy Kulikov <segoon-AT-openwall.com>,
kernel-janitors-AT-vger.kernel.org,
Alexander Viro <viro-AT-zeniv.linux.org.uk>,
linux-fsdevel-AT-vger.kernel.org, linux-kernel-AT-vger.kernel.org,
Jakub Jelinek <jakub-AT-redhat.com> |
| Archive‑link: | |
Article |
On Tue, 23 Nov 2010 11:02:44 -0700
Andreas Dilger <adilger.kernel@dilger.ca> wrote:
> On 2010-11-23, at 07:45, walter harms wrote:
> > Maybe we can convince the gcc people to make 0 padding default. That will not solve the
problems for other compilers but when they claim "works like gcc" we can press then to support this
also. I can imagine that this will close some other subtle leaks also.
>
> It makes the most sense to tackle this at the GCC level, since the added overhead of doing
memset(0) on the whole struct may be non-trivial for commonly-used and/or large structures.
(My, what long lines you have!)
We can't reasonably address this with gcc changes. If gcc starts doing
what we want in the next release, how long will it be until that
release is the *oldest* version of gcc which the kernel may be compiled
with? Five years?
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
