linux-kernel - Q. private_destroy_list in fsnotify_mark

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: <1318.1327416223@jrobl>
Date:	Tue, 24 Jan 2012 23:43:43 +0900
From:	"J. R. Okajima" <hooanon05@...oo.co.jp>
To:	eparis@...hat.com
cc:	linux-kernel@...r.kernel.org
Subject: Q. private_destroy_list in fsnotify_mark_destroy()

Hello Eric Paris,

In fsnotify_mark_destroy(), private_destroy_list is replaced by global
destroy_list, and the function calls fsnotify_put_mark() for each
fsnotify mark.
And waits for the global destroy_list becomes empty.
Should it be private_destroy_list? I am afraid the fsnotify_mark_destroy
kthread may cause a deadlock.

J. R. Okajima
--
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/