linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: jeffschroeder@computer.org
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: Btrfs v0.14 Released
Date: Thu, 1 May 2008 12:26:55 -0400	[thread overview]
Message-ID: <200805011226.56076.chris.mason@oracle.com> (raw)
In-Reply-To: <c24352ca0805010918j395470d0o8f2088571c90183b@mail.gmail.com>

On Thursday 01 May 2008, Jeff Schroeder wrote:
> On Thu, May 1, 2008 at 9:04 AM, Chris Mason <chris.mason@oracle.com> wrote:
> > On Tuesday 29 April 2008, Chris Mason wrote:
> >  > Hello everyone,
> >  >
> >  > Btrfs v0.14 is now available for download.  Please note the disk
> >  > format has changed, and it is not compatible with older versions of
> >  > Btrfs.
> >  >
> >  > For downloads and documention, please see the Btrfs project page:
> >  >
> >  > http://btrfs.wiki.kernel.org
> >
> >  Hello everyone,
> >
> >  I've rolled up some fixes for older kernels and fixed an uninitialized
> >  variables in btrfs-progs that could cause an oops on mount.  I'll wait a
> > few days to see if other bug reports come in and cut a 0.15 with any
> > other critical fixes.
>
> Well it oopses on writes everytime in Ubuntu 8.04 (Hardy). I'd planned
> on digging into
> it more before spending a bug report, but will send it tonight after
> getting to the affected
> machine.

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);

  reply	other threads:[~2008-05-01 16:26 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 [this message]
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
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=200805011226.56076.chris.mason@oracle.com \
    --to=chris.mason@oracle.com \
    --cc=jeffschroeder@computer.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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).