linux-kernel - Re: 2.6.28 /proc/diskstats

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: <49E29386.20204@solemnwarning.net>
Date:	Mon, 13 Apr 2009 02:21:10 +0100
From:	Daniel Collins <solemnwarning@...emnwarning.net>
To:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.28 /proc/diskstats

I've stepped through the commits in linux-2.6, the first revision with 
this behavior is 074a7aca7afa6f230104e8e65eba3420263714a5

Daniel Collins wrote:
> Hi
>
> Since 2.6.28, fd0 isn't visible in /proc/diskstats from boot, only 
> after access/mount. It is visible in /sys/block/ from boot, so there 
> are no issues detecting it. This may also affect other devices such as 
> hda but I haven't tested this yet, my test system and QEMU both only 
> have ram0-ram15 from boot. I have tested 2.6.30-rc1 and found the same 
> behavior. Is this a bug or a deliberate change?
>
> Thanks
--
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/