linux-kernel - Re: [PATCH 1/1] block: fix race between opening blkext device and freeing it

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CACVXFVO51Un=nGZCfyUN_SKG11O7+LR4paSkS8QMFsqBL9UewQ@mail.gmail.com>
Date:   Thu, 10 May 2018 08:51:54 +0800
From:   Ming Lei <tom.leiming@...il.com>
To:     Roman Penyaev <roman.penyaev@...fitbricks.com>
Cc:     Keith Busch <keith.busch@...el.com>, stable <stable@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-block <linux-block@...r.kernel.org>,
        Jens Axboe <axboe@...nel.dk>
Subject: Re: [PATCH 1/1] block: fix race between opening blkext device and
 freeing it

On Tue, Feb 2, 2016 at 12:29 AM, Roman Penyaev
<roman.penyaev@...fitbricks.com> wrote:
> Hello, Jens.
>
> Could you please take a look at this patch.
> This issue happens quite often on our servers, when udevd
> tries to get detailed info about md raid starting mdadm,
> but this raid device is already in closing state and is
> about to free internal structures, afterwards an oops
> happens and mdadm gets killed.

Looks the issue is still there, so could we consider Roman's approach
for this issue?

Thanks,
Ming Lei