From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 42986] ext2_fs.h requires undefined type umode_t
Date: Tue, 27 Mar 2012 06:17:59 GMT [thread overview]
Message-ID: <201203270617.q2R6HxI8032563@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-42986-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=42986
--- Comment #11 from Theodore Tso <tytso@mit.edu> 2012-03-27 06:17:59 ---
Yeah, but chmod is POSIX; EXT2_IOC_GETFLAGS is not. And if you are using the
EXT2_IOC_GETFLAGS variant, then you're saying that you only care about it
working on ext2, and most programs hopefully aspire to more portability than
that. I really doubt there are _that_ many ext2-specific program out there,
and the flags that can be set by IOC_GETFLAGS really are more esoteric than the
chmod flags.
In any case, Al Viro is carrying the patch in his tree, so ultimately it will
be up to him.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2012-03-27 6:17 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
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 [this message]
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=201203270617.q2R6HxI8032563@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.