1. 12 9月, 2012 1 次提交
  2. 07 9月, 2012 1 次提交
  3. 15 8月, 2012 1 次提交
  4. 24 8月, 2011 1 次提交
  5. 11 11月, 2010 1 次提交
    • J
      ALSA: sound/pci/ctxfi/ctpcm.c: Remove potential for use after free · fa2b30af
      Julia Lawall 提交于
      In each function, the value apcm is stored in the private_data field of
      runtime.  At the same time the function ct_atc_pcm_free_substream is stored
      in the private_free field of the same structure.  ct_atc_pcm_free_substream
      dereferences and ultimately frees the value in the private_data field.  But
      each function can exit in an error case with apcm having been freed, in
      which case a subsequent call to the private_free function would perform a
      dereference after free.  On the other hand, if the private_free field is
      not initialized, it is NULL, and not invoked (see snd_pcm_detach_substream
      in sound/core/pcm.c).  To avoid the introduction of a dangling pointer, the
      initializations of the private_data and private_free fields are moved to
      the end of the function, past any possible free of apcm.  This is safe
      because the previous calls to snd_pcm_hw_constraint_integer and
      snd_pcm_hw_constraint_minmax, which take runtime as an argument, do not
      refer to either of these fields.
      
      In each function, there is one error case where apcm needs to be freed, and
      a call to kfree is added.
      
      The sematic match that finds this problem is as follows:
      (http://coccinelle.lip6.fr/)
      
      // <smpl>
      @@
      expression e,e1,e2,e3;
      identifier f,free1,free2;
      expression a;
      @@
      
      *e->f = a
      ... when != e->f = e1
          when any
      if (...) {
        ... when != free1(...,e,...)
            when != e->f = e2
      * kfree(a)
        ... when != free2(...,e,...)
            when != e->f = e3
      }
      // </smpl>
      Signed-off-by: NJulia Lawall <julia@diku.dk>
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      fa2b30af
  6. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  7. 22 7月, 2009 1 次提交
  8. 22 6月, 2009 1 次提交
  9. 09 6月, 2009 1 次提交
    • T
      ALSA: ctxfi - Clear PCM resources at hw_params and hw_free · a5990dc5
      Takashi Iwai 提交于
      Currently the PCM resources are allocated only once and ever in prepare
      callback, assuming that the PCM parameters are never changed.  But it's
      not true.
      
      This patch adds the call of atc->pcm_release_resources() at hw_params
      and hw_free callbacks to assure that the PCM setup is done correctly
      for each h/w parameter changes.
      Signed-off-by: NTakashi Iwai <tiwai@suse.de>
      a5990dc5
  10. 08 6月, 2009 1 次提交
  11. 05 6月, 2009 2 次提交
  12. 02 6月, 2009 3 次提交
  13. 14 5月, 2009 2 次提交