linux-kernel - Re: [f2fs-dev] [PATCH] f2fs: Avoid double lock for cp

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

Date:   Thu, 23 Apr 2020 15:07:20 +0200
From:   Markus Elfring <Markus.Elfring@....de>
To:     Sayali Lokhande <sayalil@...eaurora.org>,
        linux-f2fs-devel@...ts.sourceforge.net,
        Jaegeuk Kim <jaegeuk@...nel.org>, Chao Yu <yuchao0@...wei.com>
Cc:     linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: Avoid double lock for cp_rwsem

> Call stack :
> f2fs_write_checkpoint()
> -> block_operations(sbi)
…

Will another imperative wording become helpful besides the provided information
for this change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?id=c578ddb39e565139897124e74e5a43e56538cb33#n151

How do you think about to add the tag “Fixes” because of adjustments
for the data synchronisation?

Regards,
Markus