On Wed, Feb 08, 2017 at 07:29:22AM -0500, Austin S. Hemmelgarn wrote: > On 2017-02-07 13:27, David Sterba wrote: > > On Fri, Feb 03, 2017 at 08:48:58AM -0500, Austin S. Hemmelgarn wrote: > >> This adds some extra documentation to the btrfs-receive manpage that > >> explains some of the security related aspects of btrfs-receive. The > >> first part covers the fact that the subvolume being received is writable > >> until the receive finishes, and the second covers the current lack of > >> sanity checking of the send stream. > >> > >> Signed-off-by: Austin S. Hemmelgarn <ahferroin7@xxxxxxxxx> > > > > Applied, thanks. > > > Didn't get a chance to mention this yesterday, but it looks like you > hadn't seen the updated version I sent on the third. Message ID is: > <20170203193805.96977-1-ahferroin7@xxxxxxxxx> Ah sorry I missed that. > The only significant difference is that I updated the description for > the writablility issue using a much better description from Graham Cobb > (with his permission of course). > > If you want, I can send an incremental patch on top of the original to > update just that description. No need to, I'll replace the patch with the latest version. Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
