From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
Paul Mackerras <paulus@ozlabs.org>,
Alexander 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, kvm-ppc@vger.kernel.org,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v8 00/17] gfs2: Fix mmap + page fault deadlocks
Date: Thu, 28 Oct 2021 22:40:25 +0100 [thread overview]
Message-ID: <YXsYyWIKjvm6a9GX@arm.com> (raw)
In-Reply-To: <YXsUNMWFpmT1eQcX@arm.com>
On Thu, Oct 28, 2021 at 10:20:52PM +0100, Catalin Marinas wrote:
> On Wed, Oct 27, 2021 at 02:14:48PM -0700, Linus Torvalds wrote:
> > On Wed, Oct 27, 2021 at 12:13 PM Catalin Marinas
> > <catalin.marinas@arm.com> wrote:
> > > As an alternative, you mentioned earlier that a per-thread fault status
> > > was not feasible on x86 due to races. Was this only for the hw poison
> > > case? I think the uaccess is slightly different.
> >
> > It's not x86-specific, it's very generic.
> >
> > If we set some flag in the per-thread status, we'll need to be careful
> > about not overwriting it if we then have a subsequent NMI that _also_
> > takes a (completely unrelated) page fault - before we then read the
> > per-thread flag.
> >
> > Think 'perf' and fetching backtraces etc.
> >
> > Note that the NMI page fault can easily also be a pointer coloring
> > fault on arm64, for exactly the same reason that whatever original
> > copy_from_user() code was. So this is not a "oh, pointer coloring
> > faults are different". They have the same re-entrancy issue.
> >
> > And both the "pagefault_disable" and "fault happens in interrupt
> > context" cases are also the exact same 'faulthandler_disabled()'
> > thing. So even at fault time they look very similar.
>
> They do look fairly similar but we should have the information in the
> fault handler to distinguish: not a page fault (pte permission or p*d
> translation), in_task(), user address, fixup handler. But I agree the
> logic looks fragile.
>
> I think for nested contexts we can save the uaccess fault state on
> exception entry, restore it on return. Or (needs some thinking on
> atomicity) save it in a local variable. The high-level API would look
> something like:
>
> unsigned long uaccess_flags; /* we could use TIF_ flags */
>
> uaccess_flags = begin_retriable_uaccess();
> copied = copy_page_from_iter_atomic(...);
> retry = end_retriable_uaccess(uaccess_flags);
It doesn't work with local flags, so it would need to be saved on
exception entry (interrupt, breakpoint etc.) on the stack, restore on
return. But the API would return pretty close (and probably still more
complicated than copy_*() returning an error code).
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: kvm-ppc@vger.kernel.org, Christoph Hellwig <hch@infradead.org>,
cluster-devel <cluster-devel@redhat.com>, Jan Kara <jack@suse.cz>,
Andreas Gruenbacher <agruenba@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@ozlabs.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
ocfs2-devel@oss.oracle.com
Subject: Re: [Ocfs2-devel] [PATCH v8 00/17] gfs2: Fix mmap + page fault deadlocks
Date: Thu, 28 Oct 2021 22:40:25 +0100 [thread overview]
Message-ID: <YXsYyWIKjvm6a9GX@arm.com> (raw)
In-Reply-To: <YXsUNMWFpmT1eQcX@arm.com>
On Thu, Oct 28, 2021 at 10:20:52PM +0100, Catalin Marinas wrote:
> On Wed, Oct 27, 2021 at 02:14:48PM -0700, Linus Torvalds wrote:
> > On Wed, Oct 27, 2021 at 12:13 PM Catalin Marinas
> > <catalin.marinas@arm.com> wrote:
> > > As an alternative, you mentioned earlier that a per-thread fault status
> > > was not feasible on x86 due to races. Was this only for the hw poison
> > > case? I think the uaccess is slightly different.
> >
> > It's not x86-specific, it's very generic.
> >
> > If we set some flag in the per-thread status, we'll need to be careful
> > about not overwriting it if we then have a subsequent NMI that _also_
> > takes a (completely unrelated) page fault - before we then read the
> > per-thread flag.
> >
> > Think 'perf' and fetching backtraces etc.
> >
> > Note that the NMI page fault can easily also be a pointer coloring
> > fault on arm64, for exactly the same reason that whatever original
> > copy_from_user() code was. So this is not a "oh, pointer coloring
> > faults are different". They have the same re-entrancy issue.
> >
> > And both the "pagefault_disable" and "fault happens in interrupt
> > context" cases are also the exact same 'faulthandler_disabled()'
> > thing. So even at fault time they look very similar.
>
> They do look fairly similar but we should have the information in the
> fault handler to distinguish: not a page fault (pte permission or p*d
> translation), in_task(), user address, fixup handler. But I agree the
> logic looks fragile.
>
> I think for nested contexts we can save the uaccess fault state on
> exception entry, restore it on return. Or (needs some thinking on
> atomicity) save it in a local variable. The high-level API would look
> something like:
>
> unsigned long uaccess_flags; /* we could use TIF_ flags */
>
> uaccess_flags = begin_retriable_uaccess();
> copied = copy_page_from_iter_atomic(...);
> retry = end_retriable_uaccess(uaccess_flags);
It doesn't work with local flags, so it would need to be saved on
exception entry (interrupt, breakpoint etc.) on the stack, restore on
return. But the API would return pretty close (and probably still more
complicated than copy_*() returning an error code).
--
Catalin
_______________________________________________
Ocfs2-devel mailing list
Ocfs2-devel@oss.oracle.com
https://oss.oracle.com/mailman/listinfo/ocfs2-devel
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH v8 00/17] gfs2: Fix mmap + page fault deadlocks
Date: Thu, 28 Oct 2021 22:40:25 +0100 [thread overview]
Message-ID: <YXsYyWIKjvm6a9GX@arm.com> (raw)
In-Reply-To: <YXsUNMWFpmT1eQcX@arm.com>
On Thu, Oct 28, 2021 at 10:20:52PM +0100, Catalin Marinas wrote:
> On Wed, Oct 27, 2021 at 02:14:48PM -0700, Linus Torvalds wrote:
> > On Wed, Oct 27, 2021 at 12:13 PM Catalin Marinas
> > <catalin.marinas@arm.com> wrote:
> > > As an alternative, you mentioned earlier that a per-thread fault status
> > > was not feasible on x86 due to races. Was this only for the hw poison
> > > case? I think the uaccess is slightly different.
> >
> > It's not x86-specific, it's very generic.
> >
> > If we set some flag in the per-thread status, we'll need to be careful
> > about not overwriting it if we then have a subsequent NMI that _also_
> > takes a (completely unrelated) page fault - before we then read the
> > per-thread flag.
> >
> > Think 'perf' and fetching backtraces etc.
> >
> > Note that the NMI page fault can easily also be a pointer coloring
> > fault on arm64, for exactly the same reason that whatever original
> > copy_from_user() code was. So this is not a "oh, pointer coloring
> > faults are different". They have the same re-entrancy issue.
> >
> > And both the "pagefault_disable" and "fault happens in interrupt
> > context" cases are also the exact same 'faulthandler_disabled()'
> > thing. So even at fault time they look very similar.
>
> They do look fairly similar but we should have the information in the
> fault handler to distinguish: not a page fault (pte permission or p*d
> translation), in_task(), user address, fixup handler. But I agree the
> logic looks fragile.
>
> I think for nested contexts we can save the uaccess fault state on
> exception entry, restore it on return. Or (needs some thinking on
> atomicity) save it in a local variable. The high-level API would look
> something like:
>
> unsigned long uaccess_flags; /* we could use TIF_ flags */
>
> uaccess_flags = begin_retriable_uaccess();
> copied = copy_page_from_iter_atomic(...);
> retry = end_retriable_uaccess(uaccess_flags);
It doesn't work with local flags, so it would need to be saved on
exception entry (interrupt, breakpoint etc.) on the stack, restore on
return. But the API would return pretty close (and probably still more
complicated than copy_*() returning an error code).
--
Catalin
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
Paul Mackerras <paulus@ozlabs.org>,
Alexander 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, kvm-ppc@vger.kernel.org,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v8 00/17] gfs2: Fix mmap + page fault deadlocks
Date: Thu, 28 Oct 2021 21:40:25 +0000 [thread overview]
Message-ID: <YXsYyWIKjvm6a9GX@arm.com> (raw)
In-Reply-To: <YXsUNMWFpmT1eQcX@arm.com>
On Thu, Oct 28, 2021 at 10:20:52PM +0100, Catalin Marinas wrote:
> On Wed, Oct 27, 2021 at 02:14:48PM -0700, Linus Torvalds wrote:
> > On Wed, Oct 27, 2021 at 12:13 PM Catalin Marinas
> > <catalin.marinas@arm.com> wrote:
> > > As an alternative, you mentioned earlier that a per-thread fault status
> > > was not feasible on x86 due to races. Was this only for the hw poison
> > > case? I think the uaccess is slightly different.
> >
> > It's not x86-specific, it's very generic.
> >
> > If we set some flag in the per-thread status, we'll need to be careful
> > about not overwriting it if we then have a subsequent NMI that _also_
> > takes a (completely unrelated) page fault - before we then read the
> > per-thread flag.
> >
> > Think 'perf' and fetching backtraces etc.
> >
> > Note that the NMI page fault can easily also be a pointer coloring
> > fault on arm64, for exactly the same reason that whatever original
> > copy_from_user() code was. So this is not a "oh, pointer coloring
> > faults are different". They have the same re-entrancy issue.
> >
> > And both the "pagefault_disable" and "fault happens in interrupt
> > context" cases are also the exact same 'faulthandler_disabled()'
> > thing. So even at fault time they look very similar.
>
> They do look fairly similar but we should have the information in the
> fault handler to distinguish: not a page fault (pte permission or p*d
> translation), in_task(), user address, fixup handler. But I agree the
> logic looks fragile.
>
> I think for nested contexts we can save the uaccess fault state on
> exception entry, restore it on return. Or (needs some thinking on
> atomicity) save it in a local variable. The high-level API would look
> something like:
>
> unsigned long uaccess_flags; /* we could use TIF_ flags */
>
> uaccess_flags = begin_retriable_uaccess();
> copied = copy_page_from_iter_atomic(...);
> retry = end_retriable_uaccess(uaccess_flags);
It doesn't work with local flags, so it would need to be saved on
exception entry (interrupt, breakpoint etc.) on the stack, restore on
return. But the API would return pretty close (and probably still more
complicated than copy_*() returning an error code).
--
Catalin
next prev parent reply other threads:[~2021-10-28 21:40 UTC|newest]
Thread overview: 188+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 13:41 [PATCH v8 00/17] gfs2: Fix mmap + page fault deadlocks Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 01/17] iov_iter: Fix iov_iter_get_pages{,_alloc} page fault return value Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] [PATCH v8 01/17] iov_iter: Fix iov_iter_get_pages{, _alloc} " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 02/17] powerpc/kvm: Fix kvm_use_magic_page Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 03/17] gup: Turn fault_in_pages_{readable,writeable} into fault_in_{readable,writeable} Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] [PATCH v8 03/17] gup: Turn fault_in_pages_{readable, writeable} into fault_in_{readable, writeable} Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 04/17] iov_iter: Turn iov_iter_fault_in_readable into fault_in_iov_iter_readable Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 05/17] iov_iter: Introduce fault_in_iov_iter_writeable Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-20 16:25 ` Catalin Marinas
2021-10-20 16:25 ` Catalin Marinas
2021-10-20 16:25 ` [Cluster-devel] " Catalin Marinas
2021-10-20 16:25 ` [Ocfs2-devel] " Catalin Marinas
2021-10-19 13:41 ` [PATCH v8 06/17] gfs2: Add wrapper for iomap_file_buffered_write Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 07/17] gfs2: Clean up function may_grant Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 08/17] gfs2: Introduce flag for glock holder auto-demotion Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 09/17] gfs2: Move the inode glock locking to gfs2_file_buffered_write Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 10/17] gfs2: Eliminate ip->i_gh Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 11/17] gfs2: Fix mmap + page fault deadlocks for buffered I/O Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [PATCH v8 12/17] iomap: Fix iomap_dio_rw return value for user copies Andreas Gruenbacher
2021-10-19 13:41 ` Andreas Gruenbacher
2021-10-19 13:41 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:41 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:42 ` [PATCH v8 13/17] iomap: Support partial direct I/O on user copy failures Andreas Gruenbacher
2021-10-19 13:42 ` Andreas Gruenbacher
2021-10-19 13:42 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:42 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:42 ` [PATCH v8 14/17] iomap: Add done_before argument to iomap_dio_rw Andreas Gruenbacher
2021-10-19 13:42 ` Andreas Gruenbacher
2021-10-19 13:42 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:42 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 15:51 ` Darrick J. Wong
2021-10-19 15:51 ` Darrick J. Wong
2021-10-19 15:51 ` [Cluster-devel] " Darrick J. Wong
2021-10-19 15:51 ` Darrick J. Wong
2021-10-19 19:30 ` Andreas Gruenbacher
2021-10-19 19:30 ` Andreas Gruenbacher
2021-10-19 19:30 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 19:30 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-20 1:57 ` Darrick J. Wong
2021-10-20 1:57 ` Darrick J. Wong
2021-10-20 1:57 ` [Cluster-devel] " Darrick J. Wong
2021-10-20 1:57 ` [Ocfs2-devel] " Darrick J. Wong
2021-10-19 13:42 ` [PATCH v8 15/17] gup: Introduce FOLL_NOFAULT flag to disable page faults Andreas Gruenbacher
2021-10-19 13:42 ` Andreas Gruenbacher
2021-10-19 13:42 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:42 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:42 ` [PATCH v8 16/17] iov_iter: Introduce nofault " Andreas Gruenbacher
2021-10-19 13:42 ` Andreas Gruenbacher
2021-10-19 13:42 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:42 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 13:42 ` [PATCH v8 17/17] gfs2: Fix mmap + page fault deadlocks for direct I/O Andreas Gruenbacher
2021-10-19 13:42 ` Andreas Gruenbacher
2021-10-19 13:42 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-19 13:42 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-19 15:40 ` [PATCH v8 00/17] gfs2: Fix mmap + page fault deadlocks Linus Torvalds
2021-10-19 15:40 ` Linus Torvalds
2021-10-19 15:40 ` [Cluster-devel] " Linus Torvalds
2021-10-19 15:40 ` [Ocfs2-devel] " Linus Torvalds
2021-10-19 15:59 ` Bob Peterson
2021-10-19 16:00 ` [Cluster-devel] " Bob Peterson
2021-10-19 16:00 ` [Ocfs2-devel] " Bob Peterson
2021-10-19 16:00 ` Bob Peterson
2021-10-20 16:36 ` Catalin Marinas
2021-10-20 16:36 ` Catalin Marinas
2021-10-20 16:36 ` [Cluster-devel] " Catalin Marinas
2021-10-20 16:36 ` [Ocfs2-devel] " Catalin Marinas
2021-10-20 20:11 ` Linus Torvalds
2021-10-20 20:11 ` Linus Torvalds
2021-10-20 20:11 ` [Cluster-devel] " Linus Torvalds
2021-10-20 20:11 ` [Ocfs2-devel] " Linus Torvalds
2021-10-20 22:44 ` Catalin Marinas
2021-10-20 22:44 ` Catalin Marinas
2021-10-20 22:44 ` [Cluster-devel] " Catalin Marinas
2021-10-20 22:44 ` [Ocfs2-devel] " Catalin Marinas
2021-10-21 6:19 ` Linus Torvalds
2021-10-21 6:19 ` Linus Torvalds
2021-10-21 6:19 ` [Cluster-devel] " Linus Torvalds
2021-10-21 6:19 ` [Ocfs2-devel] " Linus Torvalds
2021-10-22 18:06 ` Catalin Marinas
2021-10-22 18:06 ` Catalin Marinas
2021-10-22 18:06 ` [Cluster-devel] " Catalin Marinas
2021-10-22 18:06 ` [Ocfs2-devel] " Catalin Marinas
2021-10-22 19:22 ` Linus Torvalds
2021-10-22 19:22 ` Linus Torvalds
2021-10-22 19:22 ` [Cluster-devel] " Linus Torvalds
2021-10-22 19:22 ` [Ocfs2-devel] " Linus Torvalds
2021-10-25 18:59 ` Andreas Gruenbacher
2021-10-25 19:00 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-25 19:00 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-25 19:00 ` Andreas Gruenbacher
2021-10-26 18:24 ` Catalin Marinas
2021-10-26 18:24 ` Catalin Marinas
2021-10-26 18:24 ` [Cluster-devel] " Catalin Marinas
2021-10-26 18:24 ` [Ocfs2-devel] " Catalin Marinas
2021-10-26 18:50 ` Linus Torvalds
2021-10-26 18:50 ` Linus Torvalds
2021-10-26 18:50 ` [Cluster-devel] " Linus Torvalds
2021-10-26 18:50 ` [Ocfs2-devel] " Linus Torvalds
2021-10-26 19:18 ` Linus Torvalds
2021-10-26 19:18 ` Linus Torvalds
2021-10-26 19:18 ` [Cluster-devel] " Linus Torvalds
2021-10-26 19:18 ` [Ocfs2-devel] " Linus Torvalds
2021-10-27 19:13 ` Catalin Marinas
2021-10-27 19:13 ` Catalin Marinas
2021-10-27 19:13 ` [Cluster-devel] " Catalin Marinas
2021-10-27 19:13 ` [Ocfs2-devel] " Catalin Marinas
2021-10-27 21:14 ` Linus Torvalds
2021-10-27 21:14 ` Linus Torvalds
2021-10-27 21:14 ` [Cluster-devel] " Linus Torvalds
2021-10-27 21:14 ` [Ocfs2-devel] " Linus Torvalds
2021-10-28 21:20 ` Catalin Marinas
2021-10-28 21:20 ` Catalin Marinas
2021-10-28 21:20 ` [Cluster-devel] " Catalin Marinas
2021-10-28 21:20 ` [Ocfs2-devel] " Catalin Marinas
2021-10-28 21:40 ` Catalin Marinas [this message]
2021-10-28 21:40 ` Catalin Marinas
2021-10-28 21:40 ` [Cluster-devel] " Catalin Marinas
2021-10-28 21:40 ` [Ocfs2-devel] " Catalin Marinas
2021-10-28 22:15 ` Andreas Grünbacher
2021-10-28 22:15 ` Andreas Grünbacher
2021-10-28 22:15 ` [Cluster-devel] " Andreas Grünbacher
2021-10-28 22:15 ` [Ocfs2-devel] " Andreas Grünbacher
2021-10-29 12:50 ` Catalin Marinas
2021-10-29 12:50 ` Catalin Marinas
2021-10-29 12:50 ` [Cluster-devel] " Catalin Marinas
2021-10-29 12:50 ` [Ocfs2-devel] " Catalin Marinas
2021-10-28 22:32 ` Linus Torvalds
2021-10-28 22:32 ` Linus Torvalds
2021-10-28 22:32 ` [Cluster-devel] " Linus Torvalds
2021-10-28 22:32 ` [Ocfs2-devel] " Linus Torvalds
2021-10-29 17:50 ` Catalin Marinas
2021-10-29 17:50 ` Catalin Marinas
2021-10-29 17:50 ` [Cluster-devel] " Catalin Marinas
2021-10-29 17:50 ` [Ocfs2-devel] " Catalin Marinas
2021-10-29 18:47 ` Linus Torvalds
2021-10-29 18:47 ` Linus Torvalds
2021-10-29 18:47 ` [Cluster-devel] " Linus Torvalds
2021-10-29 18:47 ` [Ocfs2-devel] " Linus Torvalds
2021-10-25 18:24 ` Andreas Gruenbacher
2021-10-25 18:24 ` Andreas Gruenbacher
2021-10-25 18:24 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-25 18:24 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-26 5:12 ` Theodore Ts'o
2021-10-26 5:12 ` Theodore Ts'o
2021-10-26 5:12 ` [Cluster-devel] " Theodore Ts'o
2021-10-26 5:12 ` [Ocfs2-devel] " Theodore Ts'o
2021-10-26 9:44 ` Andreas Gruenbacher
2021-10-26 9:44 ` Andreas Gruenbacher
2021-10-26 9:44 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-26 9:44 ` [Ocfs2-devel] " Andreas Gruenbacher
2021-10-27 21:21 ` Andreas Gruenbacher
2021-10-27 21:21 ` Andreas Gruenbacher
2021-10-27 21:21 ` [Cluster-devel] " Andreas Gruenbacher
2021-10-27 21:21 ` [Ocfs2-devel] " Andreas Gruenbacher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YXsYyWIKjvm6a9GX@arm.com \
--to=catalin.marinas@arm.com \
--cc=agruenba@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=paulus@ozlabs.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.