linux-kernel - Re: [PATCH 5/8] block: improve automatic native capacity unlocking

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: <20100516.001742.22051241.davem@davemloft.net>
Date:	Sun, 16 May 2010 00:17:42 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	tj@...nel.org
Cc:	jeff@...zik.org, linux-ide@...r.kernel.org, jens.axboe@...cle.com,
	linux-scsi@...r.kernel.org, James.Bottomley@...e.de,
	linux-kernel@...r.kernel.org, ben@...adent.org.uk,
	bzolnier@...il.com
Subject: Re: [PATCH 5/8] block: improve automatic native capacity unlocking

From: Tejun Heo <tj@...nel.org>
Date: Sat, 15 May 2010 20:09:31 +0200

> Currently, native capacity unlocking is initiated only when a
> recognized partition extends beyond the end of the disk.  However,
> there are several other unhandled cases where truncated capacity can
> lead to misdetection of partitions.
> 
> * Partition table is fully beyond EOD.
> 
> * Partition table is partially beyond EOD (daisy chained ones).
> 
> * Recognized partition starts beyond EOD.
> 
> This patch updates generic partition check code such that all the
> above three cases are handled too.  For the first two, @state tracks
> whether low level partition check code tried to read beyond EOD during
> partition scan and triggers native capacity unlocking accordingly.
> The third is now handled similarly to the original unlocking case.
> 
> Signed-off-by: Tejun Heo <tj@...nel.org>

Acked-by: David S. Miller <davem@...emloft.net>
--
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/