linux-kernel - Re: [PATCH v4] driver core: Fix use-after-free and double free on glue directory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 19 Jun 2019 00:09:40 +0800
From:   Muchun Song <smuchun@...il.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     "Rafael J. Wysocki" <rafael@...nel.org>,
        Benjamin Herrenschmidt <benh@...nel.crashing.org>,
        Prateek Sood <prsood@...eaurora.org>,
        Mukesh Ojha <mojha@...eaurora.org>, gkohli@...eaurora.org,
        linux-kernel <linux-kernel@...r.kernel.org>,
        linux-arm-msm <linux-arm-msm@...r.kernel.org>,
        zhaowuyun@...gtech.com
Subject: Re: [PATCH v4] driver core: Fix use-after-free and double free on
 glue directory

Greg KH <gregkh@...uxfoundation.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

Thanks.

Yours,
Muchun