diff options
author | Vladimir Davydov <vdavydov@parallels.com> | 2015-04-16 12:47:35 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2015-04-17 09:04:06 -0400 |
commit | 69828dce7af2cb6d08ef5a03de687d422fb7ec1f (patch) | |
tree | 6acd4726c17d847bdf3490bcd414d55ff6b219a2 /kernel/fork.c | |
parent | 64a4096c5cdab377b6e1f44008ee8b2636db579d (diff) | |
download | linux-69828dce7af2cb6d08ef5a03de687d422fb7ec1f.tar.gz linux-69828dce7af2cb6d08ef5a03de687d422fb7ec1f.tar.bz2 linux-69828dce7af2cb6d08ef5a03de687d422fb7ec1f.zip |
signal: remove warning about using SI_TKILL in rt_[tg]sigqueueinfo
Sending SI_TKILL from rt_[tg]sigqueueinfo was deprecated, so now we issue
a warning on the first attempt of doing it. We use WARN_ON_ONCE, which is
not informative and, what is worse, taints the kernel, making the trinity
syscall fuzzer complain false-positively from time to time.
It does not look like we need this warning at all, because the behaviour
changed quite a long time ago (2.6.39), and if an application relies on
the old API, it gets EPERM anyway and can issue a warning by itself.
So let us zap the warning in kernel.
Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>
Acked-by: Oleg Nesterov <oleg@redhat.com>
Cc: Richard Weinberger <richard@nod.at>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/fork.c')
0 files changed, 0 insertions, 0 deletions