public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Ursula Braun <ubraun@linux.vnet.ibm.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
	schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
	ubraun@linux.vnet.ibm.com, dan.carpenter@oracle.com
Subject: [PATCH net-next 0/1] smc: fix potential use after free
Date: Mon, 30 Jan 2017 10:55:03 +0100	[thread overview]
Message-ID: <20170130095504.7940-1-ubraun@linux.vnet.ibm.com> (raw)

From: Ursula Braun <ursula.braun@de.ibm.com>

Hi Dave,

please add Dan's fix for the smc-code. Thanks, Dan and Dave!

Regards, Ursula Braun

Dan Carpenter (1):
  smc: Reset rx/tx buffer descriptor in case of errors

 net/smc/smc_core.c | 5 +++++
 1 file changed, 5 insertions(+)

-- 
2.8.4

             reply	other threads:[~2017-01-30  9:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30  9:55 Ursula Braun [this message]
2017-01-30  9:55 ` [PATCH net-next 1/1] smc: some potential use after free bugs Ursula Braun
2017-01-30 21:38   ` 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=20170130095504.7940-1-ubraun@linux.vnet.ibm.com \
    --to=ubraun@linux.vnet.ibm.com \
    --cc=dan.carpenter@oracle.com \
    --cc=davem@davemloft.net \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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