linux-kernel - Re: khubd and ent:sda1 sucking CPU with reiser4 + USB HD

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]

Date:	Tue, 6 Mar 2007 09:52:02 +0100
From:	Oliver Neukum <oneukum@...e.de>
To:	ebuddington@...leyan.edu,
	"list, USB" <linux-usb-devel@...ts.sourceforge.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: khubd and ent:sda1 sucking CPU with reiser4 + USB HD

Am Dienstag, 6. März 2007 05:13 schrieb Eric Buddington:
> reiser4[khubd(163)]: commit_current_atom (fs/reiser4/txnmgr.c:1049)[nikita-3176]:
> WARNING: Flushing like mad: 16384
> reiser4[khubd(163)]: commit_current_atom (fs/reiser4/txnmgr.c:1049)[nikita-3176]:
> WARNING: Flushing like mad: 32768
> ...<many simiar messages>
> 
> Most problematically, khubd and ent:sda1! are conspiring to suck 100%
> CPU time, even after powering off the drive. A bunch of processes are
> stuck in 'D' state, possibly because they're trying to access the dead
> disk, which won't umount ("device is busy").

It looks like khubd allocates memory and enters reiser4. Possibly we have
GFP_KERNEL in khubd where we should have GFP_NOIO or reiser4 has
a problem dealing with IO failures.

	Regards
		Oliver

-
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/