From: Greg KH <gregkh@linuxfoundation.org>
To: Muchun Song <smuchun@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Prateek Sood <prsood@codeaurora.org>,
Mukesh Ojha <mojha@codeaurora.org>,
gkohli@codeaurora.org,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
zhaowuyun@wingtech.com
Subject: Re: [PATCH v4] driver core: Fix use-after-free and double free on glue directory
Date: Tue, 18 Jun 2019 18:13:40 +0200 [thread overview]
Message-ID: <20190618161340.GA13983@kroah.com> (raw)
In-Reply-To: <CAPSr9jFMKb1bQAbCFLqP2+fb60kcbyJ+cDspkL5FH28CNKFz3A@mail.gmail.com>
On Wed, Jun 19, 2019 at 12:09:40AM +0800, Muchun Song wrote:
> Greg KH <gregkh@linuxfoundation.org> 于2019年6月18日周二 下午11:29写道：
> >
> > On Tue, Jun 18, 2019 at 09:40:13PM +0800, Muchun Song wrote:
> > > Ping guys ? I think this is worth fixing.
> >
> > That's great (no context here), but I need people to actually agree on
> > what the correct fix should be. I had two different patches that were
> > saying they fixed the same issue, and that feels really wrong.
>
> Another patch:
> Subject: [PATCH v3] drivers: core: Remove glue dirs early only
> when refcount is 1
>
> My first v1 patch:
> Subject: [PATCH] driver core: Fix use-after-free and double free
> on glue directory
>
> The above two patches are almost the same that fix is based on the refcount.
> But why we change the solution from v1 to v4? Some discussion can
> refer to the mail:
>
> Subject: [PATCH] driver core: Fix use-after-free and double free
> on glue directory
Again, I am totally confused and do not see a patch in an email that I
can apply...
Someone needs to get people to agree here...
thanks,
greg k-h
next prev parent reply other threads:[~2019-06-18 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 14:23 [PATCH v4] driver core: Fix use-after-free and double free on glue directory Muchun Song
2019-05-24 19:04 ` Greg KH
2019-05-25 12:15 ` Muchun Song
2019-06-18 13:40 ` Muchun Song
2019-06-18 14:11 ` Benjamin Herrenschmidt
2019-06-18 15:28 ` Greg KH
2019-06-18 16:09 ` Muchun Song
2019-06-18 16:13 ` Greg KH [this message]
2019-06-18 21:51 ` Benjamin Herrenschmidt
2019-06-25 15:06 ` Muchun Song
2019-06-25 22:56 ` Benjamin Herrenschmidt
2019-06-26 0:55 ` Greg KH
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=20190618161340.GA13983@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=benh@kernel.crashing.org \
--cc=gkohli@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mojha@codeaurora.org \
--cc=prsood@codeaurora.org \
--cc=rafael@kernel.org \
--cc=smuchun@gmail.com \
--cc=zhaowuyun@wingtech.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).