linux-kernel - kernel: 3.1-rc4: disk tracing query

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

Message-ID: <alpine.DEB.2.02.1109051758360.23828@p34.internal.lan>
Date:	Mon, 5 Sep 2011 18:01:30 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	linux-kernel@...r.kernel.org
cc:	Alan Piszcz <ap@...arrain.com>
Subject: kernel: 3.1-rc4: disk tracing query

Hello,

I found that samba seems to stat() the filesystems that are shared out 
even if you are not accessing the ones in question, e.g.:

/raid
/home/user

If I access the server by \\name it will check all of the directories and 
thus wake the raid.
For now I've disabled samba to stop this behavior.

However, I am still noticing my raid waking up from time to time, I've 
tried using gresecurity to track down what is getting exec()'d before it 
wakes but I have not had any luck finding out what it is-- no useful notes 
in the raid ctrl logs either.

Is there a way I can get the kernel to log what program/syscall/etc is 
trying to access a particular block device so I can find out what is 
causing the raid to wake up?

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