From: Adam Borowski <kilobyte@angband.pl>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: ping howto (was Re: [PATCH resend] vfs: allow FILE_EXTENT_SAME (dedupe_file_range) on a file opened ro)
Date: Thu, 13 Oct 2016 00:15:52 +0200 [thread overview]
Message-ID: <20161012221552.GA17385@angband.pl> (raw)
In-Reply-To: <20161005143854.17133-1-kilobyte@angband.pl>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
On Wed, Oct 05, 2016 at 04:38:54PM +0200, Adam Borowski wrote:
> [fix for dedupe-vs-exec ETXTBSY]
> Reviewed-by: Mark Fasheh <mfasheh@suse.de>
Hi guys!
May I ask if I'm doing something wrong, or barking up the wrong tree? I've
sent this patch thrice (May 20, Jul 18, Oct 5), pinged once (Aug 6), yet it
hasn't been taken nor NACKed yet. For fixes to vfs core I need to bother Al
Viro, -fsdevel@vger, -kernel@vger, right?
It's not a vital fix (strictly speaking, it only allows to fix userspace),
as save for unprivileged containers, when deduping executables you usually
need to be root anyway -- but it'd still be nice to have it. It has been
ACKed by the original author of that code.
(Sorry for being annoying, I got only 13 commits elsewhere in the kernel so
please point me in the right direction when hitting :p)
Meow!
--
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month. Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-10-12 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 14:38 [PATCH resend] vfs: allow FILE_EXTENT_SAME (dedupe_file_range) on a file opened ro Adam Borowski
2016-10-12 22:15 ` Adam Borowski [this message]
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=20161012221552.GA17385@angband.pl \
--to=kilobyte@angband.pl \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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.