From: Alexander Potapenko <glider@google.com> To: kernel test robot <lkp@intel.com> Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org, Alexander Viro <viro@zeniv.linux.org.uk>, Alexei Starovoitov <ast@kernel.org>, Andrew Morton <akpm@linux-foundation.org>, Linux Memory Management List <linux-mm@kvack.org>, Andrey Konovalov <andreyknvl@google.com>, Andy Lutomirski <luto@kernel.org>, Arnd Bergmann <arnd@arndb.de>, Borislav Petkov <bp@alien8.de>, Christoph Hellwig <hch@lst.de>, Christoph Lameter <cl@linux-foundation.org>, David Rientjes <rientjes@google.com>, Dmitry Vyukov <dvyukov@google.com>, Eric Dumazet <edumazet@google.com>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Herbert Xu <herbert@gondor.apana.org.au>, Ilya Leoshkevich <iii@linux.ibm.com>, Ingo Molnar <mingo@redhat.com>, Jens Axboe <axboe@kernel.dk>, Joonsoo Kim <iamjoonsoo.kim@lge.com>, Kees Cook <keescook@chromium.org>, Marco Elver <elver@google.com>, Mark Rutland <mark.rutland@arm.com>, Matthew Wilcox <willy@infradead.org>, "Michael S. Tsirkin" <mst@redhat.com>, Pekka Enberg <penberg@kernel.org>, Peter Zijlstra <peterz@infradead.org>, Petr Mladek <pmladek@suse.com>, Steven Rostedt <rostedt@goodmis.org>, Thomas Gleixner <tglx@linutronix.de> Subject: Re: [PATCH v4 04/45] x86: asm: instrument usercopy in get_user() and __put_user_size() Date: Fri, 15 Jul 2022 18:44:38 +0200 [thread overview] Message-ID: <CAG_fn=UOWkegr1oeD8h1OKXBCv-ZM0uePGcGtCrdVv+CRGkWGw@mail.gmail.com> (raw) In-Reply-To: <202207021844.0J4s1Gjz-lkp@intel.com> On Sat, Jul 2, 2022 at 12:46 PM kernel test robot <lkp@intel.com> wrote: > > Hi Alexander, > > I love your patch! Yet something to improve: > > [auto build test ERROR on masahiroy-kbuild/for-next] > [also build test ERROR on linus/master v5.19-rc4 next-20220701] > [cannot apply to tip/x86/core tip/x86/mm] > [If your patch is applied to the wrong git tree, kindly drop us a note. > And when submitting patch, we suggest to use '--base' as documented in > https://git-scm.com/docs/git-format-patch] > > url: https://github.com/intel-lab-lkp/linux/commits/Alexander-Potapenko/Add-KernelMemorySanitizer-infrastructure/20220701-222712 > base: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git for-next > config: i386-randconfig-a011 (https://download.01.org/0day-ci/archive/20220702/202207021844.0J4s1Gjz-lkp@intel.com/config) > compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project a9119143a2d1f4d0d0bc1fe0d819e5351b4e0deb) > reproduce (this is a W=1 build): > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # https://github.com/intel-lab-lkp/linux/commit/0ca0e4029535365a65588446ba55a952ca186079 > git remote add linux-review https://github.com/intel-lab-lkp/linux > git fetch --no-tags linux-review Alexander-Potapenko/Add-KernelMemorySanitizer-infrastructure/20220701-222712 > git checkout 0ca0e4029535365a65588446ba55a952ca186079 > # save the config file > mkdir build_dir && cp config build_dir/.config > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash > > If you fix the issue, kindly add following tag where applicable > Reported-by: kernel test robot <lkp@intel.com> Uh oh, this is a very good catch. > All errors (new ones prefixed by >>): > > >> arch/x86/math-emu/reg_ld_str.c:1043:3: error: address of bit-field requested > FPU_get_user(instruction_address.selector, > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > arch/x86/math-emu/fpu_system.h:127:36: note: expanded from macro 'FPU_get_user' > #define FPU_get_user(x,y) do { if (get_user((x),(y))) FPU_abort; } while (0) > ~~~~^~~~~~~~~~~~~~~~~~ > arch/x86/include/asm/uaccess.h:131:43: note: expanded from macro 'get_user' > #define get_user(x,ptr) ({ might_fault(); do_get_user_call(get_user,x,ptr); }) > ^ > arch/x86/include/asm/uaccess.h:103:43: note: expanded from macro 'do_get_user_call' > instrument_copy_from_user_before((void *)&(x), ptr, sizeof(*(ptr))); \ > ^ > include/linux/compiler.h:56:47: note: expanded from macro 'if' > #define if(cond, ...) if ( __trace_if_var( !!(cond , ## __VA_ARGS__) ) ) > ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ > include/linux/compiler.h:58:52: note: expanded from macro '__trace_if_var' > #define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) : __trace_if_value(cond)) > ^~~~ > >> arch/x86/math-emu/reg_ld_str.c:1043:3: error: address of bit-field requested > FPU_get_user(instruction_address.selector, > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Actually `x` in get_user(x, ptr) and put_user(x, ptr) is not guaranteed to be addressable (e.g. in this case it is a bitfield). We can copy the values to a local var, like it's done in __put_user_size: 254 __typeof__(*(ptr)) __pus_val = x; \ 255 __chk_user_ptr(ptr); \ 256 instrument_copy_to_user(ptr, &(__pus_val), size); \ , but this won't help KASAN or KCSAN detect the bugs accessing x. Perhaps a better solution would be to declare instrument_get_user() and instrument_put_user(), which will unpoison/check the values for KMSAN and do nothing for other tools. -- Alexander Potapenko Software Engineer Google Germany GmbH Erika-Mann-Straße, 33 80636 München Geschäftsführer: Paul Manicle, Liana Sebastian Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Potapenko <glider@google.com> To: kbuild-all@lists.01.org Subject: Re: [PATCH v4 04/45] x86: asm: instrument usercopy in get_user() and __put_user_size() Date: Fri, 15 Jul 2022 18:44:38 +0200 [thread overview] Message-ID: <CAG_fn=UOWkegr1oeD8h1OKXBCv-ZM0uePGcGtCrdVv+CRGkWGw@mail.gmail.com> (raw) In-Reply-To: <202207021844.0J4s1Gjz-lkp@intel.com> [-- Attachment #1: Type: text/plain, Size: 4444 bytes --] On Sat, Jul 2, 2022 at 12:46 PM kernel test robot <lkp@intel.com> wrote: > > Hi Alexander, > > I love your patch! Yet something to improve: > > [auto build test ERROR on masahiroy-kbuild/for-next] > [also build test ERROR on linus/master v5.19-rc4 next-20220701] > [cannot apply to tip/x86/core tip/x86/mm] > [If your patch is applied to the wrong git tree, kindly drop us a note. > And when submitting patch, we suggest to use '--base' as documented in > https://git-scm.com/docs/git-format-patch] > > url: https://github.com/intel-lab-lkp/linux/commits/Alexander-Potapenko/Add-KernelMemorySanitizer-infrastructure/20220701-222712 > base: https://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git for-next > config: i386-randconfig-a011 (https://download.01.org/0day-ci/archive/20220702/202207021844.0J4s1Gjz-lkp(a)intel.com/config) > compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project a9119143a2d1f4d0d0bc1fe0d819e5351b4e0deb) > reproduce (this is a W=1 build): > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # https://github.com/intel-lab-lkp/linux/commit/0ca0e4029535365a65588446ba55a952ca186079 > git remote add linux-review https://github.com/intel-lab-lkp/linux > git fetch --no-tags linux-review Alexander-Potapenko/Add-KernelMemorySanitizer-infrastructure/20220701-222712 > git checkout 0ca0e4029535365a65588446ba55a952ca186079 > # save the config file > mkdir build_dir && cp config build_dir/.config > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=i386 SHELL=/bin/bash > > If you fix the issue, kindly add following tag where applicable > Reported-by: kernel test robot <lkp@intel.com> Uh oh, this is a very good catch. > All errors (new ones prefixed by >>): > > >> arch/x86/math-emu/reg_ld_str.c:1043:3: error: address of bit-field requested > FPU_get_user(instruction_address.selector, > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > arch/x86/math-emu/fpu_system.h:127:36: note: expanded from macro 'FPU_get_user' > #define FPU_get_user(x,y) do { if (get_user((x),(y))) FPU_abort; } while (0) > ~~~~^~~~~~~~~~~~~~~~~~ > arch/x86/include/asm/uaccess.h:131:43: note: expanded from macro 'get_user' > #define get_user(x,ptr) ({ might_fault(); do_get_user_call(get_user,x,ptr); }) > ^ > arch/x86/include/asm/uaccess.h:103:43: note: expanded from macro 'do_get_user_call' > instrument_copy_from_user_before((void *)&(x), ptr, sizeof(*(ptr))); \ > ^ > include/linux/compiler.h:56:47: note: expanded from macro 'if' > #define if(cond, ...) if ( __trace_if_var( !!(cond , ## __VA_ARGS__) ) ) > ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ > include/linux/compiler.h:58:52: note: expanded from macro '__trace_if_var' > #define __trace_if_var(cond) (__builtin_constant_p(cond) ? (cond) : __trace_if_value(cond)) > ^~~~ > >> arch/x86/math-emu/reg_ld_str.c:1043:3: error: address of bit-field requested > FPU_get_user(instruction_address.selector, > ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Actually `x` in get_user(x, ptr) and put_user(x, ptr) is not guaranteed to be addressable (e.g. in this case it is a bitfield). We can copy the values to a local var, like it's done in __put_user_size: 254 __typeof__(*(ptr)) __pus_val = x; \ 255 __chk_user_ptr(ptr); \ 256 instrument_copy_to_user(ptr, &(__pus_val), size); \ , but this won't help KASAN or KCSAN detect the bugs accessing x. Perhaps a better solution would be to declare instrument_get_user() and instrument_put_user(), which will unpoison/check the values for KMSAN and do nothing for other tools. -- Alexander Potapenko Software Engineer Google Germany GmbH Erika-Mann-Straße, 33 80636 München Geschäftsführer: Paul Manicle, Liana Sebastian Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg
next prev parent reply other threads:[~2022-07-15 16:45 UTC|newest] Thread overview: 147+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-01 14:22 [PATCH v4 00/45] Add KernelMemorySanitizer infrastructure Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 01/45] x86: add missing include to sparsemem.h Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 02/45] stackdepot: reserve 5 extra bits in depot_stack_handle_t Alexander Potapenko 2022-07-12 14:17 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 03/45] instrumented.h: allow instrumenting both sides of copy_from_user() Alexander Potapenko 2022-07-12 14:17 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 04/45] x86: asm: instrument usercopy in get_user() and __put_user_size() Alexander Potapenko 2022-07-02 3:47 ` kernel test robot 2022-07-15 14:03 ` Alexander Potapenko 2022-07-15 14:03 ` Alexander Potapenko 2022-07-02 10:45 ` kernel test robot 2022-07-15 16:44 ` Alexander Potapenko [this message] 2022-07-15 16:44 ` Alexander Potapenko 2022-07-02 13:09 ` kernel test robot 2022-07-07 10:13 ` Marco Elver 2022-08-07 17:33 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 05/45] asm-generic: instrument usercopy in cacheflush.h Alexander Potapenko 2022-07-12 14:17 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 06/45] kmsan: add ReST documentation Alexander Potapenko 2022-07-07 12:34 ` Marco Elver 2022-07-15 7:42 ` Alexander Potapenko 2022-07-15 8:52 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 07/45] kmsan: introduce __no_sanitize_memory and __no_kmsan_checks Alexander Potapenko 2022-07-12 14:17 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 08/45] kmsan: mark noinstr as __no_sanitize_memory Alexander Potapenko 2022-07-12 14:17 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 09/45] x86: kmsan: pgtable: reduce vmalloc space Alexander Potapenko 2022-07-11 16:12 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 10/45] libnvdimm/pfn_dev: increase MAX_STRUCT_PAGE_SIZE Alexander Potapenko 2022-07-11 16:26 ` Marco Elver 2022-08-03 9:41 ` Alexander Potapenko 2022-08-03 9:44 ` Alexander Potapenko 2023-01-05 22:08 ` Dan Williams 2023-01-09 9:51 ` Alexander Potapenko 2023-01-09 22:06 ` Dan Williams 2023-01-10 5:56 ` Greg Kroah-Hartman 2023-01-10 6:55 ` Dan Williams 2023-01-10 8:48 ` Alexander Potapenko 2023-01-10 8:52 ` Alexander Potapenko 2023-01-10 8:53 ` Eric Dumazet 2023-01-10 8:55 ` Christoph Hellwig 2023-01-10 15:35 ` Steven Rostedt 2023-01-10 9:14 ` Alexander Potapenko 2023-01-30 8:34 ` Alexander Potapenko 2023-01-30 18:57 ` Dan Williams 2022-07-01 14:22 ` [PATCH v4 11/45] kmsan: add KMSAN runtime core Alexander Potapenko 2022-07-02 0:18 ` Hillf Danton 2022-08-03 17:25 ` Alexander Potapenko 2022-07-11 16:49 ` Marco Elver 2022-08-03 18:14 ` Alexander Potapenko 2022-07-13 10:04 ` Marco Elver 2022-08-03 17:45 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 12/45] kmsan: disable instrumentation of unsupported common kernel code Alexander Potapenko 2022-07-12 11:54 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 13/45] MAINTAINERS: add entry for KMSAN Alexander Potapenko 2022-07-12 12:06 ` Marco Elver 2022-08-02 16:39 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 14/45] mm: kmsan: maintain KMSAN metadata for page operations Alexander Potapenko 2022-07-12 12:20 ` Marco Elver 2022-08-03 10:30 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 15/45] mm: kmsan: call KMSAN hooks from SLUB code Alexander Potapenko 2022-07-12 13:13 ` Marco Elver 2022-08-02 16:31 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 16/45] kmsan: handle task creation and exiting Alexander Potapenko 2022-07-12 13:17 ` Marco Elver 2022-08-02 15:47 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 17/45] init: kmsan: call KMSAN initialization routines Alexander Potapenko 2022-07-12 14:05 ` Marco Elver 2022-08-02 20:07 ` Alexander Potapenko 2022-08-03 9:08 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 18/45] instrumented.h: add KMSAN support Alexander Potapenko 2022-07-12 13:51 ` Marco Elver 2022-08-03 11:17 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 19/45] kmsan: unpoison @tlb in arch_tlb_gather_mmu() Alexander Potapenko 2022-07-13 9:28 ` Marco Elver 2022-07-01 14:22 ` [PATCH v4 20/45] kmsan: add iomap support Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 21/45] Input: libps2: mark data received in __ps2_command() as initialized Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 22/45] dma: kmsan: unpoison DMA mappings Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 23/45] virtio: kmsan: check/unpoison scatterlist in vring_map_one_sg() Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 24/45] kmsan: handle memory sent to/from USB Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 25/45] kmsan: add tests for KMSAN Alexander Potapenko 2022-07-12 14:16 ` Marco Elver 2022-08-02 17:29 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 26/45] kmsan: disable strscpy() optimization under KMSAN Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 27/45] crypto: kmsan: disable accelerated configs " Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 28/45] kmsan: disable physical page merging in biovec Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 29/45] block: kmsan: skip bio block merging logic for KMSAN Alexander Potapenko 2022-07-13 10:22 ` Marco Elver 2022-08-02 17:47 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 30/45] kcov: kmsan: unpoison area->list in kcov_remote_area_put() Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 31/45] security: kmsan: fix interoperability with auto-initialization Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 32/45] objtool: kmsan: list KMSAN API functions as uaccess-safe Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 33/45] x86: kmsan: disable instrumentation of unsupported code Alexander Potapenko 2022-07-12 13:43 ` Marco Elver 2022-08-03 10:52 ` Alexander Potapenko 2022-07-01 14:22 ` [PATCH v4 34/45] x86: kmsan: skip shadow checks in __switch_to() Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 35/45] x86: kmsan: handle open-coded assembly in lib/iomem.c Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 36/45] x86: kmsan: use __msan_ string functions where possible Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 37/45] x86: kmsan: sync metadata pages on page fault Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 38/45] x86: kasan: kmsan: support CONFIG_GENERIC_CSUM on x86, enable it for KASAN/KMSAN Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 39/45] x86: fs: kmsan: disable CONFIG_DCACHE_WORD_ACCESS Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 40/45] x86: kmsan: don't instrument stack walking functions Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 41/45] entry: kmsan: introduce kmsan_unpoison_entry_regs() Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 42/45] bpf: kmsan: initialize BPF registers with zeroes Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 43/45] namei: initialize parameters passed to step_into() Alexander Potapenko 2022-07-02 17:23 ` Linus Torvalds 2022-07-03 3:59 ` Al Viro 2022-07-04 2:52 ` Al Viro 2022-07-04 8:20 ` Alexander Potapenko 2022-07-04 13:44 ` Al Viro 2022-07-04 13:55 ` Al Viro 2022-07-04 15:49 ` Alexander Potapenko 2022-07-04 16:03 ` Greg Kroah-Hartman 2022-07-04 16:33 ` Alexander Potapenko 2022-07-04 18:23 ` Segher Boessenkool 2022-07-04 16:00 ` Al Viro 2022-07-04 16:47 ` Alexander Potapenko 2022-07-04 17:36 ` Linus Torvalds 2022-07-04 19:02 ` Al Viro 2022-07-04 19:16 ` Linus Torvalds 2022-07-04 19:55 ` Al Viro 2022-07-04 20:24 ` Linus Torvalds 2022-07-04 20:46 ` Al Viro 2022-07-04 20:51 ` Linus Torvalds 2022-07-04 21:04 ` Al Viro 2022-07-04 23:13 ` [PATCH 1/7] __follow_mount_rcu(): verify that mount_lock remains unchanged Al Viro 2022-07-04 23:14 ` [PATCH 2/7] follow_dotdot{,_rcu}(): change calling conventions Al Viro 2022-07-04 23:14 ` [PATCH 3/7] namei: stash the sampled ->d_seq into nameidata Al Viro 2022-07-04 23:15 ` [PATCH 4/7] step_into(): lose inode argument Al Viro 2022-07-04 23:15 ` [PATCH 5/7] follow_dotdot{,_rcu}(): don't bother with inode Al Viro 2022-07-04 23:16 ` [PATCH 6/7] lookup_fast(): " Al Viro 2022-07-04 23:17 ` [PATCH 7/7] step_into(): move fetching ->d_inode past handle_mounts() Al Viro 2022-07-04 23:19 ` [PATCH 1/7] __follow_mount_rcu(): verify that mount_lock remains unchanged Al Viro 2022-07-05 0:06 ` Linus Torvalds 2022-07-05 3:48 ` Al Viro 2022-07-04 20:47 ` [PATCH v4 43/45] namei: initialize parameters passed to step_into() Linus Torvalds 2022-08-08 16:37 ` Alexander Potapenko 2022-07-01 14:23 ` [PATCH v4 44/45] mm: fs: initialize fsdata passed to write_begin/write_end interface Alexander Potapenko 2022-07-04 20:07 ` Matthew Wilcox 2022-07-04 20:30 ` Al Viro 2022-08-25 15:39 ` Alexander Potapenko 2022-08-25 16:33 ` Linus Torvalds 2022-08-25 21:57 ` Segher Boessenkool 2022-08-26 19:41 ` Linus Torvalds 2022-08-31 13:32 ` Alexander Potapenko 2022-08-25 22:13 ` Segher Boessenkool 2022-07-01 14:23 ` [PATCH v4 45/45] x86: kmsan: enable KMSAN builds for x86 Alexander Potapenko
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='CAG_fn=UOWkegr1oeD8h1OKXBCv-ZM0uePGcGtCrdVv+CRGkWGw@mail.gmail.com' \ --to=glider@google.com \ --cc=akpm@linux-foundation.org \ --cc=andreyknvl@google.com \ --cc=arnd@arndb.de \ --cc=ast@kernel.org \ --cc=axboe@kernel.dk \ --cc=bp@alien8.de \ --cc=cl@linux-foundation.org \ --cc=dvyukov@google.com \ --cc=edumazet@google.com \ --cc=elver@google.com \ --cc=gregkh@linuxfoundation.org \ --cc=hch@lst.de \ --cc=herbert@gondor.apana.org.au \ --cc=iamjoonsoo.kim@lge.com \ --cc=iii@linux.ibm.com \ --cc=kbuild-all@lists.01.org \ --cc=keescook@chromium.org \ --cc=linux-mm@kvack.org \ --cc=lkp@intel.com \ --cc=llvm@lists.linux.dev \ --cc=luto@kernel.org \ --cc=mark.rutland@arm.com \ --cc=mingo@redhat.com \ --cc=mst@redhat.com \ --cc=penberg@kernel.org \ --cc=peterz@infradead.org \ --cc=pmladek@suse.com \ --cc=rientjes@google.com \ --cc=rostedt@goodmis.org \ --cc=tglx@linutronix.de \ --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: 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.