1. 19 2月, 2009 1 次提交
  2. 12 2月, 2009 8 次提交
  3. 10 2月, 2009 7 次提交
  4. 08 2月, 2009 1 次提交
  5. 07 2月, 2009 13 次提交
  6. 06 2月, 2009 10 次提交
    • L
      Merge branch 'for-linus' of git://neil.brown.name/md · b2a740aa
      Linus Torvalds 提交于
      * 'for-linus' of git://neil.brown.name/md:
        md: Ensure an md array never has too many devices.
        md: Fix a bug in linear.c causing which_dev() to return the wrong device.
        md: Allow read error in a single drive raid1 to be passed up.
      b2a740aa
    • S
      ieee1394: dv1394: move deprecation message from module init to file open · 86431532
      Stefan Richter 提交于
      On many Linux installations, the dv1394 driver will be auto-loaded
      whenever an AV/C device (e.g. camcorder or audio device) is plugged in.
      An irritating message would then appear in the kernel log.
      
      Defer this message to until a dv1394 character device file is actually
      used by a program.  Also include the program name in the message and
      update the message slightly.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      86431532
    • T
      Merge branch 'fix/usb-audio' into for-linus · b0050cae
      Takashi Iwai 提交于
      b0050cae
    • T
      Merge branch 'fix/hda' into for-linus · b2573eb5
      Takashi Iwai 提交于
      b2573eb5
    • T
      ALSA: hda - Add missing COEF initialization for ALC887 · 4a5a4c56
      Takashi Iwai 提交于
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      4a5a4c56
    • T
      ALSA: hda - Add missing initialization for ALC272 · c6e8f2da
      Takashi Iwai 提交于
      ALC272 needs EAPD for speaker outputs as well as other similar ALC
      codecs.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      c6e8f2da
    • C
      sound: usb-audio: handle wMaxPacketSize for FIXED_ENDPOINT devices · 894dcd78
      Clemens Ladisch 提交于
      For audio devices that do not have proper audio descriptors (e.g.,
      Edirol UA-20), we use hardcoded parameters from our quirks list.
      However, we must still read the maximum packet size from the standard
      endpoint descriptor; otherwise, we might use packets that are too big
      and therefore rejected by the USB core.
      Signed-off-by: NClemens Ladisch <clemens@ladisch.de>
      Cc: <stable@kernel.org>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      894dcd78
    • N
      md: Ensure an md array never has too many devices. · de01dfad
      NeilBrown 提交于
      Each different metadata format supported by md supports a
      different maximum number of devices.
      We really should be enforcing this maximum in the kernel, but
      we aren't quite doing that properly.
      
      We currently only enforce it at the 'hot_add' point, which is an
      older interface which is not used by current userspace.
      
      We need to also enforce it at 'add_new_disk' time for active arrays
      and at 'do_md_run' time when starting a new array.
      
      So move the test from 'hot_add' into 'bind_rdev_to_array' which is
      called from both 'hot_add' and 'add_new_disk, and add a new
      test in 'analyse_sbs' which is called from 'do_md_run'.
      
      This bug (or missing feature) has been around "forever" and so
      the patch is suitable for any -stable that is currently maintained.
      
      Cc: stable@kernel.org
      Signed-off-by: NNeilBrown <neilb@suse.de>
      de01dfad
    • A
      md: Fix a bug in linear.c causing which_dev() to return the wrong device. · 852c8bf4
      Andre Noll 提交于
      ab5bd5cb introduced the following
      bug in linear software raid for large arrays on 32 bit machines:
      
      which_dev() computes the device holding a given sector by shifting
      down the sector number to a 32 bit range, dividing by the array
      spacing and looking up the resulting index in the hash table of
      the array.
      
      Because the computed index might be slightly too small, a loop at
      the end of which_dev() increases the index until the given sector
      actually falls into the range of the device associated with that index.
      
      The changes of the above mentioned commit caused this loop to check
      whether the _index_ rather than the sector number is small enough,
      effectively bypassing the loop and thus possibly returning the wrong
      device.
      
      As reported by Simon Kirby, this leads to errors such as
      
      	linear_make_request: Sector 2340486136 out of bounds on dev sdi: 156301312 sectors, offset 2109870464
      
      Fix this bug by introducing a local variable for the index so that
      the variable containing the passed sector is left unchanged.
      
      Cc: stable@kernel.org
      Signed-off-by: NAndre Noll <maan@systemlinux.org>
      Signed-off-by: NNeilBrown <neilb@suse.de>
      852c8bf4
    • N
      md: Allow read error in a single drive raid1 to be passed up. · 4706b349
      NeilBrown 提交于
      If a raid1 only has a single working device and gets a read error, 
      we choose to simply return that error up to the filesystem (or whatever)
      rather than failing the whole array.
      
      However the codes doesn't quite do that.  We attempt a readbalance
      which allocates the same drive, so we retry the read - indefinitely. 
      
      Instead:  If read_balance in the error case chooses the same drive that just
      failed, treat it as a failure and don't retry.
      Signed-off-by: NNeilBrown <neilb@suse.de>
      4706b349