From: Christoph Hellwig <hch@infradead.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: hch@infradead.org, matthew@wil.cx, trond.myklebust@fys.uio.no,
adilger@clusterfs.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [patch 1/2] VFS: new fgetattr() file operation
Date: Mon, 24 Sep 2007 14:27:25 +0100 [thread overview]
Message-ID: <20070924132725.GA20116@infradead.org> (raw)
In-Reply-To: <E1IZnpC-0003vk-00@dorka.pomaz.szeredi.hu>
On Mon, Sep 24, 2007 at 03:18:10PM +0200, Miklos Szeredi wrote:
> > Or not support such a broken protocol at all.
>
> Wonder what people would say if we removed support for NFSv[23].
>
> Just because a protocol does not support "perfect" UNIX semantics, it
> doesn't mean it's broken. By that standard almost all network
> filesystem protocols are severely broken.
Well, they are broken by these and other standards. At least nfs and
cifs maintainers do the workarounds for this brokeness where they belong.
next prev parent reply other threads:[~2007-09-24 13:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 12:24 [patch 1/2] VFS: new fgetattr() file operation Miklos Szeredi
2007-09-24 12:25 ` [patch 2/2] VFS: allow filesystem to override mknod capability checks Miklos Szeredi
2007-09-24 12:38 ` Christoph Hellwig
2007-09-28 2:40 ` Neil Brown
2007-10-01 18:06 ` Miklos Szeredi
2007-09-24 12:36 ` [patch 1/2] VFS: new fgetattr() file operation Christoph Hellwig
2007-09-24 12:48 ` Miklos Szeredi
2007-09-24 12:59 ` Matthew Wilcox
2007-09-24 13:06 ` Miklos Szeredi
2007-09-24 13:10 ` Christoph Hellwig
2007-09-24 13:18 ` Miklos Szeredi
2007-09-24 13:27 ` Christoph Hellwig [this message]
2007-09-24 13:38 ` Miklos Szeredi
2007-09-24 13:16 ` Matthew Wilcox
2007-09-24 13:21 ` Miklos Szeredi
2007-09-24 13:42 ` Alan Cox
2007-09-24 13:40 ` Miklos Szeredi
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=20070924132725.GA20116@infradead.org \
--to=hch@infradead.org \
--cc=adilger@clusterfs.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=miklos@szeredi.hu \
--cc=trond.myklebust@fys.uio.no \
/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).