linux-kernel - Tracking down a workqueue io source

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>] [day] [month] [year] [list]

Message-ID: <52433113.1000806@ubuntu.com>
Date:	Wed, 25 Sep 2013 14:53:07 -0400
From:	Phillip Susi <psusi@...ntu.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-ide@...r.kernel.org
Subject: Tracking down a workqueue io source

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I worked up some patches to use the ata SLEEP command instead of
STANDBY to save more power, but I have found that something in the
kernel keeps issuing a request to the disk ( no mounted filesystems on
it ) every 10 minutes.  This request resets the link bringing the disk
back up to STANDBY mode.  blktrace shows the process name is "pool" so
I guess it is a work queue item?  Inserting a dump_stack() was not
helpful.  How can I track down the source of this request?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSQzETAAoJEJrBOlT6nu75Pu0IAMOSNFLbklwCjmVMFZjuQk2x
zrc6xOfPPmPsFqHUPG1TaoSUgzGJXsbZLUeaVFV2ZEIOFJPVl8Vn4Izkzyemk9dp
xtgbtECLMCMZujpqGpL6UwBwBepUfDvoRSpdpcjZ28XByrXS1V8SrQtBw/4HtnDm
Pkmf2MXxlqGDhAxCCuKHfnvjlP2pjfEt8teFH9Vsj4znMJw4BUC8IOepDATwbGd3
WEEv5kqmN27K7ZiEE3zo3jaQMlUtWrJwdyU+1zwvvdTpos/USdem9P4n80s5+CYm
S7e0awRKOjleEZnozyNU9VO5tLViuKyp2096/6+gvna7MIE/Mgj7aWI/S4+A28c=
=f2IA
-----END PGP SIGNATURE-----
--
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/