From: Christoph Hellwig <hch@infradead.org>
To: Brad Boyer <flar@allandria.com>
Cc: Damian Stewart <damian@frey.co.nz>, linux-fsdevel@vger.kernel.org
Subject: Re: PROBLEM: hfsplus filesystem allows opendir() on plain files
Date: Fri, 5 Dec 2008 04:39:49 -0500 [thread overview]
Message-ID: <20081205093948.GA15714@infradead.org> (raw)
In-Reply-To: <20081202222111.GA2738@cynthia.pants.nu>
On Tue, Dec 02, 2008 at 02:21:11PM -0800, Brad Boyer wrote:
> We can't fix this without either eliminating this way to open the
> resource fork
Which sould have happened long ago. See the reiser4 discussion. You're
breaking userspace semantic without a good reason.
next prev parent reply other threads:[~2008-12-05 9:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 15:26 PROBLEM: hfsplus filesystem allows opendir() on plain files Damian Stewart
2008-12-02 22:21 ` Brad Boyer
2008-12-05 8:53 ` Damian Stewart
2008-12-06 6:00 ` Brad Boyer
2008-12-05 9:39 ` Christoph Hellwig [this message]
2008-12-06 6:32 ` Brad Boyer
2008-12-06 6:47 ` Al Viro
2008-12-06 7:21 ` Brad Boyer
2008-12-06 22:31 ` Al Viro
2008-12-06 22:35 ` Al Viro
2008-12-06 12:06 ` Anton Altaparmakov
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=20081205093948.GA15714@infradead.org \
--to=hch@infradead.org \
--cc=damian@frey.co.nz \
--cc=flar@allandria.com \
--cc=linux-fsdevel@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).