From: Rolf Evers-Fischer <embedded24@evers-fischer.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Rolf Evers-Fischer <embedded24@evers-fischer.de>,
kishon@ti.com, bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, andy.shevchenko@gmail.com
Subject: Re: [PATCH v3 0/2] pci: endpoint: Fix double free in pci_epf_create()
Date: Wed, 28 Feb 2018 11:35:32 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.20.1802281130190.29501@5HSWXM1.fritz.box> (raw)
In-Reply-To: <20180227145231.GC112033@bhelgaas-glaptop.roam.corp.google.com>
Hello Bjorn!
On Tue, 27 Feb 2018, Bjorn Helgaas wrote:
> On Tue, Feb 27, 2018 at 10:20:30AM +0000, Lorenzo Pieralisi wrote:
> > On Tue, Feb 27, 2018 at 11:02:28AM +0100, Rolf Evers-Fischer wrote:
> > > This is version 3 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.
> > >
> > > 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 (2):
> > > pci: endpoint: Simplify name allocation for epf device
> > > pci: endpoint: Fix kernel panic after put_device()
> > ^^^
> >
> > s/pci/PCI
> >
> > Bjorn pointed that out too, I can do it when merging the patches myself
> > just a hint in case you have to respin it again, no problem.
>
> I wonder if Rolf posted the wrong version accidentally, since he
> mentioned making these match, but I don't see anything different in
> this posting. Oh, never mind, I see the response about rebasing.
> I should have been more clear about what I was looking for.
>
> Also s/epf/EPF/, since "epf" isn't a real word.
>
It was my mistake. I should have asked you to clarify your request -
especially after detecting that rebasing the commits didn't change
anything.
Nevertheless, it seems that there will be soon a v4, where the s/pci/PCI
and the s/epf/EPF can be done along with.
Best regards,
Rolf
next prev parent reply other threads:[~2018-02-28 10:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 10:02 [PATCH v3 0/2] pci: endpoint: Fix double free in pci_epf_create() Rolf Evers-Fischer
2018-02-27 10:02 ` [PATCH v3 1/2] pci: endpoint: Simplify name allocation for epf device Rolf Evers-Fischer
2018-02-27 10:09 ` Kishon Vijay Abraham I
2018-02-27 10:15 ` Rolf Evers-Fischer
2018-02-27 10:43 ` Kishon Vijay Abraham I
2018-02-27 10:02 ` [PATCH v3 2/2] pci: endpoint: Fix kernel panic after put_device() Rolf Evers-Fischer
2018-02-27 10:43 ` Kishon Vijay Abraham I
2018-02-27 17:57 ` Lorenzo Pieralisi
2018-02-28 10:29 ` Rolf Evers-Fischer
2018-02-27 10:20 ` [PATCH v3 0/2] pci: endpoint: Fix double free in pci_epf_create() Lorenzo Pieralisi
2018-02-27 12:11 ` Rolf Evers-Fischer
2018-02-27 14:52 ` Bjorn Helgaas
2018-02-28 10:35 ` Rolf Evers-Fischer [this message]
2018-02-27 16:13 ` Andy Shevchenko
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=alpine.LNX.2.20.1802281130190.29501@5HSWXM1.fritz.box \
--to=embedded24@evers-fischer.de \
--cc=andy.shevchenko@gmail.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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).