From: Rafael Mendonca <rafaelmendsr@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jia-Ju Bai <baijiaju1990@gmail.com>,
Damian Hobson-Garcia <dhobsong@igel.co.jp>,
"Hans J. Koch" <hjk@hansjkoch.de>
Cc: Rafael Mendonca <rafaelmendsr@gmail.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] uio: uio_dmem_genirq: Fix locking issues in irq config and handling
Date: Fri, 30 Sep 2022 19:40:56 -0300 [thread overview]
Message-ID: <20220930224100.816175-1-rafaelmendsr@gmail.com> (raw)
The goal of this series is to apply the changes from [1] to the
"uio_dmem_genirq" driver. The implementation of "uio_dmem_genirq" was
based on "uio_pdrv_genirq" and it is used in a similar manner to the
"uio_pdrv_genirq" driver with respect to interrupt configuration and
handling. At the time "uio_dmem_genirq" was introduced, both had the
same implementation of the 'uio_info' handlers irqcontrol() and
handler(). Later, [1] was only applied to "uio_pdrv_genirq", even though
both had the same issues addressed by the patch, which ended up making
them a little different.
The original motivation for this series was to fix a bug introduced by
commit [2], which can be solved by copying the implementation of the
interrupt configuration and handling from "uio_pdrv_genirq" to
"uio_dmem_genirq", thus, making their implementation similar again.
Since patch [1] solves the bug introduced in [2] and also addresses
other issues, I broke it into 3 separate changes.
[1] 34cb27528398 ("UIO: Fix concurrency issue")
https://lore.kernel.org/lkml/201306201636.00535.vitas@nppfactor.kiev.ua/
[2] b74351287d4b ("uio: fix a sleep-in-atomic-context bug in
uio_dmem_genirq_irqcontrol()")
https://lore.kernel.org/all/20191218094405.6009-1-baijiaju1990@gmail.com/
Rafael Mendonca (3):
uio: uio_dmem_genirq: Fix missing unlock in irq configuration
uio: uio_dmem_genirq: Fix deadlock between irq config and handling
uio: uio_dmem_genirq: Use non-atomic bit operations in irq config and handling
drivers/uio/uio_dmem_genirq.c | 22 ++++++++++++++--------
1 file changed, 14 insertions(+), 8 deletions(-)
--
2.34.1
next reply other threads:[~2022-09-30 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 22:40 Rafael Mendonca [this message]
2022-09-30 22:40 ` [PATCH 1/3] uio: uio_dmem_genirq: Fix missing unlock in irq configuration Rafael Mendonca
2022-09-30 22:40 ` [PATCH 2/3] uio: uio_dmem_genirq: Fix deadlock between irq config and handling Rafael Mendonca
2022-09-30 22:40 ` [PATCH 3/3] uio: uio_dmem_genirq: Use non-atomic bit operations in " Rafael Mendonca
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=20220930224100.816175-1-rafaelmendsr@gmail.com \
--to=rafaelmendsr@gmail.com \
--cc=baijiaju1990@gmail.com \
--cc=dhobsong@igel.co.jp \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®