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] [day] [month] [year] [list]
Message-ID: <y0mk5cymwh2.fsf@ton.toronto.redhat.com>
Date:	Fri, 26 Sep 2008 17:24:41 -0400
From:	fche@...hat.com (Frank Ch. Eigler)
To:	Chris Snook <csnook@...hat.com>
Cc:	Martin Knoblauch <knobi@...bisoft.de>,
	linux-kernel@...r.kernel.org,
	Peter zijlstra <a.p.zijlstra@...llo.nl>,
	Fengguang Wu <wfg@...l.ustc.edu.cn>,
	systemtap@...rces.redhat.com
Subject: Re: How to find out, what "pdflush" is working on


> [...]
>> Is there a way to find out what a certain instance of "pdflush" is
>> working on? Like which block-device or which fliesystem it is
>> writing to? [...]

Something based upon the following systemtap script may help:

probe kernel.function("__writeback_single_inode") {
  if (execname() == "pdflush")
     printf("pdflush %d writeback bdev %x inode %x\n", tid(), $inode->i_rdev, $inode->i_ino) 
}

Other fields are available as $inode->FOO.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ