All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Michael J Ruhl <michael.j.ruhl@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, linux-kernel@vger.kernel.org,
	Eric Dumazet <edumazet@google.com>,
	linux-hardening@vger.kernel.org, netdev@vger.kernel.org,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH v3 0/2] igb: Proactively round up to kmalloc bucket size
Date: Tue, 18 Oct 2022 03:09:33 -0700	[thread overview]
Message-ID: <202210180307.484A016FE0@keescook> (raw)
In-Reply-To: <20221018092340.never.556-kees@kernel.org>

On Tue, Oct 18, 2022 at 02:25:23AM -0700, Kees Cook wrote:
> Kees Cook (2):
>   igb: Do not free q_vector unless new one was allocated
>   igb: Proactively round up to kmalloc bucket size
> 
>  drivers/net/ethernet/intel/igb/igb_main.c | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)

Ugh, yay for my MUA vs commas. Sorry for any future typo bounce spam. :(

-- 
Kees Cook
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

WARNING: multiple messages have this Message-ID (diff)
From: Kees Cook <keescook@chromium.org>
To: Michael J Ruhl <michael.j.ruhl@intel.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
	Tony Nguyen <anthony.l.nguyen@intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	netdev@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v3 0/2] igb: Proactively round up to kmalloc bucket size
Date: Tue, 18 Oct 2022 03:09:33 -0700	[thread overview]
Message-ID: <202210180307.484A016FE0@keescook> (raw)
In-Reply-To: <20221018092340.never.556-kees@kernel.org>

On Tue, Oct 18, 2022 at 02:25:23AM -0700, Kees Cook wrote:
> Kees Cook (2):
>   igb: Do not free q_vector unless new one was allocated
>   igb: Proactively round up to kmalloc bucket size
> 
>  drivers/net/ethernet/intel/igb/igb_main.c | 10 +++++++---
>  1 file changed, 7 insertions(+), 3 deletions(-)

Ugh, yay for my MUA vs commas. Sorry for any future typo bounce spam. :(

-- 
Kees Cook

  parent reply	other threads:[~2022-10-18 10:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  9:25 [Intel-wired-lan] [PATCH v3 0/2] igb: Proactively round up to kmalloc bucket size Kees Cook
2022-10-18  9:25 ` Kees Cook
2022-10-18  9:25 ` [Intel-wired-lan] [PATCH v3 1/2] igb: Do not free q_vector unless new one was allocated Kees Cook
2022-10-18  9:25   ` Kees Cook
2022-10-18 12:20   ` [Intel-wired-lan] " Ruhl, Michael J
2022-10-18 12:20     ` Ruhl, Michael J
2022-10-20 21:59     ` [Intel-wired-lan] " Jacob Keller
2022-10-29  3:29   ` G, GurucharanX
2022-10-29  3:29     ` G, GurucharanX
2022-10-18  9:25 ` [Intel-wired-lan] [PATCH v3 2/2] igb: Proactively round up to kmalloc bucket size Kees Cook
2022-10-18  9:25   ` Kees Cook
2022-10-29  3:17   ` [Intel-wired-lan] " Kees Cook
2022-10-29  3:17     ` Kees Cook
2022-10-31 20:42     ` [Intel-wired-lan] " Ruhl, Michael J
2022-10-31 20:42       ` Ruhl, Michael J
2022-11-01 21:37       ` [Intel-wired-lan] " Kees Cook
2022-11-01 21:37         ` Kees Cook
2022-11-02 14:12         ` [Intel-wired-lan] " Ruhl, Michael J
2022-11-02 14:12           ` Ruhl, Michael J
2022-10-29  3:30   ` [Intel-wired-lan] " G, GurucharanX
2022-10-29  3:30     ` G, GurucharanX
2022-10-18 10:09 ` Kees Cook [this message]
2022-10-18 10:09   ` [PATCH v3 0/2] " Kees Cook

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=202210180307.484A016FE0@keescook \
    --to=keescook@chromium.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=linux-hardening@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.j.ruhl@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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.