From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Bjorn Helgaas <bhelgaas@google.com>, linux-pci@vger.kernel.org
Cc: "Rick Wertenbroek" <rick.wertenbroek@gmail.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: [PATCH v3 15/16] misc: pci_endpoint_test: Do not write status in IRQ handler
Date: Sat, 25 Mar 2023 16:02:25 +0900 [thread overview]
Message-ID: <20230325070226.511323-16-damien.lemoal@opensource.wdc.com> (raw)
In-Reply-To: <20230325070226.511323-1-damien.lemoal@opensource.wdc.com>
pci_endpoint_test_irqhandler() always rewrites the status register when
an IRQ is raised, either as-is if STATUS_IRQ_RAISED is not set, or with
STATUS_IRQ_RAISED cleared if that flag is set. The first case creates a
race window with the endpoint side, meaning that the host side test
driver may end up reading what it just wrote, thus loosing the real
status as set by the endpoint side before raising the next interrupt.
This can prevent detecting that the STATUS_IRQ_RAISED flag was set by
the endpoint.
Remove this race window by not clearing the STATUS_IRQ_RAISED status
flag and not rewriting that register for every IRQ received.
Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
---
drivers/misc/pci_endpoint_test.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/misc/pci_endpoint_test.c b/drivers/misc/pci_endpoint_test.c
index 24efe3b88a1f..afd2577261f8 100644
--- a/drivers/misc/pci_endpoint_test.c
+++ b/drivers/misc/pci_endpoint_test.c
@@ -159,10 +159,7 @@ static irqreturn_t pci_endpoint_test_irqhandler(int irq, void *dev_id)
if (reg & STATUS_IRQ_RAISED) {
test->last_irq = irq;
complete(&test->irq_raised);
- reg &= ~STATUS_IRQ_RAISED;
}
- pci_endpoint_test_writel(test, PCI_ENDPOINT_TEST_STATUS,
- reg);
return IRQ_HANDLED;
}
--
2.39.2
next prev parent reply other threads:[~2023-03-25 7:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 7:02 [PATCH v3 00/16] PCI endpoint fixes and improvements Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 01/16] PCI: endpoint: Automatically create a function specific attributes group Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 02/16] PCI: endpoint: Move pci_epf_type_add_cfs() code Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 03/16] PCI: epf-test: Fix DMA transfer completion initialization Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 04/16] PCI: epf-test: Fix DMA transfer completion detection Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 05/16] PCI: epf-test: Use dmaengine_submit() to initiate DMA transfer Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 06/16] PCI: epf-test: Simplify read/write/copy test functions Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 07/16] PCI: epf-test: Simply pci_epf_test_raise_irq() Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 08/16] PCI: epf-test: Simplify IRQ test commands execution Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 09/16] PCI: epf-test: Improve handling of command and status registers Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 10/16] PCI: epf-test: Cleanup pci_epf_test_cmd_handler() Damien Le Moal
2023-03-28 6:56 ` Rick Wertenbroek
2023-03-29 1:02 ` Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 11/16] PCI: epf-test: Simplify dma support checks Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 12/16] PCI: epf-test: Simplify transfers result print Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 13/16] misc: pci_endpoint_test: Free IRQs before removing the device Damien Le Moal
2023-03-25 7:02 ` [PATCH v3 14/16] misc: pci_endpoint_test: Re-init completion for every test Damien Le Moal
2023-03-25 7:02 ` Damien Le Moal [this message]
2023-03-25 7:02 ` [PATCH v3 16/16] misc: pci_endpoint_test: Simplify pci_endpoint_test_msi_irq() Damien Le Moal
2023-03-28 17:57 ` [PATCH v3 00/16] PCI endpoint fixes and improvements Bjorn Helgaas
2023-03-31 10:20 ` Kishon Vijay Abraham I
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=20230325070226.511323-16-damien.lemoal@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=rick.wertenbroek@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;
as well as URLs for NNTP newsgroup(s).