https://bugzilla.novell.com/show_bug.cgi?id=757783 https://bugzilla.novell.com/show_bug.cgi?id=757783#c34 --- Comment #34 from Mike Galbraith <mgalbraith@suse.com> 2012-04-30 14:09:33 UTC --- (In reply to comment #33)
pid_ns leaks with -default and -xen domU
Likely this one. vsftpd-14507 [003] .... 1467.046189: proc_set_super: get_pid_ns: 0xffff8801dc560998 count:1->2 vsftpd-14507 [003] .... 1467.046201: create_pid_namespace: create_pid_namespace: 0xffff8801dc560998 vsftpd-14507 [003] .... 1467.046206: alloc_pid: get_pid_ns: 0xffff8801dc560998 count:2->3 vsftpd-14521 [003] .... 1467.052481: switch_task_namespaces: exiting: 0xffff8801dc560998 count:3 vsftpd-14521 [003] .... 1467.073823: free_nsproxy: put_pid_ns: 0xffff8801dc560998 count:3->2 vsftpd-14507 [003] .... 1467.173657: put_pid: namespace: 0xffff8801dc560998 pid count:2->1 pid_ns count:2 vsftpd-14507 [003] .... 1467.173677: proc_kill_sb: put_pid_ns: 0xffff8801dc560998 count:2->1 <idle>-0 [003] ..s. 1467.213562: put_pid: namespace: 0xffff8801dc560998 pid count:6->5 pid_ns count:1 While we wait for rcu destruction, someone grabs references to the pid, foiling grand destruction plan.. sometimes, like this one, plan is foiled permanently.
btw wonder why nobody reported this issue long time ago no one is using vsftpd on oS nowadays ?
Or folks have truckloads of ram, and don't notice a bit going missing. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.