diff for duplicates of <YY69bWxs22LNlLs6@arm.com> diff --git a/a/1.txt b/N1/1.txt index 0468532..14c42ee 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -20,7 +20,7 @@ stopping if any of the iovs cannot be faulted in. It would be more consistent for MTE as well if we keep the fault-in check at the beginning of the user buffers only. I mentioned it here: -https://lore.kernel.org/all/YYQk9L0D57QHc0gE at arm.com/ +https://lore.kernel.org/all/YYQk9L0D57QHc0gE@arm.com/ > The same bug exists in generic_perform_write, but I'm not aware of any > callers of generic_perform_write that have page faults turned off. @@ -31,8 +31,8 @@ Similar reason as above, though one may argue it's a slight ABI change. > iomap_write_iter and generic_perform_write into post-faulting, but at > the very least, that still needs a bit of performance analysis: > -> https://lore.kernel.org/linux-fsdevel/20211026094430.3669156-1-agruenba at redhat.com/ -> https://lore.kernel.org/linux-fsdevel/20211027212138.3722977-1-agruenba at redhat.com/ +> https://lore.kernel.org/linux-fsdevel/20211026094430.3669156-1-agruenba@redhat.com/ +> https://lore.kernel.org/linux-fsdevel/20211027212138.3722977-1-agruenba@redhat.com/ I don't think that's urgent. At least generic_perform_write() will make progress with a fault-in that checks the beginning of the buffer, even diff --git a/a/content_digest b/N1/content_digest index b81d031..7e0795f 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,8 +1,12 @@ "ref\020211110174457.533866-1-agruenba@redhat.com\0" "From\0Catalin Marinas <catalin.marinas@arm.com>\0" - "Subject\0[Cluster-devel] [RFC] gfs2: Prevent endless loops in gfs2_file_buffered_write\0" + "Subject\0Re: [RFC] gfs2: Prevent endless loops in gfs2_file_buffered_write\0" "Date\0Fri, 12 Nov 2021 19:15:57 +0000\0" - "To\0cluster-devel.redhat.com\0" + "To\0Andreas Gruenbacher <agruenba@redhat.com>\0" + "Cc\0Linus Torvalds <torvalds@linux-foundation.org>" + Alexander Viro <viro@zeniv.linux.org.uk> + linux-fsdevel@vger.kernel.org + " cluster-devel@redhat.com\0" "\00:1\0" "b\0" "Hi Andreas,\n" @@ -27,7 +31,7 @@ "consistent for MTE as well if we keep the fault-in check at the\n" "beginning of the user buffers only. I mentioned it here:\n" "\n" - "https://lore.kernel.org/all/YYQk9L0D57QHc0gE at arm.com/\n" + "https://lore.kernel.org/all/YYQk9L0D57QHc0gE@arm.com/\n" "\n" "> The same bug exists in generic_perform_write, but I'm not aware of any\n" "> callers of generic_perform_write that have page faults turned off.\n" @@ -38,8 +42,8 @@ "> iomap_write_iter and generic_perform_write into post-faulting, but at\n" "> the very least, that still needs a bit of performance analysis:\n" "> \n" - "> https://lore.kernel.org/linux-fsdevel/20211026094430.3669156-1-agruenba at redhat.com/\n" - "> https://lore.kernel.org/linux-fsdevel/20211027212138.3722977-1-agruenba at redhat.com/\n" + "> https://lore.kernel.org/linux-fsdevel/20211026094430.3669156-1-agruenba@redhat.com/\n" + "> https://lore.kernel.org/linux-fsdevel/20211027212138.3722977-1-agruenba@redhat.com/\n" "\n" "I don't think that's urgent. At least generic_perform_write() will make\n" "progress with a fault-in that checks the beginning of the buffer, even\n" @@ -57,4 +61,4 @@ "-- \n" Catalin -1815ad07ee0ff08ed774abe3bf43f41a8bba33c5ba8876ee9082bf05c9680364 +c8365d3e6dc6d9db30a735db55ed98c061090ccd73443b77910a9dcbaa43761d
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.