linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: akpm@linux-foundation.org
Cc: adilger.kernel@dilger.ca, wharms@bfs.de,
	xiyou.wangcong@gmail.com, eric.dumazet@gmail.com,
	segoon@openwall.com, kernel-janitors@vger.kernel.org,
	viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org, jakub@redhat.com
Subject: Re: [PATCH v2] fs: select: fix information leak to userspace
Date: Tue, 23 Nov 2010 12:22:03 -0800 (PST)	[thread overview]
Message-ID: <20101123.122203.260090992.davem@davemloft.net> (raw)
In-Reply-To: <20101123121840.e9d17d91.akpm@linux-foundation.org>

From: Andrew Morton <akpm@linux-foundation.org>
Date: Tue, 23 Nov 2010 12:18:40 -0800

> 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?

Completely agreed.

  reply	other threads:[~2010-11-23 20:21 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 [this message]
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     ` [PATCH] " Andrew Morton

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=20101123.122203.260090992.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=adilger.kernel@dilger.ca \
    --cc=akpm@linux-foundation.org \
    --cc=eric.dumazet@gmail.com \
    --cc=jakub@redhat.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=segoon@openwall.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=wharms@bfs.de \
    --cc=xiyou.wangcong@gmail.com \
    /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).