An error occurred fetching the project authors.
  1. 16 Aug, 2003 10 commits
    • Alan Stern's avatar
      [PATCH] PATCH: (as70b) Update request_bufflen to match this_count · 133d35e0
      Alan Stern authored
      This patch addresses a problem in both sd.c and sr.c.  When a read/write
      command is initialized, the routines may reduce this_count (the number of
      sectors to transfer) if it exceeds the maximum allowed value (i.e., 0xffff
      for READ(10)).  However, the code does not similarly alter
      scmd->request_bufflen and scmd->bufflen to match the change in the CDB
      value.
      
      scmd->request_bufflen is important for the usb-storage driver, which
      requires that it be exactly equal to the number of bytes transferred.
      scmd->bufflen is used in the rw_intr() routines, where it is passed to
      scsi_io_completion() as the number of sectors transferred if no errors
      occur.
      
      Another small change in the patch concerns the code in sr.c that checks
      whether the total of the scatter-gather area lengths matches
      scmd->request_bufflen.  If they don't match, the patch bumps the kernel
      log message level up to KERN_ERR, and it takes the more conservative
      approach of adjusting scmd->request_bufflen only if the s-g length is
      smaller than the request length.
      133d35e0
    • Christoph Hellwig's avatar
      [PATCH] Re: scsi proc_info called unconditionally · 350e26aa
      Christoph Hellwig authored
      On Sat, Aug 16, 2003 at 10:44:09AM +0200, Olaf Hering wrote:
      >
      > Why is ->proc_info() called when the function pointer is NULL?
      
      Looks like the check for it's presence got lost in
      
      	[PATCH] Correct removal of procfs host enteries [1/2]
      
      Here's a trivial patch to get it back:
      350e26aa
    • Randy Dunlap's avatar
      [PATCH] ppa needs to scsi_unregister(host) · 9caf5bda
      Randy Dunlap authored
      When umounting a ppa device, I see (2.6.0-test3):
      
      Releasing ppa0
      Iomega VPI0 (ppa) interface did not call scsi_unregister
      Call Trace:
       [<f89aeca6>] exit_this_scsi_driver+0xb6/0xfa [ppa]
       [<c013c08d>] sys_delete_module+0x18d/0x1e0
       [<c0155276>] do_munmap+0x136/0x1b0
       [<c0155333>] sys_munmap+0x43/0x70
       [<c0109657>] syscall_call+0x7/0xb
      
      so ppa needs to call scsi_unregister().
      Is this all that's needed?
      
      --
      ~Randy
      
      
      patch_name:	scsi_ppa_unreg.patch
      patch_version:	2003-08-15.09:46:30
      author:		Randy.Dunlap <rddunlap@osdl.org>
      description:	ppa driver needs to call scsi_unregister(host);
      product:	Linux
      product_versions: 260-815
      maintainer:	campbell@torque.net
      diffstat:	=
       drivers/scsi/ppa.c |    1 +
       1 files changed, 1 insertion(+)
      9caf5bda
    • David Jeffery's avatar
      [PATCH] ips 4/4: version resync · b768d5c4
      David Jeffery authored
      This patch has no code changes.  It is just a resync of all the version
      numbers with the 6.10 driver and bumping up the driver version number.
      b768d5c4
    • James Bottomley's avatar
      ips 3/4: use pci_dma APIs and remove GFP abuse · cae1550d
      James Bottomley authored
      From: David Jeffery <david_jeffery@adaptec.com>
      (with minor reject fixes)
      
      This patch removes several places where we were using kmalloc flag
      tricks to always get memory <4GB instead of using the proper
      dma_alloc_consistent() API.  It also no longer #errors on when compiled
      for x86-64 kernels.
      cae1550d
    • James Bottomley's avatar
      ips 2/4: 2.4 resync · 23efa200
      James Bottomley authored
      From: David Jeffery <david_jeffery@adaptec.com>
      (with minor fixes for rejects)
      
      This patch is a resync with the 6.10 driver for 2.4 and updates the 2.4
      compatability code.  It adds a new wrapper function for differences
      between the 2.4 and 2.6 scsi proc interface,  forces pci posting in 3
      places, corrects using a meaningless constant of 0x80 to 0, and syncs
      comments that had changed. 
      23efa200
    • James Bottomley's avatar
      ips 1/4: lindent ips.c · 3ecd3030
      James Bottomley authored
      From: 	David Jeffery <david_jeffery@adaptec.com>
      (with fix ups for rejections on CONFIG_HIGHIO)
      
      This patch has no code changes.  It is only the result of running
      scripts/Lindent on drivers/scsi/ips.c in test3.  Rather than use this
      patch, it may be advisable to just run 
      
      sh scripts/Lindent drivers/scsi/ips.c 
      
      The nasty 3-4 space indenting in ips.c has always made it a pain to
      read.  The remaining patches in this patch set all assume ips.c has been
      lindented. 
      3ecd3030
    • Anton Blanchard's avatar
      [PATCH] another fix to sym2 hotplug conversion · 4e9f2a9a
      Anton Blanchard authored
      In sym_attach we call sym_hcb_attach. If it fails we call
      sym_free_resources which will call sym_hcb_free. Unfortunately
      sym_hcb_attach also calls sym_hcb_free on failure.
      
      This results in a bunch of things being freed twice and it looks like
      the sym2 memory allocator adds them to the freelist twice. Sometime later
      on we allocate the memory twice, with weird consequences.
      4e9f2a9a
    • Anton Blanchard's avatar
      [PATCH] minor fix to sym2 hotplug conversion · 1aac244b
      Anton Blanchard authored
      One problem we found when we hit a bad adapter, we need to use scsi_host_put.
      1aac244b
    • James Bottomley's avatar
      Add fastfail to SCSI · 5a659463
      James Bottomley authored
      This is the preliminary version with no error indications or
      control over the types of failures.
      5a659463
  2. 15 Aug, 2003 1 commit
    • James Bottomley's avatar
      oops in sd_shutdown · 177342da
      James Bottomley authored
      From: Andries Brouwer <aebr@win.tue.nl>
      
      I see an Oops in the SCSI code, caused by the fact that sdkp is NULL
      in sd_shutdown. "How can that be?", you will ask - dev->driver_data was set
      in sd_probe. But in my case sd_probe never finished. An insmod usb-storage
      hangs forever, or at least for more than six hours, giving ample opportunity
      to observe this race between sd_probe and sd_shutdown.
      (Of course sd_probe hangs in sd_revalidate disk.)
      
      Perhaps the obvious test is a good idea.
      Locking seems meaningless - sd_probe will never finish.
      177342da
  3. 14 Aug, 2003 27 commits
  4. 13 Aug, 2003 2 commits