From: Gabriel Krisman Bertazi <krisman@suse.de>
To: Breno Leitao <leitao@debian.org>
Cc: axboe@kernel.dk, asml.silence@gmail.com,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org,
gustavold@meta.com, leit@meta.com, kasan-dev@googlegroups.com
Subject: Re: [PATCH v3 2/2] io_uring: Add KASAN support for alloc_caches
Date: Thu, 23 Feb 2023 16:09:24 -0300 [thread overview]
Message-ID: <87sfewryfv.fsf@suse.de> (raw)
In-Reply-To: <20230223164353.2839177-3-leitao@debian.org> (Breno Leitao's message of "Thu, 23 Feb 2023 08:43:53 -0800")
Breno Leitao <leitao@debian.org> writes:
> Add support for KASAN in the alloc_caches (apoll and netmsg_cache).
> Thus, if something touches the unused caches, it will raise a KASAN
> warning/exception.
>
> It poisons the object when the object is put to the cache, and unpoisons
> it when the object is gotten or freed.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
> ---
> include/linux/io_uring_types.h | 1 +
> io_uring/alloc_cache.h | 6 +++++-
> io_uring/io_uring.c | 4 ++--
> io_uring/net.h | 5 ++++-
> 4 files changed, 12 insertions(+), 4 deletions(-)
>
> diff --git a/include/linux/io_uring_types.h b/include/linux/io_uring_types.h
> index efa66b6c32c9..35ebcfb46047 100644
> --- a/include/linux/io_uring_types.h
> +++ b/include/linux/io_uring_types.h
> @@ -190,6 +190,7 @@ struct io_ev_fd {
> struct io_alloc_cache {
> struct io_wq_work_node list;
> unsigned int nr_cached;
> + size_t elem_size;
> };
>
> struct io_ring_ctx {
> diff --git a/io_uring/alloc_cache.h b/io_uring/alloc_cache.h
> index 301855e94309..3aba7b356320 100644
> --- a/io_uring/alloc_cache.h
> +++ b/io_uring/alloc_cache.h
> @@ -16,6 +16,8 @@ static inline bool io_alloc_cache_put(struct io_alloc_cache *cache,
> if (cache->nr_cached < IO_ALLOC_CACHE_MAX) {
> cache->nr_cached++;
> wq_stack_add_head(&entry->node, &cache->list);
> + /* KASAN poisons object */
> + kasan_slab_free_mempool(entry);
> return true;
> }
> return false;
> @@ -27,6 +29,7 @@ static inline struct io_cache_entry *io_alloc_cache_get(struct io_alloc_cache *c
> struct io_cache_entry *entry;
>
> entry = container_of(cache->list.next, struct io_cache_entry, node);
> + kasan_unpoison_range(entry, cache->elem_size);
I kind of worry there is no type checking at the same time we are
unpoisoning a constant-size range. Seems easy to misuse the API. But it
does look much better now with elem_size cached inside io_alloc_cache.
>
> -#if defined(CONFIG_NET)
> struct io_async_msghdr {
> +#if defined(CONFIG_NET)
> union {
> struct iovec fast_iov[UIO_FASTIOV];
> struct {
> @@ -22,8 +22,11 @@ struct io_async_msghdr {
> struct sockaddr __user *uaddr;
> struct msghdr msg;
> struct sockaddr_storage addr;
> +#endif
> };
>
> +#if defined(CONFIG_NET)
> +
Nit, but you could have added an empty definition in the #else section
that already exists in the file, or just guarded the caching code
entirely when CONFIG_NET=n.
Just nits, and overall it is good to have this KASAN support!
Reviewed-by: Gabriel Krisman Bertazi <krisman@suse.de>
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2023-02-23 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 16:43 [PATCH v3 0/2] io_uring: Add KASAN support for alloc caches Breno Leitao
2023-02-23 16:43 ` [PATCH v3 1/2] io_uring: Move from hlist to io_wq_work_node Breno Leitao
2023-02-23 19:02 ` Gabriel Krisman Bertazi
2023-02-23 19:39 ` Jens Axboe
2023-02-24 18:32 ` Gabriel Krisman Bertazi
2023-02-24 19:41 ` Jens Axboe
2023-02-24 9:55 ` Breno Leitao
2023-02-23 16:43 ` [PATCH v3 2/2] io_uring: Add KASAN support for alloc_caches Breno Leitao
2023-02-23 19:09 ` Gabriel Krisman Bertazi [this message]
2023-03-16 19:01 ` [PATCH v3 0/2] io_uring: Add KASAN support for alloc caches Jens Axboe
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=87sfewryfv.fsf@suse.de \
--to=krisman@suse.de \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=gustavold@meta.com \
--cc=io-uring@vger.kernel.org \
--cc=kasan-dev@googlegroups.com \
--cc=leit@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.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: 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.