1. 05 10月, 2007 1 次提交
    • S
      [CIFS] Fix cifsd so shuts down when signing fails during mount · a013689d
      Steve French 提交于
      Fixes two problems:
      1) we dropped down to negotiating lanman if we did not recognize the
      mechanism (krb5 e.g.)
      2) we did not stop cifsd (thus will fail when doing rmod cifs with
      slab free errors) when we fail tcon but have a bad session (which is
      the case in which signing is required but we don't allow signing on
      the client)
      
      It also turns on extended security flag in the header when passing
      "sec=krb5" on mount command (although kerberos support is not done of
      course)
      Acked-by: NJeff Layton <jlayton@redhat.com>
      CC: Shaggy <shaggy@us.ibm.com>
      Signed-off-by: NSteve French <sfrench@us.ibm.com>
      a013689d
  2. 04 10月, 2007 3 次提交
  3. 02 10月, 2007 2 次提交
    • S
      [CIFS] Reduce chance of list corruption in find_writable_file · 9b22b0b7
      Steve French 提交于
      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: NShaggy <shaggy@us.ibm.com>
      Acked-by: NShirish Pargaonkar <shirishp@us.ibm.com>
      Signed-off-by: NSteve French <sfrench@us.ibm.com>
      9b22b0b7
    • S
      [CIFS] change misleading field name · 4084973d
      Steve French 提交于
      num_auth is really num_subauth in ACL terminology
      Signed-off-by: NSteve French <sfrench@us.ibm.com>
      4084973d
  4. 29 9月, 2007 2 次提交
  5. 28 9月, 2007 1 次提交
  6. 26 9月, 2007 2 次提交
  7. 25 9月, 2007 1 次提交
  8. 20 9月, 2007 3 次提交
  9. 17 9月, 2007 2 次提交
  10. 15 9月, 2007 3 次提交
  11. 14 9月, 2007 1 次提交
  12. 11 9月, 2007 1 次提交
  13. 08 9月, 2007 1 次提交
  14. 31 8月, 2007 4 次提交
  15. 24 8月, 2007 3 次提交
  16. 23 8月, 2007 1 次提交
  17. 21 8月, 2007 2 次提交
    • Z
      dio: zero struct dio with kzalloc instead of manually · 848c4dd5
      Zach Brown 提交于
      This patch uses kzalloc to zero all of struct dio rather than manually
      trying to track which fields we rely on being zero.  It passed aio+dio
      stress testing and some bug regression testing on ext3.
      
      This patch was introduced by Linus in the conversation that lead up to
      Badari's minimal fix to manually zero .map_bh.b_state in commit:
      
        6a648fa7
      
      It makes the code a bit smaller.  Maybe a couple fewer cachelines to
      load, if we're lucky:
      
         text    data     bss     dec     hex filename
      3285925  568506 1304616 5159047  4eb887 vmlinux
      3285797  568506 1304616 5158919  4eb807 vmlinux.patched
      
      I was unable to measure a stable difference in the number of cpu cycles
      spent in blockdev_direct_IO() when pushing aio+dio 256K reads at
      ~340MB/s.
      
      So the resulting intent of the patch isn't a performance gain but to
      avoid exposing ourselves to the risk of finding another field like
      .map_bh.b_state where we rely on zeroing but don't enforce it in the
      code.
      Signed-off-by: NZach Brown <zach.brown@oracle.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      848c4dd5
    • D
      JFFS2 locking regression fix. · b5748643
      David Woodhouse 提交于
      Commit a491486a introduced a locking
      problem in JFFS2 -- we up() the alloc_sem when we weren't previously
      holding it. This leads to all kinds of fun behaviour later.
      
      There was a _reason_ for the
      	if (1 /* alternative path needs testing */ ||
      which the above-mentioned commit removed :)
      
      Discovered and debugged by Giulio Fedel <giulio.fedel@andorsystems.com>
      Signed-off-by: NDavid Woodhouse <dwmw2@infradead.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      b5748643
  18. 19 8月, 2007 1 次提交
  19. 18 8月, 2007 1 次提交
  20. 14 8月, 2007 5 次提交