diff for duplicates of <20200918134406.GA17064@lst.de> diff --git a/a/1.txt b/N1/1.txt index 873357d..a78ce31 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ On Fri, Sep 18, 2020 at 02:40:12PM +0100, Al Viro wrote: > > /* Vector 0x110 is LINUX_32BIT_SYSCALL_TRAP */ -> > - return pt_regs_trap_type(current_pt_regs()) == 0x110; -> > + return pt_regs_trap_type(current_pt_regs()) == 0x110 || +> > - return pt_regs_trap_type(current_pt_regs()) = 0x110; +> > + return pt_regs_trap_type(current_pt_regs()) = 0x110 || > > + (current->flags & PF_FORCE_COMPAT); > > Can't say I like that approach ;-/ Reasoning about the behaviour is much diff --git a/a/content_digest b/N1/content_digest index 354fad4..49c91ad 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,7 +3,7 @@ "ref\020200918134012.GY3421308@ZenIV.linux.org.uk\0" "From\0Christoph Hellwig <hch@lst.de>\0" "Subject\0Re: [PATCH 1/9] kernel: add a PF_FORCE_COMPAT flag\0" - "Date\0Fri, 18 Sep 2020 15:44:06 +0200\0" + "Date\0Fri, 18 Sep 2020 13:44:06 +0000\0" "To\0Al Viro <viro@zeniv.linux.org.uk>\0" "Cc\0Christoph Hellwig <hch@lst.de>" Andrew Morton <akpm@linux-foundation.org> @@ -32,8 +32,8 @@ "b\0" "On Fri, Sep 18, 2020 at 02:40:12PM +0100, Al Viro wrote:\n" "> > \t/* Vector 0x110 is LINUX_32BIT_SYSCALL_TRAP */\n" - "> > -\treturn pt_regs_trap_type(current_pt_regs()) == 0x110;\n" - "> > +\treturn pt_regs_trap_type(current_pt_regs()) == 0x110 ||\n" + "> > -\treturn pt_regs_trap_type(current_pt_regs()) = 0x110;\n" + "> > +\treturn pt_regs_trap_type(current_pt_regs()) = 0x110 ||\n" "> > +\t\t(current->flags & PF_FORCE_COMPAT);\n" "> \n" "> Can't say I like that approach ;-/ Reasoning about the behaviour is much\n" @@ -42,4 +42,4 @@ "I don't particularly like it either. But do you have a better idea\n" how to deal with io_uring vs compat tasks? -5cfdb88f3449260ee155d6479b2271b68cf03b6ce4927ef49992182af16a5dad +9ede2f77867940027b5d8307b6ddffb6383215677e44315a5556cb42ab2f2bfa
diff --git a/a/content_digest b/N2/content_digest index 354fad4..642bdb0 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -5,29 +5,29 @@ "Subject\0Re: [PATCH 1/9] kernel: add a PF_FORCE_COMPAT flag\0" "Date\0Fri, 18 Sep 2020 15:44:06 +0200\0" "To\0Al Viro <viro@zeniv.linux.org.uk>\0" - "Cc\0Christoph Hellwig <hch@lst.de>" - Andrew Morton <akpm@linux-foundation.org> - Jens Axboe <axboe@kernel.dk> - Arnd Bergmann <arnd@arndb.de> - David Howells <dhowells@redhat.com> - linux-arm-kernel@lists.infradead.org - x86@kernel.org - linux-kernel@vger.kernel.org + "Cc\0linux-aio@kvack.org" linux-mips@vger.kernel.org - linux-parisc@vger.kernel.org - linuxppc-dev@lists.ozlabs.org - linux-s390@vger.kernel.org + David Howells <dhowells@redhat.com> + linux-mm@kvack.org + keyrings@vger.kernel.org sparclinux@vger.kernel.org - linux-block@vger.kernel.org + Christoph Hellwig <hch@lst.de> + linux-arch@vger.kernel.org + linux-s390@vger.kernel.org linux-scsi@vger.kernel.org - linux-fsdevel@vger.kernel.org - linux-aio@kvack.org + x86@kernel.org + Arnd Bergmann <arnd@arndb.de> + linux-block@vger.kernel.org io-uring@vger.kernel.org - linux-arch@vger.kernel.org - linux-mm@kvack.org + linux-arm-kernel@lists.infradead.org + Jens Axboe <axboe@kernel.dk> + linux-parisc@vger.kernel.org netdev@vger.kernel.org - keyrings@vger.kernel.org - " linux-security-module@vger.kernel.org\0" + linux-kernel@vger.kernel.org + linux-security-module@vger.kernel.org + linux-fsdevel@vger.kernel.org + Andrew Morton <akpm@linux-foundation.org> + " linuxppc-dev@lists.ozlabs.org\0" "\00:1\0" "b\0" "On Fri, Sep 18, 2020 at 02:40:12PM +0100, Al Viro wrote:\n" @@ -42,4 +42,4 @@ "I don't particularly like it either. But do you have a better idea\n" how to deal with io_uring vs compat tasks? -5cfdb88f3449260ee155d6479b2271b68cf03b6ce4927ef49992182af16a5dad +4d1df30bf046d68900e49b4c928c4869418299e82e795f75e67837cbedee69cb
diff --git a/a/1.txt b/N3/1.txt index 873357d..bd6f134 100644 --- a/a/1.txt +++ b/N3/1.txt @@ -9,3 +9,8 @@ On Fri, Sep 18, 2020 at 02:40:12PM +0100, Al Viro wrote: I don't particularly like it either. But do you have a better idea how to deal with io_uring vs compat tasks? + +_______________________________________________ +linux-arm-kernel mailing list +linux-arm-kernel@lists.infradead.org +http://lists.infradead.org/mailman/listinfo/linux-arm-kernel diff --git a/a/content_digest b/N3/content_digest index 354fad4..0bf0415 100644 --- a/a/content_digest +++ b/N3/content_digest @@ -5,29 +5,29 @@ "Subject\0Re: [PATCH 1/9] kernel: add a PF_FORCE_COMPAT flag\0" "Date\0Fri, 18 Sep 2020 15:44:06 +0200\0" "To\0Al Viro <viro@zeniv.linux.org.uk>\0" - "Cc\0Christoph Hellwig <hch@lst.de>" - Andrew Morton <akpm@linux-foundation.org> - Jens Axboe <axboe@kernel.dk> - Arnd Bergmann <arnd@arndb.de> - David Howells <dhowells@redhat.com> - linux-arm-kernel@lists.infradead.org - x86@kernel.org - linux-kernel@vger.kernel.org + "Cc\0linux-aio@kvack.org" linux-mips@vger.kernel.org - linux-parisc@vger.kernel.org - linuxppc-dev@lists.ozlabs.org - linux-s390@vger.kernel.org + David Howells <dhowells@redhat.com> + linux-mm@kvack.org + keyrings@vger.kernel.org sparclinux@vger.kernel.org - linux-block@vger.kernel.org + Christoph Hellwig <hch@lst.de> + linux-arch@vger.kernel.org + linux-s390@vger.kernel.org linux-scsi@vger.kernel.org - linux-fsdevel@vger.kernel.org - linux-aio@kvack.org + x86@kernel.org + Arnd Bergmann <arnd@arndb.de> + linux-block@vger.kernel.org io-uring@vger.kernel.org - linux-arch@vger.kernel.org - linux-mm@kvack.org + linux-arm-kernel@lists.infradead.org + Jens Axboe <axboe@kernel.dk> + linux-parisc@vger.kernel.org netdev@vger.kernel.org - keyrings@vger.kernel.org - " linux-security-module@vger.kernel.org\0" + linux-kernel@vger.kernel.org + linux-security-module@vger.kernel.org + linux-fsdevel@vger.kernel.org + Andrew Morton <akpm@linux-foundation.org> + " linuxppc-dev@lists.ozlabs.org\0" "\00:1\0" "b\0" "On Fri, Sep 18, 2020 at 02:40:12PM +0100, Al Viro wrote:\n" @@ -40,6 +40,11 @@ "> harder when it's controlled like that - witness set_fs() shite...\n" "\n" "I don't particularly like it either. But do you have a better idea\n" - how to deal with io_uring vs compat tasks? + "how to deal with io_uring vs compat tasks?\n" + "\n" + "_______________________________________________\n" + "linux-arm-kernel mailing list\n" + "linux-arm-kernel@lists.infradead.org\n" + http://lists.infradead.org/mailman/listinfo/linux-arm-kernel -5cfdb88f3449260ee155d6479b2271b68cf03b6ce4927ef49992182af16a5dad +de663deaa7be4f852d8cba92cb512d0cc44035d55e9f476b0c6e2310accf71f2
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.