From: Chris Mason <chris.mason@oracle.com>
To: Tim Gardner <timg@tpi.com>
Cc: jeffschroeder@computer.org, Jan Engelhardt <jengelh@medozas.de>,
Jeff Mahoney <jeffm@suse.com>,
Tim Gardner <tim.gardner@canonical.com>,
linux-fsdevel@vger.kernel.org, kernel-team@lists.ubuntu.com,
linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
John Johansen <jjohansen@suse.de>
Subject: Re: Btrfs v0.14 Released
Date: Fri, 2 May 2008 16:58:00 -0400 [thread overview]
Message-ID: <200805021658.01459.chris.mason@oracle.com> (raw)
In-Reply-To: <481B3C0E.502@tpi.com>
On Friday 02 May 2008, Tim Gardner wrote:
> Chris Mason wrote:
> > On Friday 02 May 2008, Jeff Schroeder wrote:
> >
> > [ Btrfs oops with apparmor patched in ]
> >
> >> Make is not my forte, but here is a working test to see if apparmor
> >> exists in Ubuntu 8.04.
> >> Maybe have make apply a patch to the btrfs source if this test
> >> succeeds? Does this work in SUSE?
> >>
> >> http://www.digitalprognosis.com/opensource/patches/btrfs/lame_apparmor_t
> >>est _for_btrfs.patch
> >
> > Thanks, but this uses CONFIG_SECURITY_APPARMOR which isn't enough to tell
> > if the kernel has the patch. Lets go back to Jeff's suse patch:
> >
I ended up using the CONFIG_SECURITY_APPARMOR test because the other test
suggested here sounded like something that might eventually not be very
ubuntu specific (instead of the nice a plain CONFIG_SUSE_KERNEL).
Thanks to everyone for the hints, if someone could please test:
http://btrfs.wiki.kernel.org/index.php/Hot_Fixes
I'd be grateful.
-chris
prev parent reply other threads:[~2008-05-02 20:58 UTC|newest]
Thread overview: 30+ 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: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
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: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: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 [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=200805021658.01459.chris.mason@oracle.com \
--to=chris.mason@oracle.com \
--cc=jeffm@suse.com \
--cc=jeffschroeder@computer.org \
--cc=jengelh@medozas.de \
--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 \
--cc=timg@tpi.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.