From: ashwin-h <ashwinh@vmware.com>
To: <vyasevich@gmail.com>, <nhorman@tuxdriver.com>
Cc: <davem@davemloft.net>, <linux-sctp@vger.kernel.org>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<srivatsab@vmware.com>, <srivatsa@csail.mit.edu>,
<rostedt@goodmis.org>, <srostedt@vmware.com>,
<gregkh@linuxfoundation.org>, <ashwin.hiranniah@gmail.com>,
ashwin-h <ashwinh@vmware.com>
Subject: [PATCH 0/2] Backport to 4.19 - sctp: fully support memory accounting
Date: Wed, 6 May 2020 19:50:52 +0530 [thread overview]
Message-ID: <cover.1588242081.git.ashwinh@vmware.com> (raw)
Backport below upstream commits to 4.19 to address CVE-2019-3874.
1033990ac5b2ab6cee93734cb6d301aa3a35bcaa
sctp: implement memory accounting on tx path
9dde27de3e5efa0d032f3c891a0ca833a0d31911
sctp: implement memory accounting on rx path
Xin Long (2):
sctp: implement memory accounting on tx path
sctp: implement memory accounting on rx path
include/net/sctp/sctp.h | 2 +-
net/sctp/sm_statefuns.c | 6 ++++--
net/sctp/socket.c | 10 ++++++++--
net/sctp/ulpevent.c | 19 ++++++++-----------
net/sctp/ulpqueue.c | 3 ++-
5 files changed, 23 insertions(+), 17 deletions(-)
--
2.7.4
next reply other threads:[~2020-05-06 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 14:20 ashwin-h [this message]
2020-05-06 6:47 ` [PATCH 0/2] Backport to 4.19 - sctp: fully support memory accounting Greg KH
2020-05-06 14:20 ` [PATCH 1/2] sctp: implement memory accounting on tx path ashwin-h
2020-05-06 6:47 ` Greg KH
2020-05-06 14:20 ` [PATCH 2/2] sctp: implement memory accounting on rx path ashwin-h
2020-05-06 6:47 ` Greg KH
2020-05-08 17:24 ` [PATCH 0/2] Backport to 4.19 - sctp: fully support memory accounting Ashwin H
2020-05-08 23:23 ` David Miller
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=cover.1588242081.git.ashwinh@vmware.com \
--to=ashwinh@vmware.com \
--cc=ashwin.hiranniah@gmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=rostedt@goodmis.org \
--cc=srivatsa@csail.mit.edu \
--cc=srivatsab@vmware.com \
--cc=srostedt@vmware.com \
--cc=vyasevich@gmail.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).