| 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
| ||
|
Message-ID: <49cdff8f-65b4-4784-9789-34af07ee40c7@roeck-us.net> Date: Mon, 4 Mar 2024 10:55:40 -0800 From: Guenter Roeck <linux@...ck-us.net> To: Kemeng Shi <shikemeng@...weicloud.com> Cc: tytso@....edu, adilger.kernel@...ger.ca, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, naresh.kamboju@...aro.org, daniel.diaz@...aro.org, brauner@...nel.org Subject: Re: [PATCH v4 2/3] ext4: hold group lock in ext4 kunit test On Tue, Mar 05, 2024 at 12:35:42AM +0800, Kemeng Shi wrote: > Although there is no concurrent block allocation/free in unit test, > internal functions mb_mark_used and mb_free_blocks assert group > lock is always held. Acquire group before calling mb_mark_used and > mb_free_blocks in unit test to avoid the assertion. > > Signed-off-by: Kemeng Shi <shikemeng@...weicloud.com> > Reported-by: Guenter Roeck <linux@...ck-us.net> Tested-by: Guenter Roeck <linux@...ck-us.net>
Powered by blists - more mailing lists