From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Rolf Evers-Fischer <embedded24@evers-fischer.de>
Cc: kishon@ti.com, bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, andy.shevchenko@gmail.com
Subject: Re: [PATCH v5 0/3] pci: endpoint: Fix double free in pci_epf_create()
Date: Thu, 1 Mar 2018 12:22:55 +0000 [thread overview]
Message-ID: <20180301122247.GA31651@e107981-ln.cambridge.arm.com> (raw)
In-Reply-To: <20180228173220.544-1-embedded24@evers-fischer.de>
On Wed, Feb 28, 2018 at 06:32:17PM +0100, Rolf Evers-Fischer wrote:
> This is version 5 of a patchset to avoid double free in function
> 'pci_epf_create()'.
>
> When I accidentally created a new endpoint device with an empty name,
> the kernel warned about "attempted to be registered with empty name!"
> and crashed afterwards.
>
> It turned out that the crash was not caused by the 'device_add()'
> function itself, but by a double kfree of 'epf->name' and 'epf'.
>
> The first patch just simplifies the code, while the second patch
> fixes the problem. The third patch removes the goto labels.
>
> Thank you Andy and Kishon for your Ack/Review on v3 for patches 1 and 2.
> In v4 of these patches only the first lines of the commit messages
> have been changed. In v5 these two patches have not been changed.
> Therefore the 'Acked-By'/'Reviewed-By' lines have been added. I hope
> that's acceptable.
>
> Changes in v5:
> - Beautified the ugly part of Patch #3 (v4), where the correct return
> value was hidden under two levels of 'if'.
>
> Changes in v4:
> - s/pci/PCI and s/epf/EPF in the first line of
> recent commit messages (thanks, Bjorn!)
> - The new patch #3 removes the goto labels
> in function 'pci_epf_create()' (thanks, Lorenzo!)
>
> Changes in v3:
> - Matched to other pending pci endpoint commits (thanks, Bjorn!)
> - Added "Fixes" tag in patch 2 (thanks, Andy!)
>
> Changes in v2:
> - Based on feedback from Lorenzo, Andy and Kishon (thanks!)
> - Change IDs removed
> - First patch completely reworked in order to eliminate the
> need for the second 'kstrdup' allocation and the 'kfree' of
> the first allocation.
> It was tested with name="pci_epf_test.0" and name="pci_epb":
> The 'epf->name' was "pci_epf_test" or "pci_epb" (=unchanged).
>
> Rolf Evers-Fischer (3):
> PCI: endpoint: Simplify name allocation for EPF device
> PCI: endpoint: Fix kernel panic after put_device()
> PCI: endpoint: pci_epf_create: remove goto labels
>
> drivers/pci/endpoint/pci-epf-core.c | 52 +++++++++++--------------------------
> 1 file changed, 15 insertions(+), 37 deletions(-)
Applied to pci/endpoint for v4.17, thanks.
Lorenzo
prev parent reply other threads:[~2018-03-01 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 17:32 Rolf Evers-Fischer
2018-02-28 17:32 ` [PATCH v5 1/3] PCI: endpoint: Simplify name allocation for EPF device Rolf Evers-Fischer
2018-02-28 17:32 ` [PATCH v5 2/3] PCI: endpoint: Fix kernel panic after put_device() Rolf Evers-Fischer
2018-02-28 17:32 ` [PATCH v5 3/3] PCI: endpoint: pci_epf_create: remove goto labels Rolf Evers-Fischer
2018-03-01 12:22 ` Lorenzo Pieralisi [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=20180301122247.GA31651@e107981-ln.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=andy.shevchenko@gmail.com \
--cc=bhelgaas@google.com \
--cc=embedded24@evers-fischer.de \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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®