[PATCH v2 06/16] igb: Proactively round up to kmalloc bucket size
Ruhl, Michael J
michael.j.ruhl at intel.com
Mon Sep 26 15:49:02 UTC 2022
>-----Original Message-----
>From: Kees Cook <keescook at chromium.org>
>Sent: Friday, September 23, 2022 4:28 PM
>To: Vlastimil Babka <vbabka at suse.cz>
>Cc: Kees Cook <keescook at chromium.org>; Brandeburg, Jesse
><jesse.brandeburg at intel.com>; Nguyen, Anthony L
><anthony.l.nguyen at intel.com>; David S. Miller <davem at davemloft.net>;
>Eric Dumazet <edumazet at google.com>; Jakub Kicinski <kuba at kernel.org>;
>Paolo Abeni <pabeni at redhat.com>; intel-wired-lan at lists.osuosl.org;
>netdev at vger.kernel.org; Ruhl, Michael J <michael.j.ruhl at intel.com>;
>Hyeonggon Yoo <42.hyeyoo at gmail.com>; Christoph Lameter
><cl at linux.com>; Pekka Enberg <penberg at kernel.org>; David Rientjes
><rientjes at google.com>; Joonsoo Kim <iamjoonsoo.kim at lge.com>; Andrew
>Morton <akpm at linux-foundation.org>; Greg Kroah-Hartman
><gregkh at linuxfoundation.org>; Nick Desaulniers
><ndesaulniers at google.com>; Alex Elder <elder at kernel.org>; Josef Bacik
><josef at toxicpanda.com>; David Sterba <dsterba at suse.com>; Sumit Semwal
><sumit.semwal at linaro.org>; Christian König <christian.koenig at amd.com>;
>Daniel Micay <danielmicay at gmail.com>; Yonghong Song <yhs at fb.com>;
>Marco Elver <elver at google.com>; Miguel Ojeda <ojeda at kernel.org>; linux-
>kernel at vger.kernel.org; linux-mm at kvack.org; linux-btrfs at vger.kernel.org;
>linux-media at vger.kernel.org; dri-devel at lists.freedesktop.org; linaro-mm-
>sig at lists.linaro.org; linux-fsdevel at vger.kernel.org; dev at openvswitch.org;
>x86 at kernel.org; llvm at lists.linux.dev; linux-hardening at vger.kernel.org
>Subject: [PATCH v2 06/16] igb: Proactively round up to kmalloc bucket size
>
>In preparation for removing the "silently change allocation size"
>users of ksize(), explicitly round up all q_vector allocations so that
>allocations can be correctly compared to ksize().
>
>Additionally fix potential use-after-free in the case of new allocation
>failure: only free memory if the replacement allocation succeeds.
>
>Cc: Jesse Brandeburg <jesse.brandeburg at intel.com>
>Cc: Tony Nguyen <anthony.l.nguyen at intel.com>
>Cc: "David S. Miller" <davem at davemloft.net>
>Cc: Eric Dumazet <edumazet at google.com>
>Cc: Jakub Kicinski <kuba at kernel.org>
>Cc: Paolo Abeni <pabeni at redhat.com>
>Cc: intel-wired-lan at lists.osuosl.org
>Cc: netdev at vger.kernel.org
>Signed-off-by: Kees Cook <keescook at chromium.org>
>---
> drivers/net/ethernet/intel/igb/igb_main.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/net/ethernet/intel/igb/igb_main.c
>b/drivers/net/ethernet/intel/igb/igb_main.c
>index 2796e81d2726..eb51e531c096 100644
>--- a/drivers/net/ethernet/intel/igb/igb_main.c
>+++ b/drivers/net/ethernet/intel/igb/igb_main.c
>@@ -1195,15 +1195,16 @@ static int igb_alloc_q_vector(struct igb_adapter
>*adapter,
> return -ENOMEM;
>
> ring_count = txr_count + rxr_count;
>- size = struct_size(q_vector, ring, ring_count);
>+ size = kmalloc_size_roundup(struct_size(q_vector, ring, ring_count));
This looks good to me...
> /* allocate q_vector and rings */
> q_vector = adapter->q_vector[v_idx];
> if (!q_vector) {
> q_vector = kzalloc(size, GFP_KERNEL);
> } else if (size > ksize(q_vector)) {
>- kfree_rcu(q_vector, rcu);
> q_vector = kzalloc(size, GFP_KERNEL);
>+ if (q_vector)
>+ kfree_rcu(q_vector, rcu);
Even though this is in the ksize part, this seems like an unrelated change?
Should this be in a different patch?
Also, the kfree_rcu will free q_vector after the RCU grace period?
Is that what you want to do?
How does rcu distinguish between the original q_vector, and the newly kzalloced one?
Thanks,
Mike
> } else {
> memset(q_vector, 0, size);
> }
>--
>2.34.1
More information about the dri-devel
mailing list