On 16.12.20 г. 18:22 ч., Josef Bacik wrote: > Qu pointed out a bug in one of my error handling patches, which made me > notice that we modify the new_root->highest_objectid _after_ we've > dropped the ref to the new_root. This could lead to a possible UAF, fix > this by modifying the ->highest_objectid before we drop our reference to > the new_root. > > Signed-off-by: Josef Bacik <jo...@toxicpanda.com> This patch must be dropped as per https://github.com/kdave/btrfs-devel/commit/6044ce89a75a07a80f28f4bfeddeefc1b772366a
- Re: [PATCH 11/13] btrfs: keep track of the root o... David Sterba
- [PATCH 08/13] btrfs: abort the transaction if we fail to i... Josef Bacik
- [PATCH 06/13] btrfs: add ASSERT()'s for deleting backref c... Josef Bacik
- [PATCH 07/13] btrfs: do not double free backref nodes on e... Josef Bacik
- [PATCH 05/13] btrfs: do not WARN_ON() if we can't find the... Josef Bacik
- [PATCH 12/13] btrfs: do not cleanup upper nodes in btrfs_b... Josef Bacik
- [PATCH 09/13] btrfs: modify the new_root highest_objectid ... Josef Bacik
- Re: [PATCH 09/13] btrfs: modify the new_root highest_... Nikolay Borisov
- [PATCH 13/13] btrfs: don't clear ret in btrfs_start_dirty_... Josef Bacik
- [PATCH 10/13] btrfs: fix lockdep splat in btrfs_recover_re... Josef Bacik
- [PATCH 04/13] btrfs: splice remaining dirty_bg's onto the ... Josef Bacik
- Re: [PATCH 00/13] Serious fixes for different error paths David Sterba