From: Mark Fasheh <mfasheh@suse.de>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-xfs@vger.kernel.org, Adam Borowski <kilobyte@angband.pl>,
David Sterba <dsterba@suse.cz>
Subject: Re: [RESEND][PATCH v4 0/2] vfs: better dedupe permission check
Date: Tue, 17 Jul 2018 19:58:39 +0000 [thread overview]
Message-ID: <20180717195839.GD10690@wotan.suse.de> (raw)
In-Reply-To: <20180717194818.GV32415@magnolia>
On Tue, Jul 17, 2018 at 12:48:18PM -0700, Darrick J. Wong wrote:
> On Tue, Jul 17, 2018 at 12:09:04PM -0700, Mark Fasheh wrote:
> > From: Mark Fasheh <mfasheh@suse.de>
> >
> > [PATCH] ioctl_fideduperange.2: clarify permission requirements
> >
> > dedupe permission checks were recently relaxed - update our man page to
> > reflect those changes.
> >
> > Signed-off-by: Mark Fasheh <mfasheh@suse.de>
> > ---
> > man2/ioctl_fideduperange.2 | 8 +++++---
>
> Mmm, man page update, thank you for editing the documentation too!
No problem, thanks for suggesting I do it.
> Please cc linux-api and Michael Kerrisk so this can go upstream.
Will do. The changes you point out below all look good to me so I'll
incorporate them and send an updated version to the appropriate folks.
Thanks
--Mark
next prev parent reply other threads:[~2018-07-17 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 19:09 [RESEND][PATCH v4 0/2] vfs: better dedupe permission check Mark Fasheh
2018-07-17 19:09 ` [PATCH v4 1/2] vfs: allow dedupe of user owned read-only files Mark Fasheh
2018-07-17 19:09 ` [PATCH v4 2/2] vfs: dedupe should return EPERM if permission is not granted Mark Fasheh
2018-07-17 19:48 ` [RESEND][PATCH v4 0/2] vfs: better dedupe permission check Darrick J. Wong
2018-07-17 19:58 ` Mark Fasheh [this message]
2018-07-17 20:14 ` Mark Fasheh
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=20180717195839.GD10690@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=darrick.wong@oracle.com \
--cc=dsterba@suse.cz \
--cc=kilobyte@angband.pl \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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).