Make bsd process accounting work in pid namespaces
cover Make bsd process accounting work in pid namespaces
After I fixed access to task->tgid in kernel/acct.c, Oleg pointed out some bad side effects with this accounting vs pid namespaces interaction. I.e. when some task in pid namespace sets this accounting up, this blocks all the others from doing the same. Restricting this to init namespace only could help, but didn't look as a grace solution.
So here is the approach to make this accounting work with pid namespaces properly.
The idea is simple - when a task dies it accounts itself in each namespace it is visible from and which set the accounting up.
For example here are the commands run and the output of lastcomm from init and sub namespaces:
init_ns# accton pacct
sub_ns# accton pacct (this is a different file - sub ns is run in
a chroot-ed environment)
init_ns# cat /dev/null
sub_ns# ls /dev/null
init_ns# accton
sub_ns# accton
sub_ns# lastcomm -f pacct
ls 0 [136,0] 0.00 secs Thu May 15 10:30 accton 0 [136,0] 0.00 secs Thu May 15 10:30
init_ns# lastcomm -f pacct
accton root pts/0 0.00 secs Thu May 15 14:30 << got from sub cat root pts/1 0.00 secs Thu May 15 14:30 ls root pts/0 0.00 secs Thu May 15 14:30 << got from sub accton root pts/1 0.00 secs Thu May 15 14:30
That was the summary, the details are in patches.
The set was sent for RFC a month ago, but I got only one, but positive response from Oleg. Hopefully, he can confirm one now.
PATCH 1/10 Bsdacct: rename acct_blbls to bsd_acct_struct
It will be visible in pid_namespace.h file, so fix its name to look better outside the acct.c file.
--- kernel/acct.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
kernel/acct.c +2 -2
@@ -82,7 +82,7 @@ static void do_acct_process(struct pid_namespace *ns, struct file *);* can be placed in the same cache line as the lock. This primes * the cache line to have the data after getting the lock. */ -struct acct_glbs { +struct bsd_acct_struct {spinlock_t lock;volatile int active;volatile int needcheck;
@@ -91,7 +91,7 @@ struct acct_glbs {struct timer_list timer; }; -static struct acct_glbs acct_globals __cacheline_aligned = +static struct bsd_acct_struct acct_globals __cacheline_aligned = {__SPIN_LOCK_UNLOCKED (acct_globals.lock)};/*
Signature · 1 line
1.5.3.4
PATCH 2/10 Pidns: use kzalloc when allocating new pid_namespace struct
In reply to Pavel EmelyanovIt makes many fields initialization implicit helping in auto-setting #ifdef-ed fields (bsd-acct related pointer will be such).
--- kernel/pid_namespace.c | 8 ++------ 1 files changed, 2 insertions(+), 6 deletions(-)
kernel/pid_namespace.c +2 -6
@@ -71,7 +71,7 @@ static struct pid_namespace *create_pid_namespace(unsigned int level)struct pid_namespace *ns;int i; - ns =kmem_cache_alloc (pid_ns_cachep,GFP_KERNEL ); + ns =kmem_cache_zalloc (pid_ns_cachep,GFP_KERNEL );if (ns ==NULL ) goto out;
@@ -84,17 +84,13 @@ static struct pid_namespace *create_pid_namespace(unsigned int level) goto out_free_map;kref_init (&ns->kref); - ns->last_pid =0 ; - ns->child_reaper =NULL ; ns->level = level;set_bit (0 , ns->pidmap[0 ].page);atomic_set (&ns->pidmap[0 ].nr_free,BITS_PER_PAGE -1 ); -for (i =1 ; i <PIDMAP_ENTRIES ; i++) { - ns->pidmap[i].page =NULL ; +for (i =1 ; i <PIDMAP_ENTRIES ; i++)atomic_set (&ns->pidmap[i].nr_free,BITS_PER_PAGE ); - }return ns;
Signature · 1 line
1.5.3.4
PATCH 3/10 Pidns: add the struct bsd_acct_struct pointer on pid_namespace struct
In reply to Pavel EmelyanovAll the bsdacct-related info will be stored in the area, pointer by this one.
It will be NULL automatically for all new namespaces.
--- include/linux/pid_namespace.h | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-)
include/linux/pid_namespace.h +5 -0
@@ -14,6 +14,8 @@ struct pidmap {#define PIDMAP_ENTRIES ((PID_MAX_LIMIT + 8*PAGE_SIZE - 1)/PAGE_SIZE/8) +struct bsd_acct_struct ; +struct pid_namespace {struct kref kref;struct pidmap pidmap[PIDMAP_ENTRIES ];
@@ -25,6 +27,9 @@ struct pid_namespace {#ifdef CONFIG_PROC_FS struct vfsmount *proc_mnt;#endif +#ifdef CONFIG_BSD_PROCESS_ACCT +struct bsd_acct_struct *bacct; +#endif };extern struct pid_namespace init_pid_ns;
Signature · 1 line
1.5.3.4
PATCH 4/10 Bsdacct: "truthify" a comment near acct_process
In reply to Pavel EmelyanovThe acct_process does not accept any arguments actually.
--- kernel/acct.c | 1 - 1 files changed, 0 insertions(+), 1 deletions(-)
kernel/acct.c +0 -1
@@ -579,7 +579,6 @@ void acct_collect(long exitcode, int group_dead)/** * acct_process - now just a wrapper around do_acct_process -* @exitcode: task exit code * * handles process accounting for an exiting task */
Signature · 1 line
1.5.3.4
PATCH 5/10 Bsdacct: make check timer accept a bsd_acct_struct argument
In reply to Pavel EmelyanovWe're going to have many bsd_acct_struct instances, not just one, so the timer (currently working with a global one) has to know which one to work with.
Use a handy setup_timer macro for it (thanks to Oleg for one).
--- kernel/acct.c | 9 +++++---- 1 files changed, 5 insertions(+), 4 deletions(-)
kernel/acct.c +5 -4
@@ -97,9 +97,10 @@ static struct bsd_acct_struct acct_globals __cacheline_aligned =/* * Called whenever the timer says to check the free space. */ -static void acct_timeout (unsigned long unused) +static void acct_timeout (unsigned long x) { - acct_globals.needcheck =1 ; +struct bsd_acct_struct *acct = (struct bsd_acct_struct *)x; + acct->needcheck =1 ; }/*
@@ -193,8 +194,8 @@ static void acct_file_reopen(struct file *file) acct_globals.needcheck =0 ; acct_globals.active =1 ;/* It's been deleted if it was used before so this is safe */ -init_timer (&acct_globals.timer); - acct_globals.timer.function = acct_timeout; +setup_timer (&acct_globals.timer, acct_timeout, + (unsigned long )&acct_globals); acct_globals.timer.expires = jiffies +ACCT_TIMEOUT *HZ ;add_timer (&acct_globals.timer); }
Signature · 1 line
1.5.3.4
PATCH 6/10 Bsdacct: turn the acct_lock from on-the-struct to global
In reply to Pavel EmelyanovDon't use per-bsd-acct-struct lock, but work with a global one.
This lock is taken for short periods, so it doesn't seem it'll become a bottleneck, but it will allow us to easily avoid many locking difficulties in the future.
So this is a mostly s/acct_globals.lock/acct_lock/ over the file.
--- kernel/acct.c | 42 +++++++++++++++++++++--------------------- 1 files changed, 21 insertions(+), 21 deletions(-)
kernel/acct.c +21 -21
@@ -83,7 +83,6 @@ static void do_acct_process(struct pid_namespace *ns, struct file *);* the cache line to have the data after getting the lock. */ struct bsd_acct_struct { -spinlock_t lock;volatile int active;volatile int needcheck;struct file *file;
@@ -91,8 +90,9 @@ struct bsd_acct_struct {struct timer_list timer; }; -static struct bsd_acct_struct acct_globals __cacheline_aligned = - {__SPIN_LOCK_UNLOCKED (acct_globals.lock)}; +static DEFINE_SPINLOCK (acct_lock); + +static struct bsd_acct_struct acct_globals __cacheline_aligned;/* * Called whenever the timer says to check the free space.
@@ -114,11 +114,11 @@ static int check_free_space(struct file *file)sector_t resume;sector_t suspend; -spin_lock (&acct_globals.lock); +spin_lock (&acct_lock); res = acct_globals.active;if (!file || !acct_globals.needcheck) goto out; -spin_unlock (&acct_globals.lock); +spin_unlock (&acct_lock);/* May block */ if (vfs_statfs (file->f_path.dentry, &sbuf))
@@ -140,7 +140,7 @@ static int check_free_space(struct file *file)* If some joker switched acct_globals.file under us we'ld better be * silent and _not_ touch anything. */ -spin_lock (&acct_globals.lock); +spin_lock (&acct_lock);if (file != acct_globals.file) {if (act) res = act>0 ;
@@ -165,7 +165,7 @@ static int check_free_space(struct file *file)add_timer (&acct_globals.timer); res = acct_globals.active; out: -spin_unlock (&acct_globals.lock); +spin_unlock (&acct_lock);return res; }
@@ -173,7 +173,7 @@ out:* Close the old accounting file (if currently open) and then replace * it with file (if non-NULL). * -* NOTE: acct_globals.lock MUST be held on entry and exit. +* NOTE: acct_lock MUST be held on entry and exit. */ static void acct_file_reopen (struct file *file) {
@@ -201,11 +201,11 @@ static void acct_file_reopen(struct file *file) }if (old_acct) {mnt_unpin (old_acct->f_path.mnt); -spin_unlock (&acct_globals.lock); +spin_unlock (&acct_lock);do_acct_process (old_ns, old_acct);filp_close (old_acct,NULL );put_pid_ns (old_ns); -spin_lock (&acct_globals.lock); +spin_lock (&acct_lock); } }
@@ -235,10 +235,10 @@ static int acct_on(char *name)return error; } -spin_lock (&acct_globals.lock); +spin_lock (&acct_lock);mnt_pin (file->f_path.mnt);acct_file_reopen (file); -spin_unlock (&acct_globals.lock); +spin_unlock (&acct_lock);mntput (file->f_path.mnt);/* it's pinned, now give up active reference */
@@ -272,9 +272,9 @@ asmlinkage long sys_acct(const char __user *name) }else { error =security_acct (NULL );if (!error) { -spin_lock (&acct_globals.lock); +spin_lock (&acct_lock);acct_file_reopen (NULL ); -spin_unlock (&acct_globals.lock); +spin_unlock (&acct_lock); } }return error;
@@ -289,10 +289,10 @@ asmlinkage long sys_acct(const char __user *name)*/ void acct_auto_close_mnt (struct vfsmount *m) { -spin_lock (&acct_globals.lock); +spin_lock (&acct_lock);if (acct_globals.file && acct_globals.file->f_path.mnt == m)acct_file_reopen (NULL ); -spin_unlock (&acct_globals.lock); +spin_unlock (&acct_lock); }/**
@@ -304,12 +304,12 @@ void acct_auto_close_mnt(struct vfsmount *m)*/ void acct_auto_close (struct super_block *sb) { -spin_lock (&acct_globals.lock); +spin_lock (&acct_lock);if (acct_globals.file && acct_globals.file->f_path.mnt->mnt_sb == sb) {acct_file_reopen (NULL ); } -spin_unlock (&acct_globals.lock); +spin_unlock (&acct_lock); }/*
@@ -594,15 +594,15 @@ void acct_process(void)if (!acct_globals.file)return ; -spin_lock (&acct_globals.lock); +spin_lock (&acct_lock); file = acct_globals.file;if (unlikely (!file)) { -spin_unlock (&acct_globals.lock); +spin_unlock (&acct_lock);return ; }get_file (file); ns =get_pid_ns (acct_globals.ns); -spin_unlock (&acct_globals.lock); +spin_unlock (&acct_lock);do_acct_process (ns, file);fput (file);
Signature · 1 line
1.5.3.4
PATCH 7/10 Bsdacct: make internal code work with passed bsd_acct_struct, not global
In reply to Pavel EmelyanovThis adds the appropriate pointer to all the internal (i.e. static) functions that work with global acct instance. API calls pass a global instance to them (while we still have such).
Mostly this is a s/acct_globals./acct->/ over the file.
--- kernel/acct.c | 77 +++++++++++++++++++++++++++++---------------------------- 1 files changed, 39 insertions(+), 38 deletions(-)
kernel/acct.c +39 -38
@@ -75,7 +75,8 @@ int acct_parm[3] = {4, 2, 30};/* * External references and all of the globals. */ -static void do_acct_process (struct pid_namespace *ns,struct file *); +static void do_acct_process (struct bsd_acct_struct *acct, +struct pid_namespace *ns,struct file *);/* * This structure is used so that all the data protected by lock
@@ -106,7 +107,7 @@ static void acct_timeout(unsigned long x)/* * Check the amount of free space and suspend/resume accordingly. */ -static int check_free_space (struct file *file) +static int check_free_space (struct bsd_acct_struct *acct,struct file *file) {struct kstatfs sbuf;int res;
@@ -115,8 +116,8 @@ static int check_free_space(struct file *file)sector_t suspend;spin_lock (&acct_lock); - res = acct_globals.active; -if (!file || !acct_globals.needcheck) + res = acct->active; +if (!file || !acct->needcheck) goto out;spin_unlock (&acct_lock);
@@ -137,33 +138,33 @@ static int check_free_space(struct file *file) act =0 ;/* -* If some joker switched acct_globals.file under us we'ld better be +* If some joker switched acct->file under us we'ld better be * silent and _not_ touch anything. */ spin_lock (&acct_lock); -if (file != acct_globals.file) { +if (file != acct->file) {if (act) res = act>0 ; goto out; } -if (acct_globals.active) { +if (acct->active) {if (act <0 ) { - acct_globals.active =0 ; + acct->active =0 ;printk (KERN_INFO "Process accounting paused\n" ); } }else {if (act >0 ) { - acct_globals.active =1 ; + acct->active =1 ;printk (KERN_INFO "Process accounting resumed\n" ); } } -del_timer (&acct_globals.timer); - acct_globals.needcheck =0 ; - acct_globals.timer.expires = jiffies +ACCT_TIMEOUT *HZ ; -add_timer (&acct_globals.timer); - res = acct_globals.active; +del_timer (&acct->timer); + acct->needcheck =0 ; + acct->timer.expires = jiffies +ACCT_TIMEOUT *HZ ; +add_timer (&acct->timer); + res = acct->active; out:spin_unlock (&acct_lock);return res;
@@ -175,34 +176,33 @@ out:* * NOTE: acct_lock MUST be held on entry and exit. */ -static void acct_file_reopen (struct file *file) +static void acct_file_reopen (struct bsd_acct_struct *acct,struct file *file) {struct file *old_acct =NULL ;struct pid_namespace *old_ns =NULL ; -if (acct_globals.file) { - old_acct = acct_globals.file; - old_ns = acct_globals.ns; -del_timer (&acct_globals.timer); - acct_globals.active =0 ; - acct_globals.needcheck =0 ; - acct_globals.file =NULL ; +if (acct->file) { + old_acct = acct->file; + old_ns = acct->ns; +del_timer (&acct->timer); + acct->active =0 ; + acct->needcheck =0 ; + acct->file =NULL ; }if (file) { - acct_globals.file = file; - acct_globals.ns =get_pid_ns (task_active_pid_ns (current)); - acct_globals.needcheck =0 ; - acct_globals.active =1 ; + acct->file = file; + acct->ns =get_pid_ns (task_active_pid_ns (current)); + acct->needcheck =0 ; + acct->active =1 ;/* It's been deleted if it was used before so this is safe */ -setup_timer (&acct_globals.timer, acct_timeout, - (unsigned long )&acct_globals); - acct_globals.timer.expires = jiffies +ACCT_TIMEOUT *HZ ; -add_timer (&acct_globals.timer); +setup_timer (&acct->timer, acct_timeout, (unsigned long )acct); + acct->timer.expires = jiffies +ACCT_TIMEOUT *HZ ; +add_timer (&acct->timer); }if (old_acct) {mnt_unpin (old_acct->f_path.mnt);spin_unlock (&acct_lock); -do_acct_process (old_ns, old_acct); +do_acct_process (acct, old_ns, old_acct);filp_close (old_acct,NULL );put_pid_ns (old_ns);spin_lock (&acct_lock);
@@ -237,7 +237,7 @@ static int acct_on(char *name)spin_lock (&acct_lock);mnt_pin (file->f_path.mnt); -acct_file_reopen (file); +acct_file_reopen (&acct_globals, file);spin_unlock (&acct_lock);mntput (file->f_path.mnt);/* it's pinned, now give up active reference */
@@ -273,7 +273,7 @@ asmlinkage long sys_acct(const char __user *name) error =security_acct (NULL );if (!error) {spin_lock (&acct_lock); -acct_file_reopen (NULL ); +acct_file_reopen (&acct_globals,NULL );spin_unlock (&acct_lock); } }
@@ -291,7 +291,7 @@ void acct_auto_close_mnt(struct vfsmount *m) {spin_lock (&acct_lock);if (acct_globals.file && acct_globals.file->f_path.mnt == m) -acct_file_reopen (NULL ); +acct_file_reopen (&acct_globals,NULL );spin_unlock (&acct_lock); }
@@ -307,7 +307,7 @@ void acct_auto_close(struct super_block *sb)spin_lock (&acct_lock);if (acct_globals.file && acct_globals.file->f_path.mnt->mnt_sb == sb) { -acct_file_reopen (NULL ); +acct_file_reopen (&acct_globals,NULL ); }spin_unlock (&acct_lock); }
@@ -426,7 +426,8 @@ static u32 encode_float(u64 value)/* * do_acct_process does all actual work. Caller holds the reference to file. */ -static void do_acct_process (struct pid_namespace *ns,struct file *file) +static void do_acct_process (struct bsd_acct_struct *acct, +struct pid_namespace *ns,struct file *file) {struct pacct_struct *pacct = ¤t->signal->pacct;acct_t ac;
@@ -441,7 +442,7 @@ static void do_acct_process(struct pid_namespace *ns, struct file *file)* First check to see if there is enough free_space to continue * the process accounting system. */ -if (!check_free_space (file)) +if (!check_free_space (acct, file))return ;/*
@@ -604,7 +605,7 @@ void acct_process(void) ns =get_pid_ns (acct_globals.ns);spin_unlock (&acct_lock); -do_acct_process (ns, file); +do_acct_process (&acct_globals, ns, file);fput (file);put_pid_ns (ns); }
Signature · 1 line
1.5.3.4
PATCH 8/10 Bsdacct: switch from global bsd_acct_struct instance to per-pidns one
In reply to Pavel EmelyanovAllocate the structure on the first call to sys_acct(). After this each namespace, that ordered the accounting, will live with this structure till its own death.
Two notes
- routines, that close the accounting on fs umount time use the init_pid_ns's acct by now;
- accounting routine accounts to dying task's namespace (also by now).
--- include/linux/acct.h | 3 ++ kernel/acct.c | 84 +++++++++++++++++++++++++++++++++++++---------- kernel/pid_namespace.c | 2 + 3 files changed, 71 insertions(+), 18 deletions(-)
include/linux/acct.h +3 -0
@@ -120,17 +120,20 @@ struct acct_v3struct vfsmount ;struct super_block ;struct pacct_struct ; +struct pid_namespace ;extern void acct_auto_close_mnt (struct vfsmount *m);extern void acct_auto_close (struct super_block *sb);extern void acct_init_pacct (struct pacct_struct *pacct);extern void acct_collect (long exitcode,int group_dead);extern void acct_process (void ); +extern void acct_exit_ns (struct pid_namespace *);#else #define acct_auto_close_mnt (x) do { } while (0)#define acct_auto_close (x) do { } while (0)#define acct_init_pacct (x) do { } while (0)#define acct_collect (x,y) do { } while (0)#define acct_process () do { } while (0) +#define acct_exit_ns (ns) do { } while (0)#endif /*
kernel/acct.c +66 -18
176 lines not on this page · raw message
kernel/pid_namespace.c +2 -0
@@ -12,6 +12,7 @@#include <linux/pid_namespace.h> #include <linux/syscalls.h> #include <linux/err.h> +#include <linux/acct.h> #define BITS_PER_PAGE (PAGE_SIZE*8)
@@ -181,6 +182,7 @@ void zap_pid_ns_processes(struct pid_namespace *pid_ns)/* Child reaper for the pid namespace is going away */ pid_ns->child_reaper =NULL ; +acct_exit_ns (pid_ns);return ; }
Signature · 1 line
1.5.3.4
PATCH 9/10 Bsdacct: turn acct off for all pidns-s on umount time
In reply to Pavel EmelyanovAll the bsd_acct_strcts with opened accounting are linked into a global list. So, the acct_auto_close(_mnt) walks one and drops the accounting for each.
--- kernel/acct.c | 28 ++++++++++++++++------------ 1 files changed, 16 insertions(+), 12 deletions(-)
kernel/acct.c +16 -12
@@ -89,9 +89,11 @@ struct bsd_acct_struct {struct file *file;struct pid_namespace *ns;struct timer_list timer; +struct list_head list; };static DEFINE_SPINLOCK (acct_lock); +static LIST_HEAD (acct_list);/* * Called whenever the timer says to check the free space.
@@ -188,12 +190,14 @@ static void acct_file_reopen(struct bsd_acct_struct *acct, struct file *file, acct->needcheck =0 ; acct->file =NULL ; acct->ns =NULL ; +list_del (&acct->list); }if (file) { acct->file = file; acct->ns = ns; acct->needcheck =0 ; acct->active =1 ; +list_add (&acct->list, &acct_list);/* It's been deleted if it was used before so this is safe */ setup_timer (&acct->timer, acct_timeout, (unsigned long )acct); acct->timer.expires = jiffies +ACCT_TIMEOUT *HZ ;
@@ -314,13 +318,13 @@ void acct_auto_close_mnt(struct vfsmount *m) {struct bsd_acct_struct *acct; - acct = init_pid_ns.bacct; -if (acct ==NULL ) -return ; -spin_lock (&acct_lock); -if (acct->file && acct->file->f_path.mnt == m) -acct_file_reopen (acct,NULL ,NULL ); +restart: +list_for_each_entry (acct, &acct_list, list) +if (acct->file && acct->file->f_path.mnt == m) { +acct_file_reopen (acct,NULL ,NULL ); + goto restart; + }spin_unlock (&acct_lock); }
@@ -335,13 +339,13 @@ void acct_auto_close(struct super_block *sb) {struct bsd_acct_struct *acct; - acct = init_pid_ns.bacct; -if (acct ==NULL ) -return ; -spin_lock (&acct_lock); -if (acct->file && acct->file->f_path.mnt->mnt_sb == sb) -acct_file_reopen (acct,NULL ,NULL ); +restart: +list_for_each_entry (acct, &acct_list, list) +if (acct->file && acct->file->f_path.mnt->mnt_sb == sb) { +acct_file_reopen (acct,NULL ,NULL ); + goto restart; + }spin_unlock (&acct_lock); }
Signature · 1 line
1.5.3.4
PATCH 10/10 Bsdacct: account dying tasks in all relevant namespaces
In reply to Pavel EmelyanovThis just makes the acct_proces walk the pid namespaces from current up to the top and account a task in each with the accounting turned on.
ns->parent access if safe lockless, since current it still alive and holds its namespace, which in turn holds its parent.
--- kernel/acct.c | 21 ++++++++++++++------- 1 files changed, 14 insertions(+), 7 deletions(-)
kernel/acct.c +14 -7
@@ -631,15 +631,9 @@ void acct_collect(long exitcode, int group_dead)spin_unlock_irq (¤t->sighand->siglock); } -/** -* acct_process - now just a wrapper around do_acct_process -* -* handles process accounting for an exiting task -*/ -void acct_process (void ) +static void acct_process_in_ns (struct pid_namespace *ns) {struct file *file =NULL ; -struct pid_namespace *ns =task_active_pid_ns (current);struct bsd_acct_struct *acct; acct = ns->bacct;
@@ -661,3 +655,16 @@ void acct_process(void)do_acct_process (acct, ns, file);fput (file); } + +/** +* acct_process - now just a wrapper around do_acct_process +* +* handles process accounting for an exiting task +*/ +void acct_process (void ) +{ +struct pid_namespace *ns; + +for (ns =task_active_pid_ns (current); ns !=NULL ; ns = ns->parent) +acct_process_in_ns (ns); +}
Signature · 1 line
1.5.3.4
Re: [PATCH 10/10] Bsdacct: account dying tasks in all relevant namespaces
Quoted 2 lines · On Thu, 15 May 2008 15:11:55 +0400 Pavel Emelyanov <[email protected]> wrote:
+/**
+ *acct_process- now just a wrapper arounddo_acct_process
comment seems wrong.
kernel/acct.c void acct_process(void) · line 670
Quoted 9 lines
+ * handles process accounting for an exiting task
+ */kernel/acct.c +7
-0+void acct_process (void ) +{ +struct pid_namespace *ns; + +for (ns =task_active_pid_ns (current); ns !=NULL ; ns = ns->parent) +acct_process_in_ns (ns); +}
Is it really safe to walk this list locklessly?
Re: [PATCH 10/10] Bsdacct: account dying tasks in all relevant namespaces
Quoted 6 lines · Andrew Morton
Quoted 2 lines · On Thu, 15 May 2008 15:11:55 +0400 Pavel Emelyanov <[email protected]> wrote:
+/**
+ *acct_process- now just a wrapper arounddo_acct_processcomment seems wrong.
Oops. I've fixed it once and forgot to re-check after the set. Will do shortly.
Quoted 11 lines
kernel/acct.c void acct_process(void) · line 670
Quoted 9 lines
+ * handles process accounting for an exiting task
+ */kernel/acct.c +7
-0+void acct_process (void ) +{ +struct pid_namespace *ns; + +for (ns =task_active_pid_ns (current); ns !=NULL ; ns = ns->parent) +acct_process_in_ns (ns); +}Is it really safe to walk this list locklessly?
Well, yes - I wrote it in the comment to the 10th patch:
"ns->parent access if safe lockless, since current it still
alive and holds its namespace, which in turn holds its parent."
Should I also add this as a comment here?
Thanks,
Pavel
Re: [PATCH 10/10] Bsdacct: account dying tasks in all relevant namespaces
Quoted 13 lines · On Fri, 16 May 2008 14:11:04 +0400 Pavel Emelyanov <[email protected]> wrote:
Quoted 12 lines
kernel/acct.c void acct_process(void) · line 670
Quoted 10 lines
+ * handles process accounting for an exiting task
+ */kernel/acct.c +7
-0+void acct_process (void ) +{ +struct pid_namespace *ns; + +for (ns =task_active_pid_ns (current); ns !=NULL ; ns = ns->parent) +acct_process_in_ns (ns); +}Is it really safe to walk this list locklessly?
Quoted 4 lines
Well, yes - I wrote it in the comment to the 10th patch:
"
ns->parentaccess if safe lockless, since current it still
alive and holds its namespace, which in turn holds its parent."
oic.
Quoted 1 line
Should I also add this as a comment here?
It wouldn't hurt...
Quoted 9 lines · On Thu, 15 May 2008 14:52:46 +0400 Pavel Emelyanov <[email protected]> wrote:
fter I fixed access to
task->tgidinkernel/acct.c, Oleg pointed out some bad side effects with this accounting vs pid namespaces interaction. I.e. when some task in pid namespace sets this accounting up, this blocks all the others from doing the same. Restricting this to init namespace only could help, but didn't look as a grace solution.So here is the approach to make this accounting work with pid namespaces properly.
We still have this silliness in acct_file_reopen():
spin_unlock(&acct_lock); do_acct_process(acct, old_ns, old_acct); filp_close(old_acct, NULL); spin_lock(&acct_lock);
Was this lock-dropping safe before?
Is it safe now?
To work this out, we'd need to know what acct_lock protects. What does acct_lock protect?
Quoted 14 lines · Andrew Morton
Quoted 9 lines · On Thu, 15 May 2008 14:52:46 +0400 Pavel Emelyanov <[email protected]> wrote:
fter I fixed access to
task->tgidinkernel/acct.c, Oleg pointed out some bad side effects with this accounting vs pid namespaces interaction. I.e. when some task in pid namespace sets this accounting up, this blocks all the others from doing the same. Restricting this to init namespace only could help, but didn't look as a grace solution.So here is the approach to make this accounting work with pid namespaces properly.
We still have this silliness in
acct_file_reopen():
Quoted 8 lines
spin_unlock(&acct_lock); do_acct_process(acct, old_ns, old_acct); filp_close(old_acct, NULL); spin_lock(&acct_lock);Was this lock-dropping safe before?
Is it safe now?
Yup :)
Quoted 2 lines
To work this out, we'd need to know what
acct_lockprotects. What doesacct_lockprotect?
It protected the acct_glbls state before this set. This re-lock was OK before wrt. acct_glbls members and still such now.
After the set it still does so and (!) also protects the list of those bsd_acct_struct-s, that have a file opened.
So, as far as the list is concerned. There are two places, that walk this list under this lock and call acct_file_reopen - the acct_auto_close and the acct_auto_close_mnt - both perform "goto restart" to start the iteration from the very beginning, so this re-lock doesn't affect this list integrity. List modifications (add/del) always happen under this lock.
Thanks,
Pavel