diff options
author | Tejun Heo <[email protected]> | 2022-08-27 19:04:37 -1000 |
---|---|---|
committer | Greg Kroah-Hartman <[email protected]> | 2022-09-01 18:08:44 +0200 |
commit | c25491747b21536bd56dccb82a109754bbc8d52c (patch) | |
tree | 92875a8fd0337371d81d3101dbded0a7d1b8eec5 /lib/test_fortify/write_overflow-strncpy-src.c | |
parent | 2d7f9f8c1815707e9ddb454648a523efc67a04d3 (diff) |
kernfs: Add KERNFS_REMOVING flags
KERNFS_ACTIVATED tracks whether a given node has ever been activated. As a
node was only deactivated on removal, this was used for
1. Drain optimization (removed by the previous patch).
2. To hide !activated nodes
3. To avoid double activations
4. Reject adding children to a node being removed
5. Skip activaing a node which is being removed.
We want to decouple deactivation from removal so that nodes can be
deactivated and hidden dynamically, which makes KERNFS_ACTIVATED useless for
all of the above purposes.
#1 is already gone. #2 and #3 can instead test whether the node is currently
active. A new flag KERNFS_REMOVING is added to explicitly mark nodes which
are being removed for #4 and #5.
While this leaves KERNFS_ACTIVATED with no users, leave it be as it will be
used in a following patch.
Cc: Chengming Zhou <[email protected]>
Tested-by: Chengming Zhou <[email protected]>
Reviewed-by: Chengming Zhou <[email protected]>
Signed-off-by: Tejun Heo <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions