diff options
| author | Mikulas Patocka <mpatocka@redhat.com> | 2017-06-07 23:05:31 (GMT) |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-07-27 22:08:01 (GMT) |
| commit | 03c1d9d45582e8a0991747a6f7a3a235b39b3e2b (patch) | |
| tree | af9d6fe6ab6b3cb8a9ecca06ff17f7718b31e2ca /fs/sync.c | |
| parent | dbc969ca944f1a3f61af083f4126bb5408d37b4c (diff) | |
| download | linux-03c1d9d45582e8a0991747a6f7a3a235b39b3e2b.tar.xz | |
md: don't use flush_signals in userspace processes
commit f9c79bc05a2a91f4fba8bfd653579e066714b1ec upstream.
The function flush_signals clears all pending signals for the process. It
may be used by kernel threads when we need to prepare a kernel thread for
responding to signals. However using this function for an userspaces
processes is incorrect - clearing signals without the program expecting it
can cause misbehavior.
The raid1 and raid5 code uses flush_signals in its request routine because
it wants to prepare for an interruptible wait. This patch drops
flush_signals and uses sigprocmask instead to block all signals (including
SIGKILL) around the schedule() call. The signals are not lost, but the
schedule() call won't respond to them.
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Acked-by: NeilBrown <neilb@suse.com>
Signed-off-by: Shaohua Li <shli@fb.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/sync.c')
0 files changed, 0 insertions, 0 deletions