From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Serge E. Hallyn" <serue@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
James Morris <jmorris@namei.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
jeffschroeder@computer.org, Chris Wright <chrisw@sous-sol.org>,
Karl MacMillan <kmacmillan@mentalrootkit.com>,
KaiGai Kohei <kaigai@kaigai.gr.jp>
Subject: Re: [PATCH 0/2] file capabilities: Introduction
Date: Thu, 17 May 2007 11:27:47 +0530 [thread overview]
Message-ID: <20070517055747.GA15474@in.ibm.com> (raw)
In-Reply-To: <20070514200011.GB3969@ucw.cz>
On Mon, May 14, 2007 at 08:00:11PM +0000, Pavel Machek wrote:
> Hi!
>
> > "Serge E. Hallyn" <serue@us.ibm.com> wrote:
> >
> > > Following are two patches which have been sitting for some time in -mm.
> >
> > Where "some time" == "nearly six months".
> >
> > We need help considering, reviewing and testing this code, please.
>
> I did quick scan, and it looks ok. Plus, it means we can finally start
> using that old capabilities subsystem... so I think we should do it.
FWIW, I looked through it recently as well, and it looked reasonable enough
to me, though I'm not a security expert. I did have a question about
testing corner cases etc, which Serge has tried to address.
Serge, are you planning to post an update without STRICTXATTR ? That should
simplify the second patch.
Regards
Suparna
>
> Pavel
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> -
> 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
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
next prev parent reply other threads:[~2007-05-17 5:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 19:15 [PATCH 0/2] file capabilities: Introduction Serge E. Hallyn
2007-05-08 19:16 ` [PATCH 1/2] file capabilities: implement file capabilities Serge E. Hallyn
2007-05-08 19:17 ` [PATCH 2/2] file capabilities: accomodate >32 bit capabilities Serge E. Hallyn
2007-05-08 20:58 ` Andreas Dilger
2007-05-08 21:49 ` Serge E. Hallyn
2007-05-10 20:01 ` Andreas Dilger
2007-05-11 6:09 ` Suparna Bhattacharya
2007-05-14 17:26 ` Serge E. Hallyn
2007-05-08 20:05 ` [PATCH 0/2] file capabilities: Introduction Andrew Morton
2007-05-14 20:00 ` Pavel Machek
2007-05-17 5:57 ` Suparna Bhattacharya [this message]
2007-05-17 12:51 ` Serge E. Hallyn
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=20070517055747.GA15474@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=chrisw@sous-sol.org \
--cc=jeffschroeder@computer.org \
--cc=jmorris@namei.org \
--cc=kaigai@kaigai.gr.jp \
--cc=kmacmillan@mentalrootkit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=sds@tycho.nsa.gov \
--cc=serue@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.