From: Greg KH <greg@kroah.com>
To: Philipp Hahn <hahn@univention.de>
Cc: Sasha Levin <alexander.levin@verizon.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
stable@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 10/16] scsi: arcmsr: Buffer overflow in arcmsr_iop_message_xfer()
Date: Thu, 15 Dec 2016 03:45:11 -0800 [thread overview]
Message-ID: <20161215114511.GA22556@kroah.com> (raw)
In-Reply-To: <605F437C-CB55-4D47-B0AC-22711089CE6C@univention.de>
On Thu, Dec 15, 2016 at 06:13:41AM +0100, Philipp Hahn wrote:
> Hi Greg,
> Sorry for the confusion. I have been working on our Kernel based on 4.1.36 and sent my work to Sasha for Integration into stable/4.1.y, but did not notice git sending those patches to all mentioned parties. Just ignore it.
Are these patches also in 4.4-stable and 4.8-stable?
thanks,
greg k-h
next prev parent reply other threads:[~2016-12-15 11:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1481713714.git.hahn@univention.de>
2016-12-14 12:24 ` [PATCH 10/16] scsi: arcmsr: Buffer overflow in arcmsr_iop_message_xfer() Philipp Hahn
2016-12-14 16:46 ` Greg KH
2016-12-15 5:13 ` Philipp Hahn
2016-12-15 11:45 ` Greg KH [this message]
2016-12-14 12:24 ` [PATCH 15/16] net: ping: check minimum size on ICMP header length Philipp Hahn
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=20161215114511.GA22556@kroah.com \
--to=greg@kroah.com \
--cc=alexander.levin@verizon.com \
--cc=dan.carpenter@oracle.com \
--cc=hahn@univention.de \
--cc=martin.petersen@oracle.com \
--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).