linux-kernel - Re: [PATCH 4/8] block: use struct parsed_partitions *state universally in partition check code

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.001652.267947899.davem@davemloft.net>
Date:	Sun, 16 May 2010 00:16:52 -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 4/8] block: use struct parsed_partitions *state
 universally in partition check code

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

> Make the following changes to partition check code.
> 
> * Add ->bdev to struct parsed_partitions.
> 
> * Introduce read_part_sector() which is a simple wrapper around
>   read_dev_sector() which takes struct parsed_partitions *state
>   instead of @bdev.
> 
> * For functions which used to take @state and @bdev, drop @bdev.  For
>   functions which used to take @bdev, replace it with @state.
> 
> * While updating, drop superflous checks on NULL state/bdev in ldm.c.
> 
> This cleans up the API a bit and enables better handling of IO errors
> during partition check as the generic partition check code now has
> much better visibility into what went wrong in the low level code
> paths.
> 
> 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/