diff options
author | Karthik Ramanan <a0393906@ti.com> | 2017-01-05 18:01:23 +0530 |
---|---|---|
committer | Jan-Simon Moeller <jsmoeller@linuxfoundation.org> | 2017-01-05 23:38:04 +0000 |
commit | 5dbfea7fd40a029a5067dd9800c3205addd6b798 (patch) | |
tree | f01f3977d9cc1bf94b6b4c30f0670b823dfb7155 /meta-agl-bsp/meta-ti/recipes-kernel/linux/files/0003-Smack-ignore-null-signal-in-smack_task_kill.patch | |
parent | fc9db179d4cad2a70aaa8e077bb93d2f26205b85 (diff) |
dra7xx-evm: Fix issue with bluetooth pairing
This patch is ported from meta-agl-extra
Commit details below:
commit c50805d25ba95473e8b4d1eb28d1203a328cd77a
Author: José Bollo <jose.bollo@iot.bzh>
Change-Id: I54a40935d6d2bbd9c267985c9e23a14bdffb7a3c
Signed-off-by: Karthik Ramanan <a0393906@ti.com>
(cherry picked from commit 554f8d394c626d3a151127e67caddc3196e3ffc1)
Diffstat (limited to 'meta-agl-bsp/meta-ti/recipes-kernel/linux/files/0003-Smack-ignore-null-signal-in-smack_task_kill.patch')
-rw-r--r-- | meta-agl-bsp/meta-ti/recipes-kernel/linux/files/0003-Smack-ignore-null-signal-in-smack_task_kill.patch | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/meta-agl-bsp/meta-ti/recipes-kernel/linux/files/0003-Smack-ignore-null-signal-in-smack_task_kill.patch b/meta-agl-bsp/meta-ti/recipes-kernel/linux/files/0003-Smack-ignore-null-signal-in-smack_task_kill.patch new file mode 100644 index 000000000..c9180bb9f --- /dev/null +++ b/meta-agl-bsp/meta-ti/recipes-kernel/linux/files/0003-Smack-ignore-null-signal-in-smack_task_kill.patch @@ -0,0 +1,39 @@ +From ec4eb03af07b0fbc330aecca6ac4ebd6accd8825 Mon Sep 17 00:00:00 2001 +From: Rafal Krypa <r.krypa@samsung.com> +Date: Mon, 4 Apr 2016 11:14:53 +0200 +Subject: [PATCH 3/4] Smack: ignore null signal in smack_task_kill + +Kill with signal number 0 is commonly used for checking PID existence. +Smack treated such cases like any other kills, although no signal is +actually delivered when sig == 0. + +Checking permissions when sig == 0 didn't prevent an unprivileged caller +from learning whether PID exists or not. When it existed, kernel returned +EPERM, when it didn't - ESRCH. The only effect of policy check in such +case is noise in audit logs. + +This change lets Smack silently ignore kill() invocations with sig == 0. + +Signed-off-by: Rafal Krypa <r.krypa@samsung.com> +Acked-by: Casey Schaufler <casey@schaufler-ca.com> +--- + security/smack/smack_lsm.c | 3 +++ + 1 file changed, 3 insertions(+) + +diff --git a/security/smack/smack_lsm.c b/security/smack/smack_lsm.c +index b2bcb14..cf8a93f 100644 +--- a/security/smack/smack_lsm.c ++++ b/security/smack/smack_lsm.c +@@ -2239,6 +2239,9 @@ static int smack_task_kill(struct task_struct *p, struct siginfo *info, + struct smack_known *tkp = smk_of_task_struct(p); + int rc; + ++ if (!sig) ++ return 0; /* null signal; existence test */ ++ + smk_ad_init(&ad, __func__, LSM_AUDIT_DATA_TASK); + smk_ad_setfield_u_tsk(&ad, p); + /* +-- +2.7.4 + |