linux-kernel - Re: [2.6.36-rc1] List corruption when using initrd.

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: <201008180113.o7I1DXg6077317@www262.sakura.ne.jp>
Date:	Wed, 18 Aug 2010 10:13:33 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	hughd@...gle.com
Cc:	tim.c.chen@...ux.intel.com, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org, viro@...iv.linux.org.uk,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [2.6.36-rc1] List corruption when using initrd.

Hugh Dickins wrote:
> Thanks for reporting and bisecting.  Certainly there's a bug in shmem
> (that we ought to have caught long before it reached 36-rc1: sorry),
> and it is probably the cause of your crashes; but it's possible there's
> a similar bug elsewhere too, something else messing up the percpu_counters
> list - so please check if the patch below really does fix it for you.

This patch solved the list_add() corruption messages and
"[2.6.36-rc1] Bugs in __free_pipe_info()".

> I notice your dmesg also showed fs/inode.c:692 unlock_new_inode()
> warnings from get_cramfs_inode(): those would be unrelated, and
> probably from Al Viro's recent changes in cramfs/inode.c - Cc'ed.
unlock_new_inode() warnings remain after applying this patch.

Thank you.
--
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/