linux-ext4 - [Bug 16312] WARNING: at fs/fs-writeback.c:1127 __mark_inode

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]

Message-Id: <201007261359.o6QDxxnl026714@demeter.kernel.org>
Date:	Mon, 26 Jul 2010 13:59:59 GMT
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 16312] WARNING: at fs/fs-writeback.c:1127 __mark_inode_dirty

https://bugzilla.kernel.org/show_bug.cgi?id=16312





--- Comment #8 from Jan Kara <jack@...e.cz>  2010-07-26 13:59:55 ---
Hmm, looking at the original report referenced, my patches need not fix this
particular warning. This particular warning rather looks like a race when
udisks-part-id manages to read the device (and touch it's atime) before
sd_probe_async runs and registers the bdi (via add_disk()). That seems to be
possible as device_add() is run before we even schedule to run sd_async_probe()
in a separate thread.

Jens, any idea how this should be fixed? I believe we should avoid this race
because we should better have the device's queue fully set up before allowing
IO to it... But I'm far from fully understanding this area...

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html