public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Christoph Hellwig <hch@lst.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] disallow modular capabilities
Date: Tue, 04 Jan 2005 16:09:02 -0500	[thread overview]
Message-ID: <1104872943.8346.30.camel@krustophenia.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0501041303190.2294@ppc970.osdl.org>

On Tue, 2005-01-04 at 13:05 -0800, Linus Torvalds wrote:
> 
> On Tue, 4 Jan 2005, Lee Revell wrote:
> > 
> > And I posted this to LKML almost a week ago, and a real fix was posted
> > in response.
> > 
> > http://lkml.org/lkml/2004/12/28/112
> 
> Well, I realize that it has been on bugtraq, but does that make it a real 
> concern? I'll make the tristate a boolean, but has anybody half-way sane 
> ever _done_ what is described by the bugtraq posting? IOW, it looks pretty 
> much like a made-up example, also known as a "don't do that then" kind of 
> buglet ;)

Well, a buglet is still a type of bug ;-)

What's wrong with Serge's patch?  I don't see any downside.

http://lkml.org/lkml/2004/12/29/59

Lee


      parent reply	other threads:[~2005-01-04 21:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-02 20:00 [PATCH] disallow modular capabilities Christoph Hellwig
2005-01-02 20:01 ` Christoph Hellwig
2005-01-02 20:28 ` Andi Kleen
2005-01-02 20:30   ` Christoph Hellwig
2005-01-02 20:47     ` Andi Kleen
2005-01-02 22:36       ` David Meybohm
2005-01-02 23:30         ` Andi Kleen
2005-01-03  0:21           ` David Meybohm
2005-01-03  0:32             ` Andi Kleen
2005-01-03 14:38               ` Florian Weimer
2005-01-03 15:52               ` Alan Cox
2005-01-04 20:24 ` Lee Revell
2005-01-04 21:05   ` Linus Torvalds
2005-01-04 21:08     ` Christoph Hellwig
2005-01-04 21:31       ` Chris Wright
2005-01-04 21:09     ` Lee Revell [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=1104872943.8346.30.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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