summaryrefslogtreecommitdiff
path: root/tools/testing/shared/linux/kernel.h
diff options
context:
space:
mode:
authorBoris Burkov <boris@bur.io>2026-05-12 09:55:28 -0700
committerDavid Sterba <dsterba@suse.com>2026-05-16 03:08:40 +0200
commitf13342e15deafb7538a7a8577ed5f4c33c56f64e (patch)
tree742727512c855e3e16e2e6bb9db12cd4797f01d2 /tools/testing/shared/linux/kernel.h
parent99aacd195141ff77295c535388888f072ec89e82 (diff)
btrfs: swallow btrfs_record_squota_delta() ENOENT
I thought that it was likely I could harden squota deletion to the point that it was impossible to end up with an extent accounted to a qgroup outliving its qgroup. Several recent bugs have made me re-consider that position. Ultimately, this is a tradeoff between short term stability and long term strictness, but I think given that there could be another layer of bugs behind the 2-3 I just fixed, I would feel much more confident in people using squotas if the risk was "your values can get a bit out of whack which you can fix by deleting stuff or disabling/re-enabling/repairing" vs "it will abort your filesystem". As the final nail in the coffin, the Meta production kernel was lacking earlier fixes from me and Qu regarding subvol qgroup lifetime, so this is what we have been testing at scale, so I think at least for now upstream should have the same extra layer of protection. Reviewed-by: Qu Wenruo <wqu@suse.com> Signed-off-by: Boris Burkov <boris@bur.io> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'tools/testing/shared/linux/kernel.h')
0 files changed, 0 insertions, 0 deletions