From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
Cc: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
tao.peng-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org,
jeff.layton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org,
bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/4] locks: new locks_mandatory_area calling convention
Date: Tue, 8 Dec 2015 15:54:53 +0100 [thread overview]
Message-ID: <20151208145453.GA3621@lst.de> (raw)
In-Reply-To: <20151208040504.GA2791-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
On Tue, Dec 08, 2015 at 04:05:04AM +0000, Al Viro wrote:
> Where the hell would truncate(2) get struct file, anyway? IOW, the inode
> argument is _not_ pointless; re-added.
Oh, right. Interestingly is seems like xfstests has no coverage of this
code path at all.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-12-08 14:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 11:59 move btrfs clone ioctls to common code V2 Christoph Hellwig
[not found] ` <1449143992-7415-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-12-03 11:59 ` [PATCH 1/4] locks: new locks_mandatory_area calling convention Christoph Hellwig
2015-12-08 4:05 ` Al Viro
[not found] ` <20151208040504.GA2791-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2015-12-08 14:54 ` Christoph Hellwig [this message]
[not found] ` <20151208145453.GA3621-jcswGhMUV9g@public.gmane.org>
2015-12-08 16:16 ` Al Viro
2015-12-03 11:59 ` [PATCH 2/4] vfs: pull btrfs clone API to vfs layer Christoph Hellwig
[not found] ` <1449143992-7415-3-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-12-07 0:53 ` Darrick J. Wong
[not found] ` <20151207005331.GA10582-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2015-12-07 15:13 ` Christoph Hellwig
2015-12-07 21:09 ` Darrick J. Wong
[not found] ` <20151207151319.GA2472-jcswGhMUV9g@public.gmane.org>
2015-12-08 1:54 ` Darrick J. Wong
2015-12-14 16:34 ` [PATCH 5/4] vfs: return EINVAL for unsupported file types in clone Christoph Hellwig
2015-12-09 20:40 ` [PATCH 2/4] vfs: pull btrfs clone API to vfs layer Darrick J. Wong
[not found] ` <20151209204033.GB10582-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2015-12-14 16:34 ` Christoph Hellwig
2015-12-14 17:08 ` Darrick J. Wong
2015-12-03 11:59 ` [PATCH 3/4] nfsd: Pass filehandle to nfs4_preprocess_stateid_op() Christoph Hellwig
2015-12-03 11:59 ` [PATCH 4/4] nfsd: implement the NFSv4.2 CLONE operation Christoph Hellwig
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=20151208145453.GA3621@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org \
--cc=jeff.layton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org \
--cc=linux-btrfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tao.peng-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org \
--cc=viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.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).