From: Greg KH <greg@kroah.com>
To: "Rantala, Tommi T. (Nokia - FI/Espoo)" <tommi.t.rantala@nokia.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4.14 0/8] uio backport fixes for 4.14
Date: Wed, 13 Feb 2019 19:36:00 +0100 [thread overview]
Message-ID: <20190213183600.GA29373@kroah.com> (raw)
In-Reply-To: <20190213162845.11688-1-tommi.t.rantala@nokia.com>
On Wed, Feb 13, 2019 at 04:29:12PM +0000, Rantala, Tommi T. (Nokia - FI/Espoo) wrote:
> Backport uio fixes to 4.14, to fix use-after-free memory errors.
>
> Changed __poll_t to unsigned int as the former not found in 4.14, and
> resolved some patch context conflicts.
Thanks for this, all now queued up.
greg k-h
prev parent reply other threads:[~2019-02-13 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 16:29 Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-13 16:29 ` [PATCH 4.14 1/8] uio: Reduce return paths from uio_write() Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-13 16:29 ` [PATCH 4.14 2/8] uio: Prevent device destruction while fds are open Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-13 16:29 ` [PATCH 4.14 3/8] uio: use request_threaded_irq instead Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-13 16:29 ` [PATCH 4.14 4/8] uio: change to use the mutex lock instead of the spin lock Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-13 16:29 ` [PATCH 4.14 5/8] uio: fix crash after the device is unregistered Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-13 16:29 ` [PATCH 4.14 7/8] uio: fix possible circular locking dependency Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-13 16:29 ` [PATCH 4.14 6/8] uio: fix wrong return value from uio_mmap() Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-13 16:29 ` [PATCH 4.14 8/8] Revert "uio: use request_threaded_irq instead" Rantala, Tommi T. (Nokia - FI/Espoo)
2019-02-13 18:36 ` 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=20190213183600.GA29373@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tommi.t.rantala@nokia.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
all inboxes | Powered by JetHome®