All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42986] ext2_fs.h requires undefined type umode_t
Date: Sun, 25 Mar 2012 17:21:45 GMT	[thread overview]
Message-ID: <201203251721.q2PHLjaJ016562@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42986-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=42986





--- Comment #5 from Theodore Tso <tytso@mit.edu>  2012-03-25 17:21:44 ---
It's not going to be installed.  Al Viro has patches in his git tree which is
going to make it ***disappear*** from the kernel source tree altogether.  The
definitions which are needed for fs/ext2 will be moved to fs/ext2/ext2.h.   The
userspace definitions are being deleted.  The few places in the rest of the
kernel which were using ext2_fs.h and implying knowledge of the ext2 superblock
layout are being changed to use a function exported by the ext2 code, thus
properly providing better abstraction between the various kernel components.

There should be no valid user of this header, and there should not have been
one for at least eight years.   If they do exist, we'll find out when they
scream, and then we'll tell them that they are broken, and they should be using
the ext2_fs.h being shipped with e2fsprogs, and ideally libext2fs being shipped
with e2fsprogs.

The whole point is that it's insane to be maintaining two userspace headers,
especially since the one in the kernel tree has effectively not been maintained
for years (at least for use in userspace).

Again, if you know of other actual users of the ext2_fs.h being shipped in the
kernel, please let me know, and I'll personally reach out to them (and tell
them that they are close to a decade behind the times....)

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-03-25 17:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 13:23 [Bug 42986] New: ext2_fs.h requires undefined type umode_t bugzilla-daemon
2012-03-24 14:04 ` [Bug 42986] " bugzilla-daemon
2012-03-24 14:16 ` bugzilla-daemon
2012-03-25  1:20 ` bugzilla-daemon
2012-03-25  2:47 ` bugzilla-daemon
2012-03-25 17:21 ` bugzilla-daemon [this message]
2012-03-27  4:41 ` bugzilla-daemon
2012-03-27  5:02 ` bugzilla-daemon
2012-03-27  5:33 ` bugzilla-daemon
2012-03-27  7:31   ` Christoph Hellwig
2012-03-27  5:58 ` bugzilla-daemon
2012-03-27  6:05 ` bugzilla-daemon
2012-03-27  6:17 ` bugzilla-daemon
2012-03-27  6:21 ` bugzilla-daemon
2012-04-12 11:37 ` bugzilla-daemon
2012-04-12 15:04 ` bugzilla-daemon
2012-04-13  6:48 ` bugzilla-daemon

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=201203251721.q2PHLjaJ016562@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 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.