1. 04 8月, 2006 1 次提交
  2. 25 7月, 2006 1 次提交
  3. 15 7月, 2006 2 次提交
  4. 11 7月, 2006 1 次提交
  5. 04 7月, 2006 1 次提交
    • I
      [PATCH] lockdep: floppy.c irq release fix · 3e541a4a
      Ingo Molnar 提交于
      The lock validator triggered a number of bugs in the floppy driver, all
      related to the floppy driver allocating and freeing irq and dma resources from
      interrupt context.  The initial solution was to use schedule_work() to push
      this into process context, but this caused further problems: for example the
      current floppy driver in -mm2 is totally broken and all floppy commands time
      out with an error.  (as reported by Barry K.  Nathan)
      
      This patch tries another solution: simply get rid of all that dynamic IRQ and
      DMA allocation/freeing.  I doubt it made much sense back in the heydays of
      floppies (if two devices raced for DMA or IRQ resources then we didnt handle
      those cases too gracefully anyway), and today it makes near zero sense.
      
      So the new code does the simplest and most straightforward thing: allocate IRQ
      and DMA resources at module init time, and free them at module removal time.
      Dont try to release while the driver is operational.  This, besides making the
      floppy driver functional again has an added bonus, floppy IRQ stats are
      finally persistent and visible in /proc/interrupts:
      
        6: 63 XT-PIC-level floppy
      
      Besides normal floppy IO i have also tested IO error handling, motor-off
      timeouts, etc.  - and everything seems to be working fine.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NArjan van de Ven <arjan@linux.intel.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      3e541a4a
  6. 03 7月, 2006 2 次提交
  7. 02 7月, 2006 1 次提交
  8. 01 7月, 2006 1 次提交
  9. 30 6月, 2006 1 次提交
  10. 29 6月, 2006 1 次提交
  11. 28 6月, 2006 1 次提交
  12. 27 6月, 2006 9 次提交
  13. 26 6月, 2006 14 次提交
  14. 23 6月, 2006 2 次提交
  15. 22 6月, 2006 2 次提交
    • P
      [PATCH] ub: random cleanups · b5600339
      Pete Zaitcev 提交于
      Remove some silly messages and cast in stone "temporary" messages which
      we keep around. Also, I am hesitant to remove the initialization retries
      without having the hardware to test (anyone who was at KS04 has a spare?)
      Signed-off-by: NPete Zaitcev <zaitcev@yahoo.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      b5600339
    • P
      [PATCH] ub: atomic add_disk · 688e9fb1
      Pete Zaitcev 提交于
      <zaitcev> I am taling about this: "if (disk->flags & GENHD_FL_UP) del_gendisk(disk);"
      <zaitcev> If del_gendisk() undoes add_disk() like viro just said, why is it conditional?
      <viro> huh?
      <viro> add_disk() sets the damn flag
      <zaitcev> So, I should not need to check ever
      <viro> so the above is "if I've called add_disk(), call gendisk()"
      <viro> which might be what you want, of course
      <viro> but usually you know if you'd done add_disk() on that puppy anyway
      
      In ub, nobody upstream should ever see half-constructed disks before
      they were passed to add_disk. To that end, only add the struct lun to
      the list on the path of no return. With that fix in place, we do
      not need to test GENHD_FL_UP.
      Signed-off-by: NPete Zaitcev <zaitcev@redhat.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      688e9fb1