linux-kernel - Re: kernel BUG at mm/slqb.c:1411!

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 13 May 2009 17:37:58 +0900
From:	Minchan Kim <minchan.kim@...il.com>
To:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc:	linux-mm <linux-mm@...ck.org>, LKML <linux-kernel@...r.kernel.org>,
	Nick Piggin <npiggin@...e.de>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: kernel BUG at mm/slqb.c:1411!

On Wed, 13 May 2009 16:42:37 +0900 (JST)
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:

Hmm. I don't know slqb well.
So, It's just my guess. 

We surely increase l->nr_partial in  __slab_alloc_page.
In between l->nr_partial++ and call __cache_list_get_page, Who is decrease l->nr_partial again.
After all, __cache_list_get_page return NULL and hit the VM_BUG_ON.

Comment said :

        /* Protects nr_partial, nr_slabs, and partial */
  spinlock_t    page_lock;

As comment is right, We have to hold the l->page_lock ?



-- 
Kinds Regards
Minchan Kim
--
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/