From: Marek Vasut <marex@denx.de>
To: "Bjørn Erik Nilsen" <ben@datarespons.no>
Cc: jg1.han@samsung.com, pratyush.anand@gmail.com,
bhelgaas@google.com, linux-pci@vger.kernel.org, kishon@ti.com,
Mohit.KUMAR@st.com, ajay.khandelwal@st.com,
tharvey@gateworks.com, Eric.Nelson@boundarydevices.com,
troy.kisky@boundarydevices.com
Subject: Re: [PATCH v5 1/2] PCI: designware: Fix crash in dw_msi_teardown_irq
Date: Fri, 29 Nov 2013 15:32:08 +0100 [thread overview]
Message-ID: <201311291532.08758.marex@denx.de> (raw)
In-Reply-To: <1385732125-28630-2-git-send-email-ben@datarespons.no>
Dear Bjørn Erik Nilsen,
I will be a nitpicking bastard below, sorry ;-/
> "PCI: designware: Add irq_create_mapping()" resulted
> in pre-allocated irq descs. Problem was that in assign_irq()
> these descs were explicitly allocated and hence also freed,
> resulting in a crash. We also need to clear the entire irq
> range in teardown. With this commit the teardown basically
> does exactly the opposite of what was done in setup.
>
> Signed-off-by: Bjørn Erik Nilsen <ben@datarespons.no>
You can stuff your CC list here, like this, if it's more convenient for you then
to type all these people on the command line:
Cc: Exa Mple <user@example.com>
The git send-email will automatically send email to this address.
> ---
> drivers/pci/host/pcie-designware.c | 49
> ++++++++++++++++++++++++++++---------- 1 file changed, 37 insertions(+),
> 12 deletions(-)
>
> diff --git a/drivers/pci/host/pcie-designware.c
> b/drivers/pci/host/pcie-designware.c index e33b68b..61345a1 100644
> --- a/drivers/pci/host/pcie-designware.c
> +++ b/drivers/pci/host/pcie-designware.c
> @@ -209,6 +209,25 @@ static int find_valid_pos0(struct pcie_port *pp, int
> msgvec, int pos, int *pos0) return 0;
> }
>
> +static void clear_irq_range(struct pcie_port *pp, unsigned int irq_base,
> + unsigned int nvec, unsigned int pos)
> +{
> + unsigned int i, res, bit, val;
> +
> + i = 0;
> + while (i < nvec) {
Won't simple
for (i = 0; i < nvec; i++) {
do here?
> + irq_set_msi_desc_off(irq_base, i, NULL);
This one returns a return value, please handle it.
ret = irq_set(...);
if (ret)
goto fail;
> + clear_bit(pos + i, pp->msi_irq_in_use);
> + /* Disable corresponding interrupt on MSI interrupt controller
*/
> + res = ((pos + i) / 32) * 12;
> + bit = (pos + i) % 32;
> + dw_pcie_rd_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, &val);
> + val &= ~(1 << bit);
> + dw_pcie_wr_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, val);
> + ++i;
> + }
fail:
for (--i; i >=0; i--)
irq...
return ret;
> +}
> +
> static int assign_irq(int no_irqs, struct msi_desc *desc, int *pos)
> {
> int res, bit, irq, pos0, pos1, i;
> @@ -242,11 +261,20 @@ static int assign_irq(int no_irqs, struct msi_desc
> *desc, int *pos) if (!irq)
> goto no_valid_irq;
>
> + /*
> + * irq_create_mapping (called from dw_pcie_host_init) pre-allocates
> + * descs so there is no need to allocate descs here. We can therefore
> + * assume that if irq_find_mapping above returns non-zero, then the
> + * descs are also successfully allocated.
> + */
> +
> i = 0;
> while (i < no_irqs) {
> + if (irq_set_msi_desc_off(irq, i, desc) != 0) {
> + clear_irq_range(pp, irq, i, pos0);
> + goto no_valid_irq;
> + }
> set_bit(pos0 + i, pp->msi_irq_in_use);
> - irq_alloc_descs((irq + i), (irq + i), 1, 0);
> - irq_set_msi_desc(irq + i, desc);
> /*Enable corresponding interrupt in MSI interrupt controller */
> res = ((pos0 + i) / 32) * 12;
> bit = (pos0 + i) % 32;
> @@ -266,7 +294,7 @@ no_valid_irq:
>
> static void clear_irq(unsigned int irq)
> {
> - int res, bit, val, pos;
> + unsigned int pos, nvec;
> struct irq_desc *desc;
> struct msi_desc *msi;
> struct pcie_port *pp;
> @@ -281,18 +309,15 @@ static void clear_irq(unsigned int irq)
> return;
> }
>
> + /* undo what was done in assign_irq */
> pos = data->hwirq;
> + nvec = 1 << msi->msi_attrib.multiple;
>
> - irq_free_desc(irq);
> -
> - clear_bit(pos, pp->msi_irq_in_use);
> + clear_irq_range(pp, irq, nvec, pos);
>
> - /* Disable corresponding interrupt on MSI interrupt controller */
> - res = (pos / 32) * 12;
> - bit = pos % 32;
> - dw_pcie_rd_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, &val);
> - val &= ~(1 << bit);
> - dw_pcie_wr_own_conf(pp, PCIE_MSI_INTR0_ENABLE + res, 4, val);
> + /* all irqs cleared; reset attributes */
> + msi->irq = 0;
> + msi->msi_attrib.multiple = 0;
> }
>
> static int dw_msi_setup_irq(struct msi_chip *chip, struct pci_dev *pdev,
next prev parent reply other threads:[~2013-11-29 14:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <528a1bb6.6a88700a.28c9.ffff824aSMTPIN_ADDED_MISSING@mx.google.com>
[not found] ` <CAErSpo4TbUuq0wb06JV9Xchmcjsk9q3cm7+XO-dOSiJAAhXPMA@mail.gmail.com>
2013-11-18 21:02 ` Kernel oops from pci_disable_msi Bjorn Helgaas
2013-11-18 23:11 ` Jingoo Han
2013-11-19 11:24 ` Marek Vasut
[not found] ` <1384861142.3682.1.camel@bnilsen-HP-EliteBook-8760w>
[not found] ` <cmu-lmtpd-19155-1384861370-13@frontend1.mail.m-online.net>
2013-11-19 22:01 ` Marek Vasut
[not found] ` <cmu-lmtpd-1612-1384936883-21@frontend1.mail.m-online.net>
2013-11-20 10:30 ` Marek Vasut
[not found] ` <cmu-lmtpd-21237-1384948548-21@frontend1.mail.m-online.net>
2013-11-20 12:02 ` Marek Vasut
[not found] ` <cmu-lmtpd-23243-1384949805-3@frontend1.mail.m-online.net>
2013-11-20 13:57 ` Marek Vasut
[not found] ` <1385036087.3945.28.camel@bnilsen-HP>
[not found] ` <1385039987.6020.5.camel@bnilsen-HP>
[not found] ` <16.79.22145.6305E825@epmailin9.samsung.com>
2013-11-22 8:48 ` Jingoo Han
[not found] ` <1385118399.3944.32.camel@bnilsen-HP>
[not found] ` <7D.78.31634.B838F825@epmailin2.samsung.com>
2013-11-26 11:21 ` [PATCH] " Jingoo Han
[not found] ` <cmu-lmtpd-32538-1385137032-0@frontend1.mail.m-online.net>
2013-11-26 21:19 ` Marek Vasut
[not found] ` <cmu-lmtpd-17794-1385506605-2@frontend1.mail.m-online.net>
2013-11-26 23:05 ` Marek Vasut
2013-11-27 9:46 ` Marek Vasut
[not found] ` <cmu-lmtpd-20073-1385566822-1@frontend1.mail.m-online.net>
2013-11-27 19:05 ` [PATCH v4] " Marek Vasut
[not found] ` <C7.DF.00504.D1216925@epmailin4.samsung.com>
2013-11-29 7:37 ` Jingoo Han
2013-11-29 13:35 ` [PATCH v5 0/2] " Bjørn Erik Nilsen
2013-11-29 13:35 ` [PATCH v5 1/2] PCI: designware: Fix crash in dw_msi_teardown_irq Bjørn Erik Nilsen
2013-11-29 14:32 ` Marek Vasut [this message]
[not found] ` <cmu-lmtpd-25244-1385737839-23@frontend1.mail.m-online.net>
2013-11-29 15:36 ` Marek Vasut
[not found] ` <cmu-lmtpd-32360-1385742114-0@frontend1.mail.m-online.net>
2013-11-29 17:02 ` Marek Vasut
[not found] ` <cmu-lmtpd-8418-1385750273-5@frontend1.mail.m-online.net>
2013-12-02 8:10 ` Marek Vasut
2013-11-29 13:35 ` [PATCH v5 2/2] PCI: designware: Remove redundant call to pci_write_config Bjørn Erik Nilsen
2013-12-05 1:52 ` [PATCH v5 0/2] Kernel oops from pci_disable_msi Jingoo Han
2013-12-05 2:18 ` Marek Vasut
2013-12-05 2:24 ` Jingoo Han
2013-12-05 4:07 ` Mohit KUMAR DCG
2013-12-09 20:43 ` Bjorn Helgaas
[not found] ` <52a632f0.e42c980a.3d86.ffff8faeSMTPIN_ADDED_MISSING@mx.google.com>
2013-12-09 21:21 ` Bjorn Helgaas
[not found] ` <52a63678.4902980a.6fd7.ffffa2b9SMTPIN_ADDED_MISSING@mx.google.com>
2013-12-09 22:27 ` Bjorn Helgaas
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=201311291532.08758.marex@denx.de \
--to=marex@denx.de \
--cc=Eric.Nelson@boundarydevices.com \
--cc=Mohit.KUMAR@st.com \
--cc=ajay.khandelwal@st.com \
--cc=ben@datarespons.no \
--cc=bhelgaas@google.com \
--cc=jg1.han@samsung.com \
--cc=kishon@ti.com \
--cc=linux-pci@vger.kernel.org \
--cc=pratyush.anand@gmail.com \
--cc=tharvey@gateworks.com \
--cc=troy.kisky@boundarydevices.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).