1. 14 1月, 2014 1 次提交
    • A
      sound: oss: remove last sleep_on users · cdef2e5f
      Arnd Bergmann 提交于
      There are three files in oss for which I could not find an easy way to
      replace interruptible_sleep_on_timeout with a non-racy version. This
      patch instead just adds a private implementation of the function, now
      named oss_broken_sleep_on, and changes over the remaining users in
      sound/oss/ so we can remove the global interface.
      
      [fixed coding style warnings by tiwai]
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      cdef2e5f
  2. 15 3月, 2013 1 次提交
  3. 24 3月, 2011 1 次提交
    • D
      sound/oss: remove offset from load_patch callbacks · b769f494
      Dan Rosenberg 提交于
      Was: [PATCH] sound/oss/midi_synth: prevent underflow, use of
      uninitialized value, and signedness issue
      
      The offset passed to midi_synth_load_patch() can be essentially
      arbitrary.  If it's greater than the header length, this will result in
      a copy_from_user(dst, src, negative_val).  While this will just return
      -EFAULT on x86, on other architectures this may cause memory corruption.
      Additionally, the length field of the sysex_info structure may not be
      initialized prior to its use.  Finally, a signed comparison may result
      in an unintentionally large loop.
      
      On suggestion by Takashi Iwai, version two removes the offset argument
      from the load_patch callbacks entirely, which also resolves similar
      issues in opl3.  Compile tested only.
      
      v3 adjusts comments and hopefully gets copy offsets right.
      Signed-off-by: NDan Rosenberg <drosenberg@vsecurity.com>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      b769f494
  4. 11 11月, 2010 1 次提交
  5. 16 3月, 2010 1 次提交
  6. 26 2月, 2009 1 次提交
  7. 04 10月, 2006 3 次提交
  8. 29 3月, 2006 1 次提交
  9. 26 3月, 2006 1 次提交
  10. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4