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]
Date:   Sat, 09 May 2020 12:30:50 +0000
From:   Sasha Levin <>
Subject: Re: [PATCH] ext4: fix race between ext4_sync_parent() and rename()


[This is an automated email]

This commit has been processed because it contains a "Fixes:" tag
fixing commit: d59729f4e794 ("ext4: fix races in ext4_sync_parent()").

The bot has tested the following trees: v5.6.11, v5.4.39, v4.19.121, v4.14.179, v4.9.222, v4.4.222.

v5.6.11: Build OK!
v5.4.39: Build OK!
v4.19.121: Build OK!
v4.14.179: Build OK!
v4.9.222: Build OK!
v4.4.222: Failed to apply! Possible dependencies:
    6ae4c5a69877 ("ext4: cleanup ext4_sync_parent()")
    78d962510796 ("ext4: respect the nobarrier mount option in nojournal mode")

NOTE: The patch will not be queued to stable trees until it is upstream.

How should we proceed with this patch?


Powered by blists - more mailing lists