1. 03 4月, 2009 1 次提交
  2. 30 12月, 2008 2 次提交
  3. 03 12月, 2008 1 次提交
  4. 02 12月, 2008 1 次提交
  5. 09 10月, 2008 1 次提交
  6. 12 7月, 2008 1 次提交
    • M
      [SCSI] aacraid: prevent copy_from_user() BUG! · 09050715
      Mark Salyzyn 提交于
      Seen:
      
      	kernel BUG at arch/i386/lib/usercopy.c:872
      
      under a 2.6.18-8.el5 kernel. Traced it to a garbage-in/garbage-out
      ioctl condition in the aacraid driver.
      
      Adaptec's special ioctl scb passthrough needs to check the validity of
      the individual scatter gather count fields to the maximum the adapter
      supports. Doing so will have the side effect of preventing
      copy_from_user() from bugging out while populating the dma buffers.
      This is a hardening effort, issue was triggered by an errant version
      of the management tools and thus the BUG should not be seen in the
      field.
      
      [jejb: fixed up compile failure]
      Signed-off-by: NMark Salyzyn <aacraid@adaptec.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      09050715
  7. 21 6月, 2008 1 次提交
  8. 05 6月, 2008 1 次提交
  9. 03 5月, 2008 3 次提交
  10. 02 5月, 2008 1 次提交
  11. 20 4月, 2008 1 次提交
  12. 19 4月, 2008 2 次提交
  13. 16 4月, 2008 2 次提交
  14. 08 4月, 2008 3 次提交
  15. 12 2月, 2008 3 次提交
  16. 08 2月, 2008 3 次提交
    • S
      [SCSI] aacraid: do not set valid bit in sense information · 8e31e607
      Salyzyn, Mark 提交于
      Luben Tuikov [mailto:ltuikov@yahoo.com] sez:
      > Just as in your case and Tony's case, which I presume
      > uses the same RAID firmware vendor, it would've
      > probably been better if the RAID firmware vendor
      > fixed the firmware to not set the VALID bit if the
      > INFORMATION field is not valid.
      
      Point taken regarding the aacraid driver. Dropped the VALID bit, and
      then did some cleanup/simplification of the set_sense procedure and
      the associated parameters. Mike did some preliminary tests when the
      VALID bit was dropped before the 'Re: [PATCH] [SCSI] sd: make error
      handling more robust' patches came on the scene. The change in the
      SCSI subsystem does make this enclosed aacraid patch unnecessary, so
      this aacraid patch is merely post battle ground cleanup. If the
      simplification is an issue, repugnant, too much for a back-port to the
      stable trees or clouds the point, this patch could be happily
      distilled down to:
      
      diff -ru a/drivers/scsi/aacraid/aachba.c b/drivers/scsi/aacraid/aachba.c
      --- a/drivers/scsi/aacraid/aachba.c     2008-02-06 16:26:45.834938955 -0500
      +++ b/drivers/scsi/aacraid/aachba.c     2008-02-06 16:32:01.109035329 -0500
      @@ -865,7 +865,7 @@
                               u32 residue)
       {
      -        sense_buf[0] = 0xF0;    /* Sense data valid, err code 70h (current error) */
      +        sense_buf[0] = 0x70;    /* Sense data invalid, err code 70h (current error) */
               sense_buf[1] = 0;       /* Segment number, always zero */
      
               if (incorrect_length) {
      Signed-off-by: NMark Salyzyn <aacraid@adaptec.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      8e31e607
    • S
      [SCSI] aacraid: pci_set_dma_max_seg_size opened up for late model controllers · 62e9f5c4
      Salyzyn, Mark 提交于
      This patch ensures that the modern adapters get a maximum sg segment
      size on par with the maximum transfer size. Added some localized
      janitor fixes to the discussion patch I used with Fujita.
      
      FUJITA Tomonori [mailto:fujita.tomonori@lab.ntt.co.jp] sez:
      > I think that setting the proper maximum segment size for the late
      > model cards (as you did above) makes sense.
      Signed-off-by: NMark Salyzyn <aacraid@adaptec.com>
      Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      62e9f5c4
    • S
      [SCSI] aacraid: fib context lock for management ioctls (take 2) · 5234e25c
      Salyzyn, Mark 提交于
      The first patch (a119ee8e) was a bit
      too aggressive and nested the locks (!) unit testing was in
      error. This patch was reverted by
      203a512f.
      
      This new patch should fix the locks correctly.
      Signed-off-by: NMark Salyzyn <aacraid@adaptec.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      5234e25c
  17. 06 2月, 2008 1 次提交
  18. 31 1月, 2008 2 次提交
  19. 25 1月, 2008 1 次提交
  20. 24 1月, 2008 9 次提交