From: Kees Cook <kees@canonical.com>
To: John Johansen <jjohansen@suse.de>
Cc: Chris Mason <chris.mason@oracle.com>,
jeffschroeder@computer.org, linux-fsdevel@vger.kernel.org,
kernel-team@lists.ubuntu.com, linux-kernel@vger.kernel.org,
linux-btrfs@vger.kernel.org,
Tim Gardner <tim.gardner@canonical.com>
Subject: Re: Btrfs v0.14 Released
Date: Thu, 1 May 2008 12:51:52 -0700 [thread overview]
Message-ID: <20080501195152.GM12850@outflux.net> (raw)
In-Reply-To: <481A1BB9.8050109@canonical.com>
Hi,
On Thu, May 01, 2008 at 01:36:25PM -0600, Tim Gardner wrote:
> Chris Mason wrote:
> > On Thursday 01 May 2008, Tim Gardner wrote:
> >
> > [ btrfs oops on ubuntu ]
> >
> >>>> This is because ubuntu kernels ship with apparmor, you'll need this
> >>>> patch:
> >>>>
> >>>> If there is a #ifdef IM_A_UBUNTU_KERNEL I can use, I'll do it. Jeff
> >>>> Mahoney has a similar patch for SUSE that I've been meaning to merge,
> >>>> but I wanted to lookup some way to check for ubuntu as well.
> >>>>
> >>>> -chris
> >>>>
> >>>> diff -r e7da2489b19b file.c
> >>>> --- a/file.c Wed Apr 30 13:59:35 2008 -0400
> >>>> +++ b/file.c Thu May 01 12:25:11 2008 -0400
> >>>> @@ -852,7 +852,7 @@ static ssize_t btrfs_file_write(struct f
> >>>> goto out_nolock;
> >>>> if (count == 0)
> >>>> goto out_nolock;
> >>>> - err = remove_suid(fdentry(file));
> >>>> + err = remove_suid(&file->f_path);
> >>>> if (err)
> >>>> goto out_nolock;
> >>>> file_update_time(file);
> >> Couldn't you #ifdef based on CONFIG_SECURITY_APPARMOR ? This ought to
> >> work for Hardy. However the next development kernel (Intrepid) does not
> >> have the APPARMOR patches, so just knowing that its an UBUNTU kernel is
> >> not specific enough.
> >
> > I've been assuming the apparmor patches change remove_suid even when they are
> > not enabled in the config.
> >
> > -chris
> >
>
> Lets get Kees involved. He developed the patch set for Hardy. I would
> hope that if CONFIG_SECURITY_APPARMOR=n then the source would default to
> its normal state.
I can't claim to have developed the patches, only helping coordinate
their merging into Ubuntu. John Johansen is the real person we should
check with -- he did all the heavy lifting -- now added to discussion.
(Hi John!)
-Kees
--
Kees Cook
Ubuntu Security Team
next prev parent reply other threads:[~2008-05-01 19:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 20:01 Btrfs v0.14 Released Chris Mason
2008-05-01 16:04 ` Chris Mason
2008-05-01 16:18 ` Jeff Schroeder
2008-05-01 16:26 ` Chris Mason
2008-05-01 16:39 ` Jeff Schroeder
2008-05-01 19:06 ` Tim Gardner
2008-05-01 19:17 ` Chris Mason
2008-05-01 19:27 ` Jeff Mahoney
2008-05-01 19:36 ` Tim Gardner
2008-05-01 19:51 ` Kees Cook [this message]
2008-05-01 20:10 ` Jeff Mahoney
2008-05-02 6:40 ` Jan Engelhardt
2008-05-02 12:52 ` Chris Mason
2008-05-02 13:30 ` Jan Engelhardt
2008-05-02 14:10 ` Jan Engelhardt
2008-05-02 14:15 ` Jeff Schroeder
2008-05-02 14:31 ` Jan Engelhardt
2008-05-02 14:34 ` Chris Mason
2008-05-02 14:38 ` Matthew Wilcox
2008-05-02 14:52 ` Chris Mason
2008-05-02 15:07 ` Jan Engelhardt
2008-05-02 16:06 ` Tim Gardner
2008-05-02 16:26 ` Jeff Mahoney
2008-05-02 18:00 ` Jan Engelhardt
2008-05-02 18:01 ` Jeff Mahoney
2008-05-02 18:14 ` Jeff Schroeder
2008-05-02 20:58 ` Chris Mason
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=20080501195152.GM12850@outflux.net \
--to=kees@canonical.com \
--cc=chris.mason@oracle.com \
--cc=jeffschroeder@computer.org \
--cc=jjohansen@suse.de \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.gardner@canonical.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).