From: Greg KH <gregkh@linuxfoundation.org>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: valentina.manea.m@gmail.com, shuah@kernel.org,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH 3.18 0/9] Backports for security and critical bug fixes
Date: Tue, 13 Feb 2018 17:00:00 +0100 [thread overview]
Message-ID: <20180213160000.GH14300@kroah.com> (raw)
In-Reply-To: <cover.1518036867.git.shuahkh@osg.samsung.com>
On Wed, Feb 07, 2018 at 02:20:23PM -0700, Shuah Khan wrote:
> As I started backporting security fixes, found a few problems
> that prevent tools to build on newer gcc releases, deadlock bug,
> and another bug that prevents client from being able to use
> imported devices.
>
> This patch series consists of security fixes and fixes to critical
> bugs.
All now applied, thanks!
greg k-h
prev parent reply other threads:[~2018-02-13 16:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 21:20 [PATCH 3.18 0/9] Backports for security and critical bug fixes Shuah Khan
2018-02-07 21:20 ` [PATCH 3.18 1/9] usbip: fix stub_rx: get_pipe() to validate endpoint number Shuah Khan
2018-02-07 21:20 ` [PATCH 3.18 2/9] usbip: fix stub_rx: harden CMD_SUBMIT path to handle malicious input Shuah Khan
2018-02-07 21:20 ` [PATCH 3.18 3/9] usbip: prevent vhci_hcd driver from leaking a socket pointer address Shuah Khan
2018-02-07 21:20 ` [PATCH 3.18 4/9] usbip: Fix potential format overflow in userspace tools Shuah Khan
2018-02-07 21:20 ` [PATCH 3.18 5/9] usb: usbip: Fix possible deadlocks reported by lockdep Shuah Khan
2018-02-07 21:20 ` [PATCH 3.18 6/9] usbip: vhci_hcd: clear just the USB_PORT_STAT_POWER bit Shuah Khan
2018-02-07 21:20 ` [PATCH 3.18 7/9] usbip: prevent leaking socket pointer address in messages Shuah Khan
2018-02-07 21:20 ` [PATCH 3.18 8/9] usbip: stub: stop printing kernel pointer addresses " Shuah Khan
2018-02-07 21:20 ` [PATCH 3.18 9/9] usbip: vhci: " Shuah Khan
2018-02-13 16:00 ` Greg KH [this message]
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=20180213160000.GH14300@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=stable@vger.kernel.org \
--cc=valentina.manea.m@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