diff options
author | Eric W. Biederman <ebiederm@xmission.com> | 2022-01-08 09:48:31 -0600 |
---|---|---|
committer | Eric W. Biederman <ebiederm@xmission.com> | 2022-01-08 12:43:57 -0600 |
commit | 2f824d4d197e02275562359a2ae5274177ce500c (patch) | |
tree | 3e54e1226b6c4f8c5ff6ab2d8b29f6f1d44c3d0b /fs/attr.c | |
parent | 752dc9707567f39ed7850e21796cf2b467d71ad5 (diff) | |
download | linux-2f824d4d197e02275562359a2ae5274177ce500c.tar.gz linux-2f824d4d197e02275562359a2ae5274177ce500c.tar.bz2 linux-2f824d4d197e02275562359a2ae5274177ce500c.zip |
signal: Remove SIGNAL_GROUP_COREDUMP
After the previous cleanups "signal->core_state" is set whenever
SIGNAL_GROUP_COREDUMP is set and "signal->core_state" is tested
whenver the code wants to know if a coredump is in progress. The
remaining tests of SIGNAL_GROUP_COREDUMP also test to see if
SIGNAL_GROUP_EXIT is set. Similarly the only place that sets
SIGNAL_GROUP_COREDUMP also sets SIGNAL_GROUP_EXIT.
Which makes SIGNAL_GROUP_COREDUMP unecessary and redundant. So stop
setting SIGNAL_GROUP_COREDUMP, stop testing SIGNAL_GROUP_COREDUMP, and
remove it's definition.
With the setting of SIGNAL_GROUP_COREDUMP gone, coredump_finish no
longer needs to clear SIGNAL_GROUP_COREDUMP out of signal->flags
by setting SIGNAL_GROUP_EXIT.
Link: https://lkml.kernel.org/r/20211213225350.27481-5-ebiederm@xmission.com
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'fs/attr.c')
0 files changed, 0 insertions, 0 deletions