All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	Cezary Sliwa <sliwa@blue.cft.edu.pl>
Subject: Re: [PATCH] ext2: include fs.h in ext2_fs.h
Date: Fri, 3 Dec 2010 13:20:29 -0500	[thread overview]
Message-ID: <20101203182029.GB26906@thunk.org> (raw)
In-Reply-To: <4CF91A32.6080706@redhat.com>

On Fri, Dec 03, 2010 at 10:26:26AM -0600, Eric Sandeen wrote:
> As reported by Cezary Sliwa in
> https://bugzilla.kernel.org/show_bug.cgi?id=24282
> ext2_fs.h references FS_DIRSYNC_FL etc, but does not
> include <linux/fs.h> to define them.  This seems ok
> for kernelspace builds, but breaks userspace applications
> which include ext2_fs.h.
> 
> Reported-by: Cezary Sliwa <sliwa@blue.cft.edu.pl>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>

I wonder if we would be better off getting application programs weaned
off of trying to use the kernel's version of ext2_fs.h altogether.
E2fsprogs ships one which is going to be more uptodate, and works for
ext2/ext3/ext4.  Certainly if you plan to be using libext2fs (which I
would strongly advise for any program hoping to manipulate ext2
filesystem structures directly), you should be using the header file
shipped with e2fsprogs.

Debian and Ubuntu for example ships /usr/include/ext2fs/ext2_fs.h as
part of its e2fslibs-dev package.

						- Ted

      reply	other threads:[~2010-12-03 18:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 16:26 [PATCH] ext2: include fs.h in ext2_fs.h Eric Sandeen
2010-12-03 18:20 ` Ted Ts'o [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=20101203182029.GB26906@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=sliwa@blue.cft.edu.pl \
    /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.