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] [thread-next>] [day] [month] [year] [list]
Message-ID: <81a50343-34e3-4a4d-80e9-0c674876cdb8@web.de>
Date: Fri, 17 May 2024 18:55:19 +0200
From: Markus Elfring <Markus.Elfring@....de>
To: Zhiguo Niu <zhiguo.niu@...soc.com>,
 linux-f2fs-devel@...ts.sourceforge.net, kernel-janitors@...r.kernel.org,
 Chao Yu <chao@...nel.org>, Jaegeuk Kim <jaegeuk@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Hao_hao.Wang@...soc.com,
 王科 (Ke Wang) <Ke.Wang@...soc.com>,
 Zhiguo Niu <niuzhiguo84@...il.com>
Subject: Re: [PATCH] f2fs: fix to check return value of
 f2fs_allocate_new_section

…
> missed this allocated path, fix it.

* Will another imperative wording be desirable for an improved change description?

* Would you like to add the tag “Fixes”?

* How do you think about to append parentheses to the function name
  in the summary phrase?


Regards,
Markus

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ