diff options
author | Mateusz Guzik <[email protected]> | 2020-10-29 17:54:20 +0100 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2020-10-30 16:04:05 -0700 |
commit | 7e76d21bc81b2a8d4ed34d72ce5cff723155d344 (patch) | |
tree | 94f10709acfb7d87fbb855a60728662951444cae /tests | |
parent | e579a4ed0f4387336e3b992a4504eddea99036d3 (diff) |
Linux: g/c leftover fence in zfs_znode_alloc
The port removed provisions for zfs_znode_move but the cleanup missed
this bit. To quote the original:
[snip]
list_insert_tail(&zfsvfs->z_all_znodes, zp);
membar_producer();
/*
* Everything else must be valid before assigning z_zfsvfs makes the
* znode eligible for zfs_znode_move().
*/
zp->z_zfsvfs = zfsvfs;
[/snip]
In the current code it is immediately followed by unlock which issues
the same fence, thus plays no role in correctness.
Reviewed-by: Matt Macy <[email protected]>
Reviewed-by: Brian Behlendorf <[email protected]>
Signed-off-by: Mateusz Guzik <[email protected]>
Closes #11115
Diffstat (limited to 'tests')
0 files changed, 0 insertions, 0 deletions