diff for duplicates of <20190818174354.GA12940@mit.edu> diff --git a/a/1.txt b/N1/1.txt index 9f68ecf..83d2046 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ -On Sun, Aug 18, 2019@08:58:12AM -0700, Christoph Hellwig wrote: -> On Sun, Aug 18, 2019@11:11:54AM -0400, Theodore Y. Ts'o wrote: +On Sun, Aug 18, 2019 at 08:58:12AM -0700, Christoph Hellwig wrote: +> On Sun, Aug 18, 2019 at 11:11:54AM -0400, Theodore Y. Ts'o wrote: > > Note that of the mainstream file systems, ext4 and xfs don't guarantee > > that it's safe to blindly take maliciously provided file systems, such > > as those provided by a untrusted container, and mount it on a file @@ -10,7 +10,7 @@ On Sun, Aug 18, 2019@08:58:12AM -0700, Christoph Hellwig wrote: > I think this greatly misrepresents the general attitute of the XFS > developers. We take sanity checks for the modern v5 on disk format > very series, and put a lot of effort into handling corrupted file -> systems as good as possible, although there are of course no guarantee?. +> systems as good as possible, although there are of course no guaranteeѕ. > > The quote that you've taken out of context is for the legacy v4 format > that has no checksums and other integrity features. diff --git a/a/content_digest b/N1/content_digest index ffdaaab..bc3d5ef 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,13 +8,36 @@ "ref\0790210571.69061.1566120073465.JavaMail.zimbra@nod.at\0" "ref\020190818151154.GA32157@mit.edu\0" "ref\020190818155812.GB13230@infradead.org\0" - "From\0tytso@mit.edu (Theodore Y. Ts'o)\0" - "Subject\0[PATCH] erofs: move erofs out of staging\0" + "From\0Theodore Y. Ts'o <tytso@mit.edu>\0" + "Subject\0Re: [PATCH] erofs: move erofs out of staging\0" "Date\0Sun, 18 Aug 2019 13:43:54 -0400\0" + "To\0Christoph Hellwig <hch@infradead.org>\0" + "Cc\0Richard Weinberger <richard@nod.at>" + Greg Kroah-Hartman <gregkh@linuxfoundation.org> + Gao Xiang <hsiangkao@aol.com> + Jan Kara <jack@suse.cz> + Chao Yu <yuchao0@huawei.com> + Dave Chinner <david@fromorbit.com> + David Sterba <dsterba@suse.cz> + Miao Xie <miaoxie@huawei.com> + devel <devel@driverdev.osuosl.org> + Stephen Rothwell <sfr@canb.auug.org.au> + Darrick <darrick.wong@oracle.com> + Amir Goldstein <amir73il@gmail.com> + linux-erofs <linux-erofs@lists.ozlabs.org> + Al Viro <viro@zeniv.linux.org.uk> + Jaegeuk Kim <jaegeuk@kernel.org> + linux-kernel <linux-kernel@vger.kernel.org> + Li Guifu <bluce.liguifu@huawei.com> + Fang Wei <fangwei1@huawei.com> + Pavel Machek <pavel@denx.de> + linux-fsdevel <linux-fsdevel@vger.kernel.org> + Andrew Morton <akpm@linux-foundation.org> + " torvalds <torvalds@linux-foundation.org>\0" "\00:1\0" "b\0" - "On Sun, Aug 18, 2019@08:58:12AM -0700, Christoph Hellwig wrote:\n" - "> On Sun, Aug 18, 2019@11:11:54AM -0400, Theodore Y. Ts'o wrote:\n" + "On Sun, Aug 18, 2019 at 08:58:12AM -0700, Christoph Hellwig wrote:\n" + "> On Sun, Aug 18, 2019 at 11:11:54AM -0400, Theodore Y. Ts'o wrote:\n" "> > Note that of the mainstream file systems, ext4 and xfs don't guarantee\n" "> > that it's safe to blindly take maliciously provided file systems, such\n" "> > as those provided by a untrusted container, and mount it on a file\n" @@ -25,7 +48,7 @@ "> I think this greatly misrepresents the general attitute of the XFS\n" "> developers. We take sanity checks for the modern v5 on disk format\n" "> very series, and put a lot of effort into handling corrupted file\n" - "> systems as good as possible, although there are of course no guarantee?.\n" + "> systems as good as possible, although there are of course no guarantee\321\225.\n" "> \n" "> The quote that you've taken out of context is for the legacy v4 format\n" "> that has no checksums and other integrity features.\n" @@ -43,4 +66,4 @@ "\n" "\t\t\t\t\t- Ted" -2cd0cabdae93b330221fcaf57f851128c9657ed5ae4974ab94b4aff8dfdaaa6c +f1e1e99f4bd29367985e157a15fd1d686c5ec1b06daaf30021dcaa6ab176008e
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.