linux-kernel - Re: [PATCH V2] bcache: fix potential deadlock problem in btree_gc

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-next>] [day] [month] [year] [list]

Message-ID: <80c2a2c6-01b9-8280-34b4-ff6b9cfaf76a@web.de>
Date:   Sun, 26 Apr 2020 20:16:36 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Zhiqiang Liu <liuzhiqiang26@...wei.com>,
        linux-bcache@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org,
        Coly Li <colyli@...e.de>, Feilong Lin <linfeilong@...wei.com>,
        Kent Overstreet <kmo@...erainc.com>, mingfangsen@...wei.com,
        renxudong1@...wei.com, Wu Bo <wubo40@...wei.com>,
        yanxiaodan@...wei.com
Subject: Re: [PATCH V2] bcache: fix potential deadlock problem in
 btree_gc_coalesce

> --
> V1->V2: rewrite commit log (suggested by Coly Li) and rename the patch

* The patch version description should be placed behind triple dashes.

* I would find a shorter version identification (without the arrow)
  also sufficient.

> Fixes: 2a285686c1 ("bcache: btree locking rework")>

Will a longer commit identifier be safer for the final change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=b2768df24ec400dd4f7fa79542f797e904812053#n183

Regards,
Markus