From: Andrew Morton <akpm@linux-foundation.org>
To: Andreas Dilger <adilger.kernel@dilger.ca>
Cc: Vasiliy Kulikov <segooon@gmail.com>,
kernel-janitors@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs: select: fix information leak to userspace
Date: Sun, 14 Nov 2010 18:05:05 -0800 [thread overview]
Message-ID: <20101114180505.674c7da0.akpm@linux-foundation.org> (raw)
In-Reply-To: <8D90F8B2-EA29-4EB9-9807-294CE0D5523B@dilger.ca>
On Sat, 13 Nov 2010 14:38:19 -0700 Andreas Dilger <adilger.kernel@dilger.ca> wrote:
> On 2010-11-12, at 13:08, Andrew Morton wrote:
> > On Wed, 10 Nov 2010 23:38:02 +0300
> > Vasiliy Kulikov <segooon@gmail.com> wrote:
> >> On some architectures __kernel_suseconds_t is int.
> >
> > On sparc and parisc. On all other architectures this patch is a waste
> > of cycles.
> >
> > --- a/fs/select.c~fs-select-fix-information-leak-to-userspace-fix
> > +++ a/fs/select.c
> > @@ -306,7 +306,8 @@ static int poll_select_copy_remaining(st
> > rts.tv_sec = rts.tv_nsec = 0;
> >
> > if (timeval) {
> > - memset(&rtv, 0, sizeof(rtv));
> > + if (sizeof(rtv) > sizeof(rtv.tv_sec) + sizeof(rtv.tv_usec))
> > + memset(&rtv, 0, sizeof(rtv));
> > rtv.tv_sec = rts.tv_sec;
> > rtv.tv_usec = rts.tv_nsec / NSEC_PER_USEC;
> >
> > _
> >
> >
> > The `if' gets eliminated at compile time. With this approach we add
> > four bytes of text to the sparc64 build and zero bytes of text to the
> > x86_64 build.
>
> It's nice to have comments (or at least a good commit message) for unusual code like this, so that in the future it is clear when this kind of workaround can be removed (e.g. if the time_t is changed to always be a 64-bit value for Y2038 issues, even on 32-bit arches).
>
Well, I'm the resident comment fanatic, but I thought this was all
sufficiently obvious to not need one. But I'll add one ;)
prev parent reply other threads:[~2010-11-15 2:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 20:38 [PATCH] fs: select: fix information leak to userspace Vasiliy Kulikov
2010-11-12 20:08 ` Andrew Morton
2010-11-13 21:38 ` Andreas Dilger
2010-11-14 9:25 ` [PATCH v2] " Vasiliy Kulikov
2010-11-15 2:06 ` Andrew Morton
2010-11-15 19:12 ` Eric Dumazet
2010-11-16 11:19 ` Boaz Harrosh
2010-11-22 23:50 ` Andrew Morton
2010-11-23 0:20 ` Eric Dumazet
2010-11-23 0:32 ` Andrew Morton
2010-11-23 5:12 ` Dan Carpenter
2010-11-23 6:59 ` Eric Dumazet
2010-11-23 14:01 ` Américo Wang
2010-11-23 14:45 ` walter harms
2010-11-23 15:23 ` Américo Wang
2010-11-23 18:02 ` Andreas Dilger
2010-11-23 20:18 ` Andrew Morton
2010-11-23 20:22 ` David Miller
2010-11-24 0:24 ` Andreas Dilger
2010-11-24 16:06 ` walter harms
2010-11-24 10:44 ` Pádraig Brady
2010-11-24 11:05 ` Américo Wang
2010-11-24 11:46 ` Pádraig Brady
2010-11-24 12:32 ` Américo Wang
2010-12-15 9:49 ` Al Viro
2010-12-15 20:30 ` Andreas Dilger
2010-12-15 20:33 ` Julia Lawall
2010-12-15 20:52 ` Eric Dumazet
2010-12-15 22:19 ` Andreas Dilger
2010-12-16 9:39 ` Boaz Harrosh
2010-11-24 17:54 ` Valdis.Kletnieks
2010-11-16 18:45 ` Vasiliy Kulikov
2010-11-15 2:05 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101114180505.674c7da0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adilger.kernel@dilger.ca \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=segooon@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).