10 May, 2007

1 commit

  • Allow check_device_area to succeed if a device has an i_size of zero. This
    addresses an issue seen on DASD devices setting up a multipath table for paths
    in online and offline state.

    Signed-off-by: Mike Anderson
    Signed-off-by: Alasdair G Kergon
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mike Anderson
     

03 Oct, 2006

3 commits

  • This patch adds support for a per-target dm_flush_fn method. This is needed
    to allow dm-loop to invalidate page cache mappings in response to BLKFLSBUF
    ioctl commands.

    Signed-off-by: Bryn Reeves
    Signed-off-by: Alasdair G Kergon
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bryn Reeves
     
  • Separate the setting of device I/O limits from dm_get_device(). dm-loop will
    use this.

    Signed-off-by: Bryn Reeves
    Signed-off-by: Alasdair G Kergon
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Bryn Reeves
     
  • This patch adds a target preresume hook.

    It is called before the targets are resumed and if it returns an error the
    resume gets cancelled.

    The crypt target will use this to indicate that it is unable to process I/O
    because no encryption key has been supplied.

    Signed-off-by: Milan Broz
    Signed-off-by: Alasdair G Kergon
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Milan Broz
     

27 Jun, 2006

4 commits


28 Mar, 2006

4 commits

  • Semaphore to mutex conversion.

    The conversion was generated via scripts, and the result was validated
    automatically via a script as well.

    Signed-off-by: Arjan van de Ven
    Signed-off-by: Ingo Molnar
    Cc: Neil Brown
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Arjan van de Ven
     
  • Use bd_claim_by_disk.

    Following symlinks are created if dm-0 maps to sda:
    /sys/block/dm-0/slaves/sda --> /sys/block/sda
    /sys/block/sda/holders/dm-0 --> /sys/block/dm-0

    Signed-off-by: Jun'ichi Nomura
    Cc: Alasdair G Kergon
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jun'ichi Nomura
     
  • Store an up-pointer to the owning struct mapped_device in every table when it
    is created.

    Access it with:
    struct mapped_device *dm_table_get_md(struct dm_table *t)

    Tables linked to md must be destroyed before the md itself.

    Signed-off-by: Mike Anderson
    Signed-off-by: Alasdair G Kergon
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mike Anderson
     
  • This flag should be set for a virtual device iff it is set for all
    underlying devices.

    Signed-off-by: Neil Brown
    Acked-by: Alasdair G Kergon
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    NeilBrown
     

27 Mar, 2006

1 commit


02 Feb, 2006

1 commit


16 Dec, 2005

1 commit

  • - export __blk_put_request and blk_execute_rq_nowait
    needed for async REQ_BLOCK_PC requests
    - seperate max_hw_sectors and max_sectors for block/scsi_ioctl.c and
    SG_IO bio.c helpers per Jens's last comments. Since block/scsi_ioctl.c SG_IO was
    already testing against max_sectors and SCSI-ml was setting max_sectors and
    max_hw_sectors to the same value this does not change any scsi SG_IO behavior. It only
    prepares ll_rw_blk.c, scsi_ioctl.c and bio.c for when SCSI-ml begins to set
    a valid max_hw_sectors for all LLDs. Today if a LLD does not set it
    SCSI-ml sets it to a safe default and some LLDs set it to a artificial low
    value to overcome memory and feedback issues.

    Note: Since we now cap max_sectors to BLK_DEF_MAX_SECTORS, which is 1024,
    drivers that used to call blk_queue_max_sectors with a large value of
    max_sectors will now see the fs requests capped to BLK_DEF_MAX_SECTORS.

    Signed-off-by: Mike Christie
    Signed-off-by: James Bottomley

    Mike Christie
     

29 Jul, 2005

1 commit


13 Jul, 2005

1 commit


06 May, 2005

1 commit


17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds