From: Oleg Nesterov <oleg@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, tony.luck@intel.com,
fenghua.yu@intel.com, monstr@monstr.eu, ralf@linux-mips.org,
benh@kernel.crashing.org, paulus@samba.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
linux390@de.ibm.com, lethal@linux-sh.org, davem@davemloft.net,
jdike@addtoit.com, richard@nod.at, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
linux-ia64@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au,
linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH -v2] Audit: push audit success and retcode into arch
Date: Wed, 08 Jun 2011 19:19:10 +0000 [thread overview]
Message-ID: <20110608191910.GA18698@redhat.com> (raw)
In-Reply-To: <20110608183720.GA16883@redhat.com>
On 06/08, Oleg Nesterov wrote:
>
> OK. Thanks a lot Eric for your explanations.
Yes. but may I ask another one?
Shouldn't copy_process()->audit_alloc(tsk) path do
clear_tsk_thread_flag(tsk, TIF_SYSCALL_AUDIT) if it doesn't
set tsk->audit_context?
I can be easily wrong, but afaics otherwise the child can run
with TIF_SYSCALL_AUDIT bit copied from parent's thread_info by
dup_task_struct()->setup_thread_stack() and without ->audit_context,
right? For what?
Any other reason why audit_syscall_entry() checks context != NULL?
IOW. Any reason the patch below is wrong?
I am just curious, thanks.
Oleg.
--- x/kernel/auditsc.c
+++ x/kernel/auditsc.c
@@ -885,6 +885,8 @@ int audit_alloc(struct task_struct *tsk)
if (likely(!audit_ever_enabled))
return 0; /* Return if not auditing. */
+ clear_tsk_thread_flag(tsk, TIF_SYSCALL_AUDIT);
+
state = audit_filter_task(tsk, &key);
if (likely(state = AUDIT_DISABLED))
return 0;
@@ -1591,9 +1593,7 @@ void audit_syscall_entry(int arch, int m
struct audit_context *context = tsk->audit_context;
enum audit_state state;
- if (unlikely(!context))
- return;
-
+ BUG_ON(!context);
/*
* This happens only on certain architectures that make system
* calls in kernel_thread via the entry.S interface, instead of
WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-kernel@vger.kernel.org, tony.luck@intel.com,
fenghua.yu@intel.com, monstr@monstr.eu, ralf@linux-mips.org,
benh@kernel.crashing.org, paulus@samba.org,
schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
linux390@de.ibm.com, lethal@linux-sh.org, davem@davemloft.net,
jdike@addtoit.com, richard@nod.at, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, x86@kernel.org,
viro@zeniv.linux.org.uk, akpm@linux-foundation.org,
linux-ia64@vger.kernel.org, microblaze-uclinux@itee.uq.edu.au,
linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h
Date: Wed, 8 Jun 2011 21:19:10 +0200 [thread overview]
Message-ID: <20110608191910.GA18698@redhat.com> (raw)
In-Reply-To: <20110608183720.GA16883@redhat.com>
On 06/08, Oleg Nesterov wrote:
>
> OK. Thanks a lot Eric for your explanations.
Yes. but may I ask another one?
Shouldn't copy_process()->audit_alloc(tsk) path do
clear_tsk_thread_flag(tsk, TIF_SYSCALL_AUDIT) if it doesn't
set tsk->audit_context?
I can be easily wrong, but afaics otherwise the child can run
with TIF_SYSCALL_AUDIT bit copied from parent's thread_info by
dup_task_struct()->setup_thread_stack() and without ->audit_context,
right? For what?
Any other reason why audit_syscall_entry() checks context != NULL?
IOW. Any reason the patch below is wrong?
I am just curious, thanks.
Oleg.
--- x/kernel/auditsc.c
+++ x/kernel/auditsc.c
@@ -885,6 +885,8 @@ int audit_alloc(struct task_struct *tsk)
if (likely(!audit_ever_enabled))
return 0; /* Return if not auditing. */
+ clear_tsk_thread_flag(tsk, TIF_SYSCALL_AUDIT);
+
state = audit_filter_task(tsk, &key);
if (likely(state == AUDIT_DISABLED))
return 0;
@@ -1591,9 +1593,7 @@ void audit_syscall_entry(int arch, int m
struct audit_context *context = tsk->audit_context;
enum audit_state state;
- if (unlikely(!context))
- return;
-
+ BUG_ON(!context);
/*
* This happens only on certain architectures that make system
* calls in kernel_thread via the entry.S interface, instead of
WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-mips@linux-mips.org, linux-ia64@vger.kernel.org,
linux-sh@vger.kernel.org, heiko.carstens@de.ibm.com,
paulus@samba.org, hpa@zytor.com, sparclinux@vger.kernel.org,
linux-s390@vger.kernel.org, richard@nod.at, x86@kernel.org,
mingo@redhat.com, fenghua.yu@intel.com,
user-mode-linux-devel@lists.sourceforge.net,
microblaze-uclinux@itee.uq.edu.au, jdike@addtoit.com,
viro@zeniv.linux.org.uk, tglx@linutronix.de, monstr@monstr.eu,
tony.luck@intel.com, linux-kernel@vger.kernel.org,
ralf@linux-mips.org, lethal@linux-sh.org, schwidefsky@de.ibm.com,
linux390@de.ibm.com, akpm@linux-foundation.org,
linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h
Date: Wed, 8 Jun 2011 21:19:10 +0200 [thread overview]
Message-ID: <20110608191910.GA18698@redhat.com> (raw)
In-Reply-To: <20110608183720.GA16883@redhat.com>
On 06/08, Oleg Nesterov wrote:
>
> OK. Thanks a lot Eric for your explanations.
Yes. but may I ask another one?
Shouldn't copy_process()->audit_alloc(tsk) path do
clear_tsk_thread_flag(tsk, TIF_SYSCALL_AUDIT) if it doesn't
set tsk->audit_context?
I can be easily wrong, but afaics otherwise the child can run
with TIF_SYSCALL_AUDIT bit copied from parent's thread_info by
dup_task_struct()->setup_thread_stack() and without ->audit_context,
right? For what?
Any other reason why audit_syscall_entry() checks context != NULL?
IOW. Any reason the patch below is wrong?
I am just curious, thanks.
Oleg.
--- x/kernel/auditsc.c
+++ x/kernel/auditsc.c
@@ -885,6 +885,8 @@ int audit_alloc(struct task_struct *tsk)
if (likely(!audit_ever_enabled))
return 0; /* Return if not auditing. */
+ clear_tsk_thread_flag(tsk, TIF_SYSCALL_AUDIT);
+
state = audit_filter_task(tsk, &key);
if (likely(state == AUDIT_DISABLED))
return 0;
@@ -1591,9 +1593,7 @@ void audit_syscall_entry(int arch, int m
struct audit_context *context = tsk->audit_context;
enum audit_state state;
- if (unlikely(!context))
- return;
-
+ BUG_ON(!context);
/*
* This happens only on certain architectures that make system
* calls in kernel_thread via the entry.S interface, instead of
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
WARNING: multiple messages have this Message-ID (diff)
From: Oleg Nesterov <oleg@redhat.com>
To: Eric Paris <eparis@redhat.com>
Cc: linux-mips@linux-mips.org, linux-ia64@vger.kernel.org,
linux-sh@vger.kernel.org, heiko.carstens@de.ibm.com,
paulus@samba.org, hpa@zytor.com, sparclinux@vger.kernel.org,
linux-s390@vger.kernel.org, richard@nod.at, x86@kernel.org,
mingo@redhat.com, fenghua.yu@intel.com,
user-mode-linux-devel@lists.sourceforge.net,
microblaze-uclinux@itee.uq.edu.au, jdike@addtoit.com,
viro@zeniv.linux.org.uk, tglx@linutronix.de, monstr@monstr.eu,
tony.luck@intel.com, linux-kernel@vger.kernel.org,
ralf@linux-mips.org, lethal@linux-sh.org, schwidefsky@de.ibm.com,
linux390@de.ibm.com, akpm@linux-foundation.org,
linuxppc-dev@lists.ozlabs.org, davem@davemloft.net
Subject: Re: [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h
Date: Wed, 8 Jun 2011 21:19:10 +0200 [thread overview]
Message-ID: <20110608191910.GA18698@redhat.com> (raw)
In-Reply-To: <20110608183720.GA16883@redhat.com>
On 06/08, Oleg Nesterov wrote:
>
> OK. Thanks a lot Eric for your explanations.
Yes. but may I ask another one?
Shouldn't copy_process()->audit_alloc(tsk) path do
clear_tsk_thread_flag(tsk, TIF_SYSCALL_AUDIT) if it doesn't
set tsk->audit_context?
I can be easily wrong, but afaics otherwise the child can run
with TIF_SYSCALL_AUDIT bit copied from parent's thread_info by
dup_task_struct()->setup_thread_stack() and without ->audit_context,
right? For what?
Any other reason why audit_syscall_entry() checks context != NULL?
IOW. Any reason the patch below is wrong?
I am just curious, thanks.
Oleg.
--- x/kernel/auditsc.c
+++ x/kernel/auditsc.c
@@ -885,6 +885,8 @@ int audit_alloc(struct task_struct *tsk)
if (likely(!audit_ever_enabled))
return 0; /* Return if not auditing. */
+ clear_tsk_thread_flag(tsk, TIF_SYSCALL_AUDIT);
+
state = audit_filter_task(tsk, &key);
if (likely(state == AUDIT_DISABLED))
return 0;
@@ -1591,9 +1593,7 @@ void audit_syscall_entry(int arch, int m
struct audit_context *context = tsk->audit_context;
enum audit_state state;
- if (unlikely(!context))
- return;
-
+ BUG_ON(!context);
/*
* This happens only on certain architectures that make system
* calls in kernel_thread via the entry.S interface, instead of
next prev parent reply other threads:[~2011-06-08 19:19 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 22:04 [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h Eric Paris
2011-06-03 22:04 ` Eric Paris
2011-06-03 22:04 ` Eric Paris
2011-06-03 22:04 ` Eric Paris
2011-06-03 22:52 ` Tony Luck
2011-06-03 22:52 ` Tony Luck
2011-06-03 22:52 ` Tony Luck
2011-06-03 22:52 ` Tony Luck
2011-06-04 22:36 ` Richard Weinberger
2011-06-04 22:36 ` Richard Weinberger
2011-06-04 22:36 ` Richard Weinberger
2011-06-06 20:17 ` [PATCH -v2] Audit: push audit success and retcode into arch David Miller
2011-06-06 20:17 ` [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h David Miller
2011-06-06 20:17 ` David Miller
2011-06-07 17:19 ` [PATCH -v2] Audit: push audit success and retcode into arch Oleg Nesterov
2011-06-07 17:19 ` [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h Oleg Nesterov
2011-06-07 17:19 ` Oleg Nesterov
2011-06-07 18:53 ` [PATCH -v2] Audit: push audit success and retcode into arch Eric Paris
2011-06-07 18:53 ` [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h Eric Paris
2011-06-07 18:53 ` Eric Paris
2011-06-07 18:53 ` Eric Paris
2011-06-08 16:36 ` [PATCH -v2] Audit: push audit success and retcode into arch Oleg Nesterov
2011-06-08 16:36 ` [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h Oleg Nesterov
2011-06-08 16:36 ` Oleg Nesterov
2011-06-08 16:36 ` Oleg Nesterov
2011-06-08 18:13 ` [PATCH -v2] Audit: push audit success and retcode into arch Eric Paris
2011-06-08 18:13 ` [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h Eric Paris
2011-06-08 18:13 ` Eric Paris
2011-06-08 18:13 ` Eric Paris
2011-06-08 18:37 ` [PATCH -v2] Audit: push audit success and retcode into arch Oleg Nesterov
2011-06-08 18:37 ` [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h Oleg Nesterov
2011-06-08 18:37 ` Oleg Nesterov
2011-06-08 19:19 ` Oleg Nesterov [this message]
2011-06-08 19:19 ` Oleg Nesterov
2011-06-08 19:19 ` Oleg Nesterov
2011-06-08 19:19 ` Oleg Nesterov
2011-06-08 14:04 ` [PATCH -v2] Audit: push audit success and retcode into arch Ralf Baechle
2011-06-08 14:04 ` [PATCH -v2] Audit: push audit success and retcode into arch ptrace.h Ralf Baechle
2011-06-08 14:04 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110608191910.GA18698@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=eparis@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=jdike@addtoit.com \
--cc=lethal@linux-sh.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=mingo@redhat.com \
--cc=monstr@monstr.eu \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=richard@nod.at \
--cc=schwidefsky@de.ibm.com \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.