1. 02 Oct, 2007 1 commit
    • Steve French's avatar
      [CIFS] Reduce chance of list corruption in find_writable_file · 9b22b0b7
      Steve French authored
      When find_writable_file is racing with close and the session
      to the server goes down, Shaggy noticed that there was a
      chance that an open file in the list of files off the inode
      could have been freed by close since cifs_reconnect can
      block (the spinlock thus not held). This means that
      we have to start over at the beginning of the list in some
      cases.
      
      There is a 2nd change that needs to be made later
      (pointed out by Jeremy Allison and Shaggy) in order to
      prevent cifs_close ever freeing the cifs per file info
      when a write is pending.  Although we delay close from
      freeing this memory for sufficiently long for all known
      cases, ultimately on a very, very slow write
      overlapping a close pending we need to allow close to return
      (without freeing the cifs file info) and defer freeing the
      memory to be the responsibility of the (sloooow) write
      thread (presumably have to look at every place wrtPending
      is decremented - and add a flag for deferred free for
      after wrtPending goes to zero).
      Acked-by: default avatarShaggy <shaggy@us.ibm.com>
      Acked-by: default avatarShirish Pargaonkar <shirishp@us.ibm.com>
      Signed-off-by: default avatarSteve French <sfrench@us.ibm.com>
      9b22b0b7
  2. 01 Oct, 2007 1 commit
  3. 29 Sep, 2007 1 commit
  4. 28 Sep, 2007 2 commits
  5. 25 Sep, 2007 2 commits
  6. 24 Sep, 2007 1 commit
  7. 20 Sep, 2007 3 commits
  8. 17 Sep, 2007 1 commit
  9. 16 Sep, 2007 1 commit
  10. 15 Sep, 2007 3 commits
  11. 13 Sep, 2007 1 commit
  12. 11 Sep, 2007 1 commit
  13. 07 Sep, 2007 1 commit
  14. 31 Aug, 2007 1 commit
  15. 30 Aug, 2007 3 commits
  16. 24 Aug, 2007 3 commits
  17. 22 Aug, 2007 3 commits
  18. 21 Aug, 2007 10 commits
  19. 20 Aug, 2007 1 commit
    • Bartlomiej Zolnierkiewicz's avatar
      ide-disk: workaround for buggy HPA support on ST340823A (take 3) · b0244a00
      Bartlomiej Zolnierkiewicz authored
      This disk reports total number of sectors instead of maximum sector address
      in response to READ_NATIVE_MAX_ADDRESS command and also happily accepts
      SET_MAX_ADDRESS command with the bogus value.  This results in +1 sector
      capacity being used and errors on attempts to use the last sector.
      
      ...
      hdd: Host Protected Area detected.
              current capacity is 78165360 sectors (40020 MB)
              native  capacity is 78165361 sectors (40020 MB)
      hdd: Host Protected Area disabled.
      ...
      hdd: reading: block=78165360, sectors=1, buffer=0xc1e63000
      hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
      hdd: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=78165360, sector=78165360
      ...
      
      Add hpa_list[] table and workaround the issue in idedisk_check_hpa().
      
      v2:
      * Add missing export and improve patch description a bit.
      
      v3:
      * Add list termination.  (From Mikko)
      
      Fixes kernel bugzilla bug #8816.
      
      Thanks to Mikko for investigating the issue and helping with this patch.
      
      Cc: Mikko Rapeli <mikko.rapeli@iki.fi>
      Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
      Signed-off-by: default avatarBartlomiej Zolnierkiewicz <bzolnier@gmail.com>
      b0244a00