From: Wei Xu <xuwei5@hisilicon.com>
To: <arm@kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Olof Johansson <olof@lixom.net>, <arnd@arndb.de>
Cc: <linuxarm@huawei.com>, "xuwei (O)" <xuwei5@huawei.com>,
John Garry <john.garry@huawei.com>, <bhelgaas@google.com>,
<linux-pci@vger.kernel.org>, <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Zhangyi ac <zhangyi.ac@huawei.com>,
"Liguozhu (Kenneth)" <liguozhu@hisilicon.com>,
<jinying@hisilicon.com>, huangdaode <huangdaode@hisilicon.com>,
Tangkunshan <tangkunshan@huawei.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
Shiju Jose <shiju.jose@huawei.com>,
Salil Mehta <salil.mehta@huawei.com>
Subject: [GIT PULL] Hisilicon fixes for v5.2
Date: Tue, 25 Jun 2019 11:23:21 +0100 [thread overview]
Message-ID: <b89ef8f0-d102-7f78-f373-cbcc7faddee3@hisilicon.com> (raw)
Hi ARM-SoC team,
Please consider to pull the following changes.
Thanks!
Best Regards,
Wei
---
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://github.com/hisilicon/linux-hisi.git tags/hisi-fixes-for-5.2
for you to fetch changes up to 07c811af1c00d7b4212eac86900b023b6405a954:
lib: logic_pio: Enforce LOGIC_PIO_INDIRECT region ops are set at registration (2019-06-25 09:40:42 +0100)
----------------------------------------------------------------
Hisilicon fixes for v5.2-rc
- fixed RCU usage in logical PIO
- Added a function to unregister a logical PIO range in logical PIO
to support the fixes in the hisi-lpc driver
- fixed and optimized hisi-lpc driver to avoid potential use-after-free
and driver unbind crash
----------------------------------------------------------------
John Garry (6):
lib: logic_pio: Fix RCU usage
lib: logic_pio: Avoid possible overlap for unregistering regions
lib: logic_pio: Add logic_pio_unregister_range()
bus: hisi_lpc: Unregister logical PIO range to avoid potential use-after-free
bus: hisi_lpc: Add .remove method to avoid driver unbind crash
lib: logic_pio: Enforce LOGIC_PIO_INDIRECT region ops are set at registration
drivers/bus/hisi_lpc.c | 43 ++++++++++++++++++++----
include/linux/logic_pio.h | 1 +
lib/logic_pio.c | 86 +++++++++++++++++++++++++++++++++--------------
3 files changed, 99 insertions(+), 31 deletions(-)
next reply other threads:[~2019-06-25 10:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 10:23 Wei Xu [this message]
2019-06-25 10:39 ` [GIT PULL] Hisilicon fixes for v5.2 Wei Xu
2019-06-25 10:44 ` John Garry
2019-06-25 11:21 ` Olof Johansson
2019-06-25 13:03 ` Olof Johansson
2019-06-25 13:31 ` John Garry
2019-06-26 15:21 ` John Garry
2019-06-27 2:19 ` Olof Johansson
2019-07-01 6:22 ` Wei Xu
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=b89ef8f0-d102-7f78-f373-cbcc7faddee3@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=huangdaode@hisilicon.com \
--cc=jinying@hisilicon.com \
--cc=john.garry@huawei.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=salil.mehta@huawei.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shiju.jose@huawei.com \
--cc=tangkunshan@huawei.com \
--cc=xuwei5@huawei.com \
--cc=zhangyi.ac@huawei.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;
as well as URLs for NNTP newsgroup(s).