From: Christoph Hellwig <hch@infradead.org>
To: Wang Haoran <haoranwangsec@gmail.com>
Cc: viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iov_iter: use kmemdup_array for dup_iter to harden against overflow
Date: Tue, 14 Apr 2026 01:18:59 -0700 [thread overview]
Message-ID: <ad34c8N-Z3-51anE@infradead.org> (raw)
In-Reply-To: <20260413060655.1139141-1-haoranwangsec@gmail.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2026-04-14 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 6:06 [PATCH] iov_iter: use kmemdup_array for dup_iter to harden against overflow Wang Haoran
2026-04-14 8:18 ` Christoph Hellwig [this message]
2026-04-14 9:46 ` Christian Brauner
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=ad34c8N-Z3-51anE@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=haoranwangsec@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox