From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: spkm3 removal
Date: Fri, 1 Oct 2010 17:20:14 -0400 [thread overview]
Message-ID: <20101001212014.GC1472@fieldses.org> (raw)
In-Reply-To: <1285963891.4391.0.camel@heimdal.trondhjem.org>
On Fri, Oct 01, 2010 at 04:11:31PM -0400, Trond Myklebust wrote:
> On Fri, 2010-10-01 at 15:51 -0400, J. Bruce Fields wrote:
> > Shall we go ahead and remove this?
> >
> > Somebody stumbled across a security problem in the spkm3 code
> > recently--unexploitable, as far as I can tell, since you'd need an spkm3
> > context first, and those are hard to come by.... But I feel a little
> > bad leaving this code around for innocent bystanders to waste their time
> > auditing.
>
> Agreed. Let's get rid of it.
OK, I'll give it a little more time in case anyone wants to make a case
for spkm3, then queue it up for 2.6.37--and maybe adding it to -next
will get me some email telling me what I should have done about the
defconfigs....
--b.
prev parent reply other threads:[~2010-10-01 21:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 19:51 spkm3 removal J. Bruce Fields
2010-10-01 20:11 ` Trond Myklebust
2010-10-01 21:20 ` J. Bruce Fields [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=20101001212014.GC1472@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).