diff for duplicates of <YXGexrdprC+NTslm@arm.com> diff --git a/a/1.txt b/N1/1.txt index 76139ce..dbceeb9 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -59,7 +59,7 @@ anything at all (i.e. returning size) should happen only when nothing could be copied" (from linux/uaccess.h). I think we can add a requirement for the new size_t-based fault_in_* variants without mandating that the whole range is probed, something like: "returning -leftover < size guarantees that a subsequent user access@uaddr copies +leftover < size guarantees that a subsequent user access at uaddr copies at least one byte eventually". I said "eventually" but maybe we can come up with some clearer wording for a liveness property. @@ -70,3 +70,8 @@ reset and guarantee forward progress. -- Catalin + +_______________________________________________ +Ocfs2-devel mailing list +Ocfs2-devel@oss.oracle.com +https://oss.oracle.com/mailman/listinfo/ocfs2-devel diff --git a/a/content_digest b/N1/content_digest index adf668b..996a7d0 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -9,9 +9,19 @@ "ref\0YXE7fhDkqJbfDk6e@arm.com\0" "ref\0CAHc6FU5xTMOxuiEDyc9VO_V98=bvoDc-0OFi4jsGPgWJWjRJWQ@mail.gmail.com\0" "From\0Catalin Marinas <catalin.marinas@arm.com>\0" - "Subject\0[Cluster-devel] [RFC][arm64] possible infinite loop in btrfs search_ioctl()\0" + "Subject\0Re: [Ocfs2-devel] [RFC][arm64] possible infinite loop in btrfs search_ioctl()\0" "Date\0Thu, 21 Oct 2021 18:09:26 +0100\0" - "To\0cluster-devel.redhat.com\0" + "To\0Andreas Gruenbacher <agruenba@redhat.com>\0" + "Cc\0cluster-devel <cluster-devel@redhat.com>" + Jan Kara <jack@suse.cz> + Will Deacon <will@kernel.org> + Linux Kernel Mailing List <linux-kernel@vger.kernel.org> + Josef Bacik <josef@toxicpanda.com> + Christoph Hellwig <hch@infradead.org> + Al Viro <viro@zeniv.linux.org.uk> + linux-fsdevel <linux-fsdevel@vger.kernel.org> + Linus Torvalds <torvalds@linux-foundation.org> + " ocfs2-devel@oss.oracle.com <ocfs2-devel@oss.oracle.com>\0" "\00:1\0" "b\0" "On Thu, Oct 21, 2021 at 04:42:33PM +0200, Andreas Gruenbacher wrote:\n" @@ -75,7 +85,7 @@ "could be copied\" (from linux/uaccess.h). I think we can add a\n" "requirement for the new size_t-based fault_in_* variants without\n" "mandating that the whole range is probed, something like: \"returning\n" - "leftover < size guarantees that a subsequent user access@uaddr copies\n" + "leftover < size guarantees that a subsequent user access at uaddr copies\n" "at least one byte eventually\". I said \"eventually\" but maybe we can come\n" "up with some clearer wording for a liveness property.\n" "\n" @@ -85,6 +95,11 @@ "reset and guarantee forward progress.\n" "\n" "-- \n" - Catalin + "Catalin\n" + "\n" + "_______________________________________________\n" + "Ocfs2-devel mailing list\n" + "Ocfs2-devel@oss.oracle.com\n" + https://oss.oracle.com/mailman/listinfo/ocfs2-devel -831c34991d5a31ce7e85165dd862a61286e54e9dd6a215a0d046469eb02511cf +9cf4e5382f5b041aa9cf8117e0044142b57a6287af6f3daa4452a2f9a535e380
diff --git a/a/1.txt b/N2/1.txt index 76139ce..3db3407 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -59,7 +59,7 @@ anything at all (i.e. returning size) should happen only when nothing could be copied" (from linux/uaccess.h). I think we can add a requirement for the new size_t-based fault_in_* variants without mandating that the whole range is probed, something like: "returning -leftover < size guarantees that a subsequent user access@uaddr copies +leftover < size guarantees that a subsequent user access at uaddr copies at least one byte eventually". I said "eventually" but maybe we can come up with some clearer wording for a liveness property. diff --git a/a/content_digest b/N2/content_digest index adf668b..0e28486 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -9,9 +9,21 @@ "ref\0YXE7fhDkqJbfDk6e@arm.com\0" "ref\0CAHc6FU5xTMOxuiEDyc9VO_V98=bvoDc-0OFi4jsGPgWJWjRJWQ@mail.gmail.com\0" "From\0Catalin Marinas <catalin.marinas@arm.com>\0" - "Subject\0[Cluster-devel] [RFC][arm64] possible infinite loop in btrfs search_ioctl()\0" + "Subject\0Re: [RFC][arm64] possible infinite loop in btrfs search_ioctl()\0" "Date\0Thu, 21 Oct 2021 18:09:26 +0100\0" - "To\0cluster-devel.redhat.com\0" + "To\0Andreas Gruenbacher <agruenba@redhat.com>\0" + "Cc\0Linus Torvalds <torvalds@linux-foundation.org>" + Al Viro <viro@zeniv.linux.org.uk> + Christoph Hellwig <hch@infradead.org> + Darrick J. Wong <djwong@kernel.org> + Jan Kara <jack@suse.cz> + Matthew Wilcox <willy@infradead.org> + cluster-devel <cluster-devel@redhat.com> + linux-fsdevel <linux-fsdevel@vger.kernel.org> + Linux Kernel Mailing List <linux-kernel@vger.kernel.org> + ocfs2-devel@oss.oracle.com <ocfs2-devel@oss.oracle.com> + Josef Bacik <josef@toxicpanda.com> + " Will Deacon <will@kernel.org>\0" "\00:1\0" "b\0" "On Thu, Oct 21, 2021 at 04:42:33PM +0200, Andreas Gruenbacher wrote:\n" @@ -75,7 +87,7 @@ "could be copied\" (from linux/uaccess.h). I think we can add a\n" "requirement for the new size_t-based fault_in_* variants without\n" "mandating that the whole range is probed, something like: \"returning\n" - "leftover < size guarantees that a subsequent user access@uaddr copies\n" + "leftover < size guarantees that a subsequent user access at uaddr copies\n" "at least one byte eventually\". I said \"eventually\" but maybe we can come\n" "up with some clearer wording for a liveness property.\n" "\n" @@ -87,4 +99,4 @@ "-- \n" Catalin -831c34991d5a31ce7e85165dd862a61286e54e9dd6a215a0d046469eb02511cf +1667f3eaa22d7c30e138404e15ec72d09c41cbd15a10b055cbfcfd25bc35bf56
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.