From: Vlastimil Babka <vbabka@suse.cz> To: Leon Romanovsky <leon@kernel.org>, Suren Baghdasaryan <surenb@google.com>, Laurent Dufour <ldufour@linux.ibm.com>, Sachin Sant <sachinp@linux.ibm.com>, Andrew Morton <akpm@linux-foundation.org> Cc: michel@lespinasse.org, jglisse@google.com, mhocko@suse.com, hannes@cmpxchg.org, mgorman@techsingularity.net, dave@stgolabs.net, willy@infradead.org, liam.howlett@oracle.com, peterz@infradead.org, paulmck@kernel.org, mingo@redhat.com, will@kernel.org, luto@kernel.org, songliubraving@fb.com, peterx@redhat.com, david@redhat.com, dhowells@redhat.com, hughd@google.com, bigeasy@linutronix.de, kent.overstreet@linux.dev, punit.agrawal@bytedance.com, lstoakes@gmail.com, peterjung1337@gmail.com, rientjes@google.com, chriscli@google.com, axelrasmussen@google.com, joelaf@google.com, minchan@google.com, rppt@kernel.org, jannh@google.com, shakeelb@google.com, tatashin@google.com, edumazet@google.com, gthelen@google.com, gurua@google.com, arjunroy@google.com, soheil@google.com, leewalsh@google.com, posk@google.com, michalechner92@googlemail.com, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, linuxppc-dev@lists.ozlabs.org, x86@kernel.org, linux-kernel@vger.kernel.org, kernel-team@android.com, regressions@leemhuis.info, Linux kernel regressions list <regressions@lists.linux.dev>, maorg@nvidia.com, gal@nvidia.com, ranro@nvidia.com, drort@nvidia.com, idok@nvidia.com, sergeyy@nvidia.com Subject: Re: [PATCH v4 00/33] Per-VMA locks Date: Tue, 11 Jul 2023 12:39:34 +0200 [thread overview] Message-ID: <53676850-539f-2813-d55d-a8bc0ec88092@suse.cz> (raw) In-Reply-To: <20230711103541.GA190975@unreal> On 7/11/23 12:35, Leon Romanovsky wrote: > > On Mon, Feb 27, 2023 at 09:35:59AM -0800, Suren Baghdasaryan wrote: > > <...> > >> Laurent Dufour (1): >> powerc/mm: try VMA lock-based page fault handling first > > Hi, > > This series and specifically the commit above broke docker over PPC. > It causes to docker service stuck while trying to activate. Revert of > this commit allows us to use docker again. Hi, there have been follow-up fixes, that are part of 6.4.3 stable (also 6.5-rc1) Does that version work for you? Vlastimil > [user@ppc-135-3-200-205 ~]# sudo systemctl status docker > ● docker.service - Docker Application Container Engine > Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) > Active: activating (start) since Mon 2023-06-26 14:47:07 IDT; 3h 50min ago > TriggeredBy: ● docker.socket > Docs: https://docs.docker.com > Main PID: 276555 (dockerd) > Memory: 44.2M > CGroup: /system.slice/docker.service > └─ 276555 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock > > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129383166+03:00" level=info msg="Graph migration to content-addressability took 0.00 se> > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129666160+03:00" level=warning msg="Your kernel does not support cgroup cfs period" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129684117+03:00" level=warning msg="Your kernel does not support cgroup cfs quotas" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129697085+03:00" level=warning msg="Your kernel does not support cgroup rt period" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129711513+03:00" level=warning msg="Your kernel does not support cgroup rt runtime" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129720656+03:00" level=warning msg="Unable to find blkio cgroup in mounts" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129805617+03:00" level=warning msg="mountpoint for pids not found" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.130199070+03:00" level=info msg="Loading containers: start." > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.132688568+03:00" level=warning msg="Running modprobe bridge br_netfilter failed with me> > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.271014050+03:00" level=info msg="Default bridge (docker0) is assigned with an IP addres> > > Python script which we used for bisect: > > import subprocess > import time > import sys > > > def run_command(cmd): > print('running:', cmd) > > p = subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE) > > try: > stdout, stderr = p.communicate(timeout=30) > > except subprocess.TimeoutExpired: > return True > > print(stdout.decode()) > print(stderr.decode()) > print('rc:', p.returncode) > > return False > > > def main(): > commands = [ > 'sudo systemctl stop docker', > 'sudo systemctl status docker', > 'sudo systemctl is-active docker', > 'sudo systemctl start docker', > 'sudo systemctl status docker', > ] > > for i in range(1000): > title = f'Try no. {i + 1}' > print('*' * 50, title, '*' * 50) > > for cmd in commands: > if run_command(cmd): > print(f'Reproduced on try no. {i + 1}!') > print(f'"{cmd}" is stuck!') > > return 1 > > print('\n') > time.sleep(30) > return 0 > > if __name__ == '__main__': > sys.exit(main()) > > Thanks
WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz> To: Leon Romanovsky <leon@kernel.org>, Suren Baghdasaryan <surenb@google.com>, Laurent Dufour <ldufour@linux.ibm.com>, Sachin Sant <sachinp@linux.ibm.com>, Andrew Morton <akpm@linux-foundation.org> Cc: michel@lespinasse.org, joelaf@google.com, songliubraving@fb.com, mhocko@suse.com, Linux kernel regressions list <regressions@lists.linux.dev>, leewalsh@google.com, david@redhat.com, peterz@infradead.org, bigeasy@linutronix.de, peterx@redhat.com, dhowells@redhat.com, linux-mm@kvack.org, edumazet@google.com, jglisse@google.com, punit.agrawal@bytedance.com, sergeyy@nvidia.com, will@kernel.org, arjunroy@google.com, chriscli@google.com, dave@stgolabs.net, minchan@google.com, gal@nvidia.com, x86@kernel.org, hughd@google.com, willy@infradead.org, gurua@google.com, mingo@redhat.com, rientjes@google.com, axelrasmussen@google.com, kernel-team@android.com, maorg@nvidia.com, ranro@nvidia.com, michalechner92@googlemail.com, soheil@google.com, paulmck@kernel.org, jannh@google.com, liam.howlett@oracle.com, regressions@leemhuis.info, shakeelb@google.com, drort@nvidia.com, luto@kernel.org, gthelen@google.com, linux-arm-kernel@lists.infradead.org, posk@google.com, lstoakes@gmail.com, peterjung1337 @gmail.com, linuxppc-dev@lists.ozlabs.org, kent.overstreet@linux.dev, linux-kernel@vger.kernel.org, idok@nvidia.com, hannes@cmpxchg.org, tatashin@google.com, mgorman@techsingularity.net, rppt@kernel.org Subject: Re: [PATCH v4 00/33] Per-VMA locks Date: Tue, 11 Jul 2023 12:39:34 +0200 [thread overview] Message-ID: <53676850-539f-2813-d55d-a8bc0ec88092@suse.cz> (raw) In-Reply-To: <20230711103541.GA190975@unreal> On 7/11/23 12:35, Leon Romanovsky wrote: > > On Mon, Feb 27, 2023 at 09:35:59AM -0800, Suren Baghdasaryan wrote: > > <...> > >> Laurent Dufour (1): >> powerc/mm: try VMA lock-based page fault handling first > > Hi, > > This series and specifically the commit above broke docker over PPC. > It causes to docker service stuck while trying to activate. Revert of > this commit allows us to use docker again. Hi, there have been follow-up fixes, that are part of 6.4.3 stable (also 6.5-rc1) Does that version work for you? Vlastimil > [user@ppc-135-3-200-205 ~]# sudo systemctl status docker > ● docker.service - Docker Application Container Engine > Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) > Active: activating (start) since Mon 2023-06-26 14:47:07 IDT; 3h 50min ago > TriggeredBy: ● docker.socket > Docs: https://docs.docker.com > Main PID: 276555 (dockerd) > Memory: 44.2M > CGroup: /system.slice/docker.service > └─ 276555 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock > > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129383166+03:00" level=info msg="Graph migration to content-addressability took 0.00 se> > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129666160+03:00" level=warning msg="Your kernel does not support cgroup cfs period" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129684117+03:00" level=warning msg="Your kernel does not support cgroup cfs quotas" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129697085+03:00" level=warning msg="Your kernel does not support cgroup rt period" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129711513+03:00" level=warning msg="Your kernel does not support cgroup rt runtime" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129720656+03:00" level=warning msg="Unable to find blkio cgroup in mounts" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.129805617+03:00" level=warning msg="mountpoint for pids not found" > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.130199070+03:00" level=info msg="Loading containers: start." > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.132688568+03:00" level=warning msg="Running modprobe bridge br_netfilter failed with me> > Jun 26 14:47:07 ppc-135-3-200-205 dockerd[276555]: time="2023-06-26T14:47:07.271014050+03:00" level=info msg="Default bridge (docker0) is assigned with an IP addres> > > Python script which we used for bisect: > > import subprocess > import time > import sys > > > def run_command(cmd): > print('running:', cmd) > > p = subprocess.Popen(cmd, shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE) > > try: > stdout, stderr = p.communicate(timeout=30) > > except subprocess.TimeoutExpired: > return True > > print(stdout.decode()) > print(stderr.decode()) > print('rc:', p.returncode) > > return False > > > def main(): > commands = [ > 'sudo systemctl stop docker', > 'sudo systemctl status docker', > 'sudo systemctl is-active docker', > 'sudo systemctl start docker', > 'sudo systemctl status docker', > ] > > for i in range(1000): > title = f'Try no. {i + 1}' > print('*' * 50, title, '*' * 50) > > for cmd in commands: > if run_command(cmd): > print(f'Reproduced on try no. {i + 1}!') > print(f'"{cmd}" is stuck!') > > return 1 > > print('\n') > time.sleep(30) > return 0 > > if __name__ == '__main__': > sys.exit(main()) > > Thanks
next prev parent reply other threads:[~2023-07-11 10:39 UTC|newest] Thread overview: 134+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-27 17:35 [PATCH v4 00/33] Per-VMA locks Suren Baghdasaryan 2023-02-27 17:35 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 01/33] maple_tree: Be more cautious about dead nodes Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 02/33] maple_tree: Detect dead nodes in mas_start() Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 03/33] maple_tree: Fix freeing of nodes in rcu mode Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 04/33] maple_tree: remove extra smp_wmb() from mas_dead_leaves() Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 05/33] maple_tree: Fix write memory barrier of nodes once dead for RCU mode Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 06/33] maple_tree: Add smp_rmb() to dead node detection Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 07/33] maple_tree: Add RCU lock checking to rcu callback functions Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 08/33] mm: Enable maple tree RCU mode by default Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 09/33] mm: introduce CONFIG_PER_VMA_LOCK Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 10/33] mm: rcu safe VMA freeing Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 11/33] mm: move mmap_lock assert function definitions Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 12/33] mm: add per-VMA lock and helper functions to control it Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 13/33] mm: mark VMA as being written when changing vm_flags Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 14/33] mm/mmap: move vma_prepare before vma_adjust_trans_huge Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 15/33] mm/khugepaged: write-lock VMA while collapsing a huge page Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 16/33] mm/mmap: write-lock VMAs in vma_prepare before modifying them Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 17/33] mm/mremap: write-lock VMA while remapping it to a new address range Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-03-01 7:01 ` Hyeonggon Yoo 2023-03-01 7:01 ` Hyeonggon Yoo 2023-02-27 17:36 ` [PATCH v4 18/33] mm: write-lock VMAs before removing them from VMA tree Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-03-01 7:43 ` Hyeonggon Yoo 2023-03-01 7:43 ` Hyeonggon Yoo 2023-03-01 7:56 ` Hyeonggon Yoo 2023-03-01 7:56 ` Hyeonggon Yoo 2023-03-01 18:34 ` Suren Baghdasaryan 2023-03-01 18:34 ` Suren Baghdasaryan 2023-03-01 18:42 ` Suren Baghdasaryan 2023-03-01 18:42 ` Suren Baghdasaryan 2023-03-02 0:53 ` Hyeonggon Yoo 2023-03-02 0:53 ` Hyeonggon Yoo 2023-03-02 2:21 ` Suren Baghdasaryan 2023-03-02 2:21 ` Suren Baghdasaryan 2023-03-01 19:07 ` Suren Baghdasaryan 2023-03-01 19:07 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 19/33] mm: conditionally write-lock VMA in free_pgtables Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 20/33] kernel/fork: assert no VMA readers during its destruction Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 21/33] mm/mmap: prevent pagefault handler from racing with mmu_notifier registration Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 22/33] mm: introduce vma detached flag Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 23/33] mm: introduce lock_vma_under_rcu to be used from arch-specific code Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 24/33] mm: fall back to mmap_lock if vma->anon_vma is not yet set Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-03-01 9:54 ` Hyeonggon Yoo 2023-03-01 9:54 ` Hyeonggon Yoo 2023-02-27 17:36 ` [PATCH v4 25/33] mm: add FAULT_FLAG_VMA_LOCK flag Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 26/33] mm: prevent do_swap_page from handling page faults under VMA lock Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 27/33] mm: prevent userfaults to be handled under per-vma lock Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 28/33] mm: introduce per-VMA lock statistics Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 29/33] x86/mm: try VMA lock-based page fault handling first Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-06-29 14:40 ` Jiri Slaby 2023-06-29 14:40 ` Jiri Slaby 2023-06-29 15:30 ` Suren Baghdasaryan 2023-06-29 15:30 ` Suren Baghdasaryan 2023-06-30 6:35 ` Jiri Slaby 2023-06-30 6:35 ` Jiri Slaby 2023-06-30 8:28 ` Jiri Slaby 2023-06-30 8:28 ` Jiri Slaby 2023-06-30 8:43 ` Jiri Slaby 2023-06-30 8:43 ` Jiri Slaby 2023-06-30 17:40 ` Suren Baghdasaryan 2023-06-30 17:40 ` Suren Baghdasaryan 2023-07-03 10:47 ` Jiri Slaby 2023-07-03 10:47 ` Jiri Slaby 2023-07-03 13:52 ` Holger Hoffstätte 2023-07-03 14:45 ` Suren Baghdasaryan 2023-07-03 15:24 ` Suren Baghdasaryan 2023-07-03 18:28 ` Suren Baghdasaryan 2023-07-05 22:15 ` Suren Baghdasaryan 2023-07-05 22:37 ` Holger Hoffstätte 2023-07-05 22:55 ` Suren Baghdasaryan 2023-07-06 14:27 ` Holger Hoffstätte 2023-07-06 16:11 ` Suren Baghdasaryan 2023-07-07 2:23 ` Suren Baghdasaryan 2023-07-07 4:40 ` Suren Baghdasaryan 2023-07-11 6:20 ` Jiri Slaby 2023-06-29 17:06 ` Linux regression tracking #adding (Thorsten Leemhuis) 2023-06-29 17:06 ` Linux regression tracking #adding (Thorsten Leemhuis) 2023-07-10 10:45 ` Linux regression tracking #update (Thorsten Leemhuis) 2023-07-03 9:58 ` Linux regression tracking (Thorsten Leemhuis) 2023-07-03 9:58 ` Linux regression tracking (Thorsten Leemhuis) 2023-02-27 17:36 ` [PATCH v4 30/33] arm64/mm: " Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 31/33] powerc/mm: " Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-03-06 15:42 ` [PATCH] powerpc/mm: fix mmap_lock bad unlock Laurent Dufour 2023-03-06 15:42 ` Laurent Dufour 2023-03-06 20:25 ` [PATCH v4 31/33] powerc/mm: try VMA lock-based page fault handling first Suren Baghdasaryan 2023-03-06 20:25 ` Suren Baghdasaryan 2023-03-06 20:25 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 32/33] mm/mmap: free vm_area_struct without call_rcu in exit_mmap Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-02-27 17:36 ` [PATCH v4 33/33] mm: separate vma->lock from vm_area_struct Suren Baghdasaryan 2023-02-27 17:36 ` Suren Baghdasaryan 2023-07-11 10:35 ` [PATCH v4 00/33] Per-VMA locks Leon Romanovsky 2023-07-11 10:35 ` Leon Romanovsky 2023-07-11 10:39 ` Vlastimil Babka [this message] 2023-07-11 10:39 ` Vlastimil Babka 2023-07-11 11:01 ` Leon Romanovsky 2023-07-11 11:01 ` Leon Romanovsky 2023-07-11 11:09 ` Leon Romanovsky 2023-07-11 11:09 ` Leon Romanovsky 2023-07-11 16:35 ` Suren Baghdasaryan 2023-07-11 16:35 ` Suren Baghdasaryan 2023-07-11 17:14 ` Leon Romanovsky 2023-07-11 17:14 ` Leon Romanovsky
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=53676850-539f-2813-d55d-a8bc0ec88092@suse.cz \ --to=vbabka@suse.cz \ --cc=akpm@linux-foundation.org \ --cc=arjunroy@google.com \ --cc=axelrasmussen@google.com \ --cc=bigeasy@linutronix.de \ --cc=chriscli@google.com \ --cc=dave@stgolabs.net \ --cc=david@redhat.com \ --cc=dhowells@redhat.com \ --cc=drort@nvidia.com \ --cc=edumazet@google.com \ --cc=gal@nvidia.com \ --cc=gthelen@google.com \ --cc=gurua@google.com \ --cc=hannes@cmpxchg.org \ --cc=hughd@google.com \ --cc=idok@nvidia.com \ --cc=jannh@google.com \ --cc=jglisse@google.com \ --cc=joelaf@google.com \ --cc=kent.overstreet@linux.dev \ --cc=kernel-team@android.com \ --cc=ldufour@linux.ibm.com \ --cc=leewalsh@google.com \ --cc=leon@kernel.org \ --cc=liam.howlett@oracle.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=lstoakes@gmail.com \ --cc=luto@kernel.org \ --cc=maorg@nvidia.com \ --cc=mgorman@techsingularity.net \ --cc=mhocko@suse.com \ --cc=michalechner92@googlemail.com \ --cc=michel@lespinasse.org \ --cc=minchan@google.com \ --cc=mingo@redhat.com \ --cc=paulmck@kernel.org \ --cc=peterjung1337@gmail.com \ --cc=peterx@redhat.com \ --cc=peterz@infradead.org \ --cc=posk@google.com \ --cc=punit.agrawal@bytedance.com \ --cc=ranro@nvidia.com \ --cc=regressions@leemhuis.info \ --cc=regressions@lists.linux.dev \ --cc=rientjes@google.com \ --cc=rppt@kernel.org \ --cc=sachinp@linux.ibm.com \ --cc=sergeyy@nvidia.com \ --cc=shakeelb@google.com \ --cc=soheil@google.com \ --cc=songliubraving@fb.com \ --cc=surenb@google.com \ --cc=tatashin@google.com \ --cc=will@kernel.org \ --cc=willy@infradead.org \ --cc=x86@kernel.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: linkBe 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.