diff options
| author | Eric Dumazet <edumazet@google.com> | 2012-08-21 15:05:14 +0200 |
|---|---|---|
| committer | Al Viro <viro@zeniv.linux.org.uk> | 2012-08-22 10:31:05 -0400 |
| commit | 88ec2789d856056344161aa20420dd37e893b0fe (patch) | |
| tree | 0e944baca39ae432b11ca105fa5c8d0cdd6a47a5 /fs | |
| parent | 55852635a8e2803cbc22d0e143d727813f0fcdb5 (diff) | |
| download | linux-3.10-88ec2789d856056344161aa20420dd37e893b0fe.tar.gz linux-3.10-88ec2789d856056344161aa20420dd37e893b0fe.tar.bz2 linux-3.10-88ec2789d856056344161aa20420dd37e893b0fe.zip | |
task_work: add a scheduling point in task_work_run()
It seems commit 4a9d4b02 (switch fput to task_work_add) reintroduced
the problem addressed in commit 944be0b2 (close_files(): add scheduling
point)
If a server process with a lot of files (say 2 million tcp sockets)
is killed, we can spend a lot of time in task_work_run() and trigger
a soft lockup.
Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions