linux-kernel - Re: [BUG] soft lockup detected with ipcs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0803022214190.15209@jikos.suse.cz>
Date:	Sun, 2 Mar 2008 22:23:25 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jiri Olsa <olsajiri@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>
cc:	linux-kernel@...r.kernel.org, Nadia Derbey <Nadia.Derbey@...l.net>,
	peifferp@...il.com
Subject: Re: [BUG] soft lockup detected with ipcs

On Sun, 2 Mar 2008, Jiri Olsa wrote:

> I got more logs via netconsole, first I ran ipcs it segfaulted next run
> the system freezed.

Did you run ipcs without any arguments? If so, it should only call 
shmctl(SHM_INFO) and shmctl(SHM_STAT), so the only two spinlocks involved 
should be either shmem_inode_info->lock in shm_get_stat() or 
kern_ipc_perm->out_lock in ipc_lock().

Could you please try what is the output with the attached patch below, so 
that we know which spinlock buggers?

Also, could you please provide strace of the first (segfaulting) 
invocation of ipcs?

On Sun, 2 Mar 2008, Andrew Morton wrote:

> > [  144.699366] BUG: unable to handle kernel paging request at virtual address 6b6b6c2b
[ ... ]
> Looks like you got a use-after free when lockdep was playing with a 
> spinlock which is taken in sys_shmctl() or one of its inlined callees.

BTW any idea where does the '2b' come from? (it's single-bit flip).

-- 
Jiri Kosina
SUSE Labs
--
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/