stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Chancellor <natechancellor@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Subject: Backport of 3f29770723fe
Date: Mon,  9 Apr 2018 11:05:22 -0700	[thread overview]
Message-ID: <20180409180525.32425-1-natechancellor@gmail.com> (raw)

Hi Greg,

Here is the backport of 3f29770723fe ("ipsec: check return value of
skb_to_sgvec always") for the 3.18, 4.4, and 4.9 trees, fixing the
warnings generated by 48a1df65334b ("skbuff: return -EMSGSIZE in
skb_to_sgvec to prevent overflow").

Let me know if there are any issues! First time using git send-email...
Nathan

             reply	other threads:[~2018-04-09 18:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 18:05 Nathan Chancellor [this message]
2018-04-09 18:05 ` [PATCH 3.18] ipsec: check return value of skb_to_sgvec always Nathan Chancellor
2018-04-09 18:05 ` [PATCH 4.4] " Nathan Chancellor
2018-04-09 18:05 ` [PATCH 4.9] " Nathan Chancellor
2018-04-09 20:25   ` Greg Kroah-Hartman
2018-04-10  6:23     ` Nathan Chancellor
2018-04-10  6:25       ` Greg Kroah-Hartman
2018-04-10 12:53 ` Backport of 3f29770723fe Greg Kroah-Hartman

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=20180409180525.32425-1-natechancellor@gmail.com \
    --to=natechancellor@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=stable@vger.kernel.org \
    /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).