lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <201105182238380008479@foxmail.com>
Date:	Wed, 18 May 2011 22:38:39 +0800
From:	"Lina Lu" <lulina_nuaa@...mail.com>
To:	"dhowells" <dhowells@...hat.com>
Cc:	"linux kernel mailing list" <linux-kernel@...r.kernel.org>
Subject: Re: CRED: Fix get_task_cred() and task_state() to not resurrect dead credentials

Hi David,

I found your get_cred patch on the community website and put the patch in my linux 
system to avoid cred problems. But the system got two abnormal situations.

One is that the kernel got a bug at line 168 in kernel/cred.c after running about seven
days. 

The other is kernel panic with the following backtrace.
CRED: put_cred_rcu() sees ffff88008626e800 with usage -3. 
I got confused, how the usage -3 was generated. 

The kernel trace information is as follows: 

kernel_trace
       <ffffffff803794d7>{notifier_call_chain+0x37} 
       <ffffffff80372d32>{panic+0xa2} 
       <ffffffff8005ae56>{put_cred_rcu+0xa6} 
       <ffffffff8008da55>{__rcu_process_callbacks+0x145} 
       <ffffffff8008dd66>{rcu_process_callbacks+0x26} 
       <ffffffff8004389e>{__do_softirq+0xde} 
       <ffffffff80007f3c>{call_softirq+0x1c} 
       <ffffffff80009535>{do_softirq+0xa5} 
       <ffffffff80279e82>{evtchn_do_upcall+0x212} 
       <ffffffff8000799e>{do_hypervisor_callback+0x1e} 
       [<ffffffff800033aa>] 
       <ffffffff8000a826>{xen_safe_halt+0xb6} 
       <ffffffff8000de1d>{xen_idle+0x5d} 
       <ffffffff800065cf>{cpu_idle+0x5f} 

Task tree: 
process:swapper (pid:0, tgid:0) 

I am looking forward to your reply. Any reply is appreciated. 

Thank you very much! 
f
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ