,
> @@ -729,6 +730,7 @@ static int audit_receive_msg(struct sk_buff *skb, struct
> nlmsghdr *nlh)
> }
> audit_set_pid(ab, NETLINK_CB(skb).portid);
> audit_log_end(ab);
> + mutex_lock(_cmd_mutex);
> }
> brea
)
}
audit_set_pid(ab, NETLINK_CB(skb).portid);
audit_log_end(ab);
+ mutex_lock(audit_cmd_mutex);
}
break;
case AUDIT_ADD_RULE:
--
1.7.1
--
Toshiyuki Okajima toshi.okaj...@jp.fujitsu.com
not stop.
You can see the deadlock with the following reproducer:
# auditctl -a exit,always -S all
# reboot
Signed-off-by: Toshiyuki Okajima
Reviewed-by: gaof...@cn.fujitsu.com
---
kernel/audit.c | 14 --
1 files changed, 8 insertions(+), 6 deletions(-)
diff --git a/kernel/audit.c b
not stop.
You can see the deadlock with the following reproducer:
# auditctl -a exit,always -S all
# reboot
Signed-off-by: Toshiyuki Okajima toshi.okaj...@jp.fujitsu.com
Reviewed-by: gaof...@cn.fujitsu.com
---
kernel/audit.c | 14 --
1 files changed, 8 insertions(+), 6 deletions(-)
diff
Hi.
(2013/10/26 0:12), Eric Paris wrote:
> On Fri, 2013-10-25 at 10:36 +0900, Toshiyuki Okajima wrote:
>
>> systemd
Hi.
(2013/10/26 0:12), Eric Paris wrote:
On Fri, 2013-10-25 at 10:36 +0900, Toshiyuki Okajima wrote:
systemd|auditd
Hi.
Thanks for your interest.
(2013/10/24 4:55), Richard Guy Briggs wrote:
> On Tue, Oct 15, 2013 at 02:30:34PM +0800, Gao feng wrote:
>> Hi Toshiyuki-san,
>
> Toshiuki and Gao,
>
>> On 10/15/2013 12:43 PM, Toshiyuki Okajima wrote:
>>> The backlog cannot
Hi.
Thanks for your interest.
(2013/10/24 4:55), Richard Guy Briggs wrote:
On Tue, Oct 15, 2013 at 02:30:34PM +0800, Gao feng wrote:
Hi Toshiyuki-san,
Toshiuki and Gao,
On 10/15/2013 12:43 PM, Toshiyuki Okajima wrote:
The backlog cannot be consumed when audit_log_start is running
.
So, audit_log_start running on auditd should not stop.
You can see the deadlock with the following reproducer:
# auditctl -a exit,always -S all
# reboot
Signed-off-by: Toshiyuki Okajima
Cc: gaof...@cn.fujitsu.com
---
kernel/audit.c | 14 --
1 files changed, 8 insertions(+), 6
Hi Gao-san,
(2013/10/15 15:30), Gao feng wrote:
> Hi Toshiyuki-san,
> On 10/15/2013 12:43 PM, Toshiyuki Okajima wrote:
>> The backlog cannot be consumed when audit_log_start is running on auditd
>> even if audit_log_start calls wait_for_auditd to consume it.
>> The situati
Hi Gao-san,
(2013/10/15 15:30), Gao feng wrote:
Hi Toshiyuki-san,
On 10/15/2013 12:43 PM, Toshiyuki Okajima wrote:
The backlog cannot be consumed when audit_log_start is running on auditd
even if audit_log_start calls wait_for_auditd to consume it.
The situation is a deadlock because only
.
So, audit_log_start running on auditd should not stop.
You can see the deadlock with the following reproducer:
# auditctl -a exit,always -S all
# reboot
Signed-off-by: Toshiyuki Okajima toshi.okaj...@jp.fujitsu.com
Cc: gaof...@cn.fujitsu.com
---
kernel/audit.c | 14 --
1 files
.
So, audit_log_start running on auditd should not stop.
You can see the deadlock with the following reproducer:
# auditctl -a exit,always -S all
# reboot
Signed-off-by: Toshiyuki Okajima
Cc: gaof...@cn.fujitsu.com
---
kernel/audit.c |3 +++
1 files changed, 3 insertions(+), 0 deletions
.
So, audit_log_start running on auditd should not stop.
You can see the deadlock with the following reproducer:
# auditctl -a exit,always -S all
# reboot
Signed-off-by: Toshiyuki Okajima toshi.okaj...@jp.fujitsu.com
Cc: gaof...@cn.fujitsu.com
---
kernel/audit.c |3 +++
1 files changed, 3
Gao-san,
(2013/10/11 18:33), Gao feng wrote:
> On 10/11/2013 09:36 AM, Toshiyuki Okajima wrote:
>> Hi.
>>
>> The following reproducer causes auditd daemon hang up.
>> (But the hang up is released after the audit_backlog_wait_time passes.)
>> # auditctl -
Gao-san,
(2013/10/11 18:33), Gao feng wrote:
On 10/11/2013 09:36 AM, Toshiyuki Okajima wrote:
Hi.
The following reproducer causes auditd daemon hang up.
(But the hang up is released after the audit_backlog_wait_time passes.)
# auditctl -a exit,always -S all
# reboot
I reproduced
n can execute the audit_log_start, and then it can cause
a hang up because only auditd daemon can consume the backlog.
So, audit_log_start executed by auditd daemon should not handle the backlog
in case auditd daemon hangs up (while wait_for_auditd is calling).
Signed-off-by: Toshiyuki Okajima
the audit_log_start, and then it can cause
a hang up because only auditd daemon can consume the backlog.
So, audit_log_start executed by auditd daemon should not handle the backlog
in case auditd daemon hangs up (while wait_for_auditd is calling).
Signed-off-by: Toshiyuki Okajima toshi.okaj
Hi guys!
I encountered that a file cannot be opened even if the process has a valid
access authority for the file on linux-3.10.
This problem is caused since the group list which getgroups() returns includes
wrong ID as the group ID after setgid(). These groups include egid of the
process
Hi guys!
I encountered that a file cannot be opened even if the process has a valid
access authority for the file on linux-3.10.
This problem is caused since the group list which getgroups() returns includes
wrong ID as the group ID after setgid(). These groups include egid of the
process
20 matches
Mail list logo
