linux-kernel - Question about sys_ind (Partition ID fields)

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

Message-ID: <1548.69.2.248.210.1213895504.squirrel@webmail.wolfmountaingroup.com>
Date:	Thu, 19 Jun 2008 11:11:44 -0600 (MDT)
From:	jmerkey@...fmountaingroup.com
To:	linux-kernel@...r.kernel.org
Subject: Question about sys_ind (Partition ID fields)

Is there a reason why the sys_ind field (The partition ID) s not cached in
the hd_struct persistently?  I noticed that after the initial
check_partition calls through check_part[]() read all this data and only
remember the starting sector and size of a given partition.  Perhaps I am
missing something, and its stored somewhere else, but I have not located
it yet.

This seems somwhat wasteful since it requires the partition tables and/or
partitions to be re-read all the time instead of just remembering what
sys_ind was previously set.   The argument that it is this way for
supporting dynamic rescanning doesn't seem to match up to the way its
implemented since you have to rescan anyway in most cases.  It makes it
somewhat ackward whem you are instrumenting multi-partition storage
modules.

Jeff

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