From: Roman Mamedov <rm@romanrm.net>
To: "Lauri Võsandi" <lauri.vosandi@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: optionally enforce chroot for btrfs receive
Date: Sun, 19 Apr 2015 17:05:03 +0500 [thread overview]
Message-ID: <20150419170503.4d888c04@natsu> (raw)
In-Reply-To: <1429443988-16001-1-git-send-email-lauri.vosandi@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Sun, 19 Apr 2015 14:46:28 +0300
Lauri Võsandi <lauri.vosandi@gmail.com> wrote:
> This patch forces btrfs receive to issue chroot before
> parsing the btrfs stream using command-line flag -C
> to confine the process and minimize damage that could
> be done via malicious btrfs stream.
>
> Signed-off-by: Lauri Võsandi <lauri.vosandi@gmail.com>
> ---
> cmds-receive.c | 38 +++++++++++++++++++++++++++++---------
> 1 file changed, 29 insertions(+), 9 deletions(-)
No patch versions and changelogs between them?...
By now there are 4 versions of this patch with identical subject and vague
unclear differences in description and content.
Usually what you do is label each new one [PATCH v2] (v3, v4) and describe what
got changed on each iteration.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-04-19 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 10:44 [PATCH] btrfs-progs: enforce chroot for btrfs receive Lauri Võsandi
2015-04-14 12:28 ` David Sterba
2015-04-14 13:19 ` Austin S Hemmelgarn
2015-04-17 17:34 ` David Sterba
2015-04-18 13:59 ` [PATCH] btrfs-progs: optionally " Lauri Võsandi
2015-04-18 14:52 ` Lauri Võsandi
2015-04-19 7:25 ` Mike Fleetwood
2015-04-19 11:46 ` Lauri Võsandi
2015-04-19 12:05 ` Roman Mamedov [this message]
2015-04-20 12:13 ` lauri
2015-04-22 17:27 ` David Sterba
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=20150419170503.4d888c04@natsu \
--to=rm@romanrm.net \
--cc=lauri.vosandi@gmail.com \
--cc=linux-btrfs@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 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.