fcntl: Don't set si_code to SI_SIGIO when sig == SIGPOLL
When fixing things to avoid ambiguous cases I had a thinko and included SIGPOLL/SIGIO in with all of the other signals that have signal specific si_codes. Which is completely wrong. Fix that. Reported-by: Vince Weaver <vincent.weaver@maine.edu> Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
This commit is contained in:
parent
2bd6bf03f4
commit
54640d2387
1 changed files with 1 additions and 1 deletions
|
@ -749,7 +749,7 @@ static void send_sigio_to_task(struct task_struct *p,
|
|||
* specific si_codes. In that case use SI_SIGIO instead
|
||||
* to remove the ambiguity.
|
||||
*/
|
||||
if (sig_specific_sicodes(signum))
|
||||
if ((signum != SIGPOLL) && sig_specific_sicodes(signum))
|
||||
si.si_code = SI_SIGIO;
|
||||
|
||||
/* Make sure we are called with one of the POLL_*
|
||||
|
|
Loading…
Reference in a new issue