On 1/15/20 8:22 AM, fdmanana@xxxxxxxxxx wrote:
From: Filipe Manana <fdmanana@xxxxxxxx> Add a similar test to the existing one but with a file that has a hardlink as well. This is motivated by a bug found in btrfs where a fsync on a file that has the old name of another file results in the logging code to hit an infinite loop. The patch that fixes the bug in btrfs has the following subject: "Btrfs: fix infinite loop during fsync after rename operations" Signed-off-by: Filipe Manana <fdmanana@xxxxxxxx>
What's our policy on adding a new variant to an existing test? I thought we preferred to create a new test for these sort of things? If not then you can add
Reviewed-by: Josef Bacik <josef@xxxxxxxxxxxxxx> I have no strong opinions either way, I just know it's come up in the past. Thanks, Josef
