| 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
| ||
|
Message-ID: <20120306185137.GA15881@redhat.com> Date: Tue, 6 Mar 2012 13:51:37 -0500 From: Dave Jones <davej@...hat.com> To: Linux Kernel <linux-kernel@...r.kernel.org> Cc: Fedora Kernel Team <kernel-team@...oraproject.org>, viro@...IV.linux.org.uk Subject: inode->i_wb_list corruption. We've had three separate reports against 3.2.x recently where the linked list debugging is getting tripped up by the prev->next pointer being null instead of pointing to the current list entry while walking the i_wb_list Call traces are slightly different each time, but all end up walking i_wb_list in dput -> d_kill -> i_put -> evict -> inode_wb_list_del What protects that list ? It looks to be just bdi->wb.list_lock ? full reports at: https://bugzilla.redhat.com/show_bug.cgi?id=784741 https://bugzilla.redhat.com/show_bug.cgi?id=799229 https://bugzilla.redhat.com/show_bug.cgi?id=799692 Dave -- 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