All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Ruiqi Gong <gongruiqi@huaweicloud.com>,
	linux-mm@kvack.org, linux-hardening@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	cocci@inria.fr, Alexander Lobakin <aleksander.lobakin@intel.com>,
	Alexander Potapenko <glider@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <cl@linux.com>,
	David Rientjes <rientjes@google.com>,
	Dennis Zhou <dennis@kernel.org>,
	Dmitry Vyukov <dvyukov@google.com>,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>,
	James Morris <jmorris@namei.org>, Jann Horn <jannh@google.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Kees Cook <keescook@chromium.org>, Marco Elver <elver@google.com>,
	Paul Moore <paul@paul-moore.com>,
	Pedro Falcato <pedro.falcato@gmail.com>,
	Pekka Enberg <penberg@kernel.org>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	"Serge E . Hallyn" <serge@hallyn.com>, Tejun Heo <tj@kernel.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Wang Weiyang <wangweiyang2@huawei.com>,
	Xiu Jianfeng <xiujianfeng@huawei.com>
Subject: Re: [cocci] [PATCH v3 0/1] Randomized slab caches for kmalloc()
Date: Fri, 23 Jun 2023 10:30:18 +0200	[thread overview]
Message-ID: <570d788b-d7f3-64ab-97e1-4e847aef1321@web.de> (raw)
In-Reply-To: <20230616111843.3677378-1-gongruiqi@huaweicloud.com>

> I adapted the v2 patch to …

I suggest to omit the cover letter for a single patch.

Will any patch series evolve for your proposed changes?

Regards,
Markus

WARNING: multiple messages have this Message-ID (diff)
From: Markus Elfring <Markus.Elfring@web.de>
To: Ruiqi Gong <gongruiqi@huaweicloud.com>,
	linux-mm@kvack.org, linux-hardening@vger.kernel.org,
	kernel-janitors@vger.kernel.org
Cc: LKML <linux-kernel@vger.kernel.org>,
	cocci@inria.fr, Alexander Lobakin <aleksander.lobakin@intel.com>,
	Alexander Potapenko <glider@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <cl@linux.com>,
	David Rientjes <rientjes@google.com>,
	Dennis Zhou <dennis@kernel.org>,
	Dmitry Vyukov <dvyukov@google.com>,
	Hyeonggon Yoo <42.hyeyoo@gmail.com>,
	James Morris <jmorris@namei.org>, Jann Horn <jannh@google.com>,
	Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Kees Cook <keescook@chromium.org>, Marco Elver <elver@google.com>,
	Paul Moore <paul@paul-moore.com>,
	Pedro Falcato <pedro.falcato@gmail.com>,
	Pekka Enberg <penberg@kernel.org>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	"Serge E . Hallyn" <serge@hallyn.com>, Tejun Heo <tj@kernel.org>,
	Vlastimil Babka <vbabka@suse.cz>,
	Wang Weiyang <wangweiyang2@huawei.com>,
	Xiu Jianfeng <xiujianfeng@huawei.com>
Subject: Re: [PATCH v3 0/1] Randomized slab caches for kmalloc()
Date: Fri, 23 Jun 2023 10:30:18 +0200	[thread overview]
Message-ID: <570d788b-d7f3-64ab-97e1-4e847aef1321@web.de> (raw)
In-Reply-To: <20230616111843.3677378-1-gongruiqi@huaweicloud.com>

> I adapted the v2 patch to …

I suggest to omit the cover letter for a single patch.

Will any patch series evolve for your proposed changes?

Regards,
Markus


  parent reply	other threads:[~2023-06-23  8:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 11:18 [PATCH v3 0/1] Randomized slab caches for kmalloc() GONG, Ruiqi
2023-06-16 11:18 ` [PATCH v3 1/1] " GONG, Ruiqi
2023-06-21 18:21   ` Kees Cook
2023-06-25 11:25     ` GONG, Ruiqi
2023-06-22 13:56   ` Vlastimil Babka
2023-06-22 20:10     ` Kees Cook
2023-06-25 12:01       ` GONG, Ruiqi
2023-06-23  8:30 ` Markus Elfring [this message]
2023-06-23  8:30   ` [PATCH v3 0/1] " Markus Elfring
2023-06-26  0:56   ` GONG, Ruiqi
2023-06-26  9:18     ` [cocci] [v3 " Markus Elfring
2023-06-26  9:18       ` Markus Elfring

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=570d788b-d7f3-64ab-97e1-4e847aef1321@web.de \
    --to=markus.elfring@web.de \
    --cc=42.hyeyoo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=aleksander.lobakin@intel.com \
    --cc=cl@linux.com \
    --cc=cocci@inria.fr \
    --cc=dennis@kernel.org \
    --cc=dvyukov@google.com \
    --cc=elver@google.com \
    --cc=glider@google.com \
    --cc=gongruiqi@huaweicloud.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=jannh@google.com \
    --cc=jmorris@namei.org \
    --cc=keescook@chromium.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paul@paul-moore.com \
    --cc=pedro.falcato@gmail.com \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=roman.gushchin@linux.dev \
    --cc=serge@hallyn.com \
    --cc=tj@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=wangweiyang2@huawei.com \
    --cc=xiujianfeng@huawei.com \
    /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.