1. 22 5月, 2010 1 次提交
    • T
      block: use struct parsed_partitions *state universally in partition check code · 1493bf21
      Tejun Heo 提交于
      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: NTejun Heo <tj@kernel.org>
      Cc: Ben Hutchings <ben@decadent.org.uk>
      Acked-by: NDavid S. Miller <davem@davemloft.net>
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      1493bf21
  2. 23 11月, 2009 1 次提交
    • K
      partitions: read whole sector with EFI GPT header · 87038c2d
      Karel Zak 提交于
      The size of EFI GPT header is not static, but whole sector is
      allocated for the header. The HeaderSize field must be greater
      than 92 (= sizeof(struct gpt_header) and must be less than or
      equal to the logical block size.
      
      It means we have to read whole sector with the header, because the
      header crc32 checksum is calculated according to HeaderSize.
      
      For more details see UEFI standard (version 2.3, May 2009):
        - 5.3.1 GUID Format overview, page 93
        - Table 13. GUID Partition Table Header, page 96
      Signed-off-by: NKarel Zak <kzak@redhat.com>
      Signed-off-by: NJens Axboe <jens.axboe@oracle.com>
      87038c2d
  3. 01 7月, 2006 1 次提交
  4. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4