netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ajay Kaher <akaher@vmware.com>
To: stable@vger.kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, alexanderduyck@fb.com, soheil@google.com,
	netdev@vger.kernel.org, namit@vmware.com, amakhalov@vmware.com,
	vsirnapalli@vmware.com, er.ajay.kaher@gmail.com,
	akaher@vmware.com
Subject: [PATCH 0/4 v6.1.y] net: fix roundup issue in kmalloc_reserve()
Date: Fri, 15 Sep 2023 23:51:01 +0530	[thread overview]
Message-ID: <1694802065-1821-1-git-send-email-akaher@vmware.com> (raw)

From: Eric Dumazet <edumazet@google.com>

This patch series is to backport upstream commit:
915d975b2ffa: net: deal with integer overflows in kmalloc_reserve()

patch 1-3/4 backport requires to apply patch 4/4 to fix roundup issue
in kmalloc_reserve()

1/4 net: add SKB_HEAD_ALIGN() helper
2/4 net: remove osize variable in __alloc_skb()
3/4 net: factorize code in kmalloc_reserve()
4/4 net: deal with integer overflows in kmalloc_reserve()

 include/linux/skbuff.h |  8 ++++++++
 net/core/skbuff.c      | 49 +++++++++++++++++++++----------------------------
 2 files changed, 29 insertions(+), 28 deletions(-)

-- 
2.7.4


             reply	other threads:[~2023-09-15 18:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 18:21 Ajay Kaher [this message]
2023-09-15 18:21 ` [PATCH v6.1.y 1/4] net: add SKB_HEAD_ALIGN() helper Ajay Kaher
2023-09-15 18:21 ` [PATCH v6.1.y 2/4] net: remove osize variable in __alloc_skb() Ajay Kaher
2023-09-15 18:21 ` [PATCH v6.1.y 3/4] net: factorize code in kmalloc_reserve() Ajay Kaher
2023-09-15 18:21 ` [PATCH v6.1.y 4/4] net: deal with integer overflows " Ajay Kaher
2023-09-16 11:30 ` [PATCH 0/4 v6.1.y] net: fix roundup issue " Greg KH

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=1694802065-1821-1-git-send-email-akaher@vmware.com \
    --to=akaher@vmware.com \
    --cc=alexanderduyck@fb.com \
    --cc=amakhalov@vmware.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=er.ajay.kaher@gmail.com \
    --cc=kuba@kernel.org \
    --cc=namit@vmware.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=soheil@google.com \
    --cc=stable@vger.kernel.org \
    --cc=vsirnapalli@vmware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).