1. 07 6月, 2014 3 次提交
  2. 13 2月, 2013 2 次提交
    • E
      coda: Restrict coda messages to the initial user namespace · d83f5901
      Eric W. Biederman 提交于
      Remove the slight chance that uids and gids in coda messages will be
      interpreted in the wrong user namespace.
      
      - Only allow processes in the initial user namespace to open the coda
        character device to communicate with coda filesystems.
      - Explicitly convert the uids in the coda header into the initial user
        namespace.
      - In coda_vattr_to_attr make kuids and kgids from the initial user
        namespace uids and gids in struct coda_vattr that just came from
        userspace.
      - In coda_iattr_to_vattr convert kuids and kgids into uids and gids
        in the intial user namespace and store them in struct coda_vattr for
        sending to coda userspace programs.
      
      Nothing needs to be changed with mounts as coda does not support
      being mounted in anything other than the initial user namespace.
      
      Cc: Jan Harkes <jaharkes@cs.cmu.edu>
      Signed-off-by: N"Eric W. Biederman" <ebiederm@xmission.com>
      d83f5901
    • E
      coda: Restrict coda messages to the initial pid namespace · 9fd973e0
      Eric W. Biederman 提交于
      Remove the slight chance that pids in coda messages will be
      interpreted in the wrong pid namespace.
      
      - Explicitly send all pids in coda messages in the initial pid
        namespace.
      - Only allow mounts from processes in the initial pid namespace.
      - Only allow processes in the initial pid namespace to open the coda
        character device to communicate with coda.
      
      Cc: Jan Harkes <jaharkes@cs.cmu.edu>
      Signed-off-by: N"Eric W. Biederman" <ebiederm@xmission.com>
      9fd973e0
  3. 29 3月, 2012 1 次提交
  4. 13 1月, 2011 1 次提交
  5. 25 10月, 2010 2 次提交
  6. 08 8月, 2010 1 次提交
  7. 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
  8. 14 11月, 2008 1 次提交
  9. 26 7月, 2008 1 次提交
    • A
      coda: remove CODA_FS_OLD_API · de0ca06a
      Adrian Bunk 提交于
      While fixing CONFIG_ leakages to the userspace kernel headers I ran into
      CODA_FS_OLD_API.
      
      After five years, are there still people using the old API left?
      Especially considering that you have to choose at compile time which API
      to support in the kernel (and distributions tend to offer the new API for
      some time).
      
      Jan: "The old API can definitely go.  Around the time the new
            interface went in there were some non-Coda userspace file system
            implementations that took a while longer to convert to the new API,
            but by now they all switched to the new interface or in some cases
            to a FUSE-based solution."
      Signed-off-by: NAdrian Bunk <bunk@kernel.org>
      Acked-by: NJan Harkes <jaharkes@cs.cmu.edu>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      de0ca06a
  10. 20 10月, 2007 1 次提交
    • P
      pid namespaces: round up the API · a47afb0f
      Pavel Emelianov 提交于
      The set of functions process_session, task_session, process_group and
      task_pgrp is confusing, as the names can be mixed with each other when looking
      at the code for a long time.
      
      The proposals are to
      * equip the functions that return the integer with _nr suffix to
        represent that fact,
      * and to make all functions work with task (not process) by making
        the common prefix of the same name.
      
      For monotony the routines signal_session() and set_signal_session() are
      replaced with task_session_nr() and set_task_session(), especially since they
      are only used with the explicit task->signal dereference.
      Signed-off-by: NPavel Emelianov <xemul@openvz.org>
      Acked-by: NSerge E. Hallyn <serue@us.ibm.com>
      Cc: Kirill Korotaev <dev@openvz.org>
      Cc: "Eric W. Biederman" <ebiederm@xmission.com>
      Cc: Cedric Le Goater <clg@fr.ibm.com>
      Cc: Herbert Poetzl <herbert@13thfloor.at>
      Cc: Sukadev Bhattiprolu <sukadev@us.ibm.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      a47afb0f
  11. 22 7月, 2007 1 次提交
    • J
      coda: remove CODA_STORE/CODA_RELEASE upcalls · d3fec424
      Jan Harkes 提交于
      This is an variation on the patch sent by Christoph Hellwig which kills
      file_count abuse by the Coda kernel module by moving the coda_flush
      functionality into coda_release.  However part of reason we were using the
      coda_flush callback was to allow Coda to pass errors that occur during
      writeback from the userspace cache manager back to close().
      
      As Al Viro explained on linux-fsdevel, it is impossible to guarantee that
      such errors can in fact be returned back to the caller.  There are many
      cases where the last reference to a file is not released by the close
      system call and it is also impossible to pick some close as a 'last-close'
      and delay it until all other references have been destroyed.
      
      The CODA_STORE/CODA_RELEASE upcall combination is clearly a broken design,
      and it is better to remove it completely.
      Signed-off-by: NJan Harkes <jaharkes@cs.cmu.edu>
      Cc: Christoph Hellwig <hch@lst.de>
      Cc: Al Viro <viro@ftp.linux.org.uk>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      d3fec424
  12. 20 7月, 2007 10 次提交
  13. 22 5月, 2007 1 次提交
    • A
      Detach sched.h from mm.h · e8edc6e0
      Alexey Dobriyan 提交于
      First thing mm.h does is including sched.h solely for can_do_mlock() inline
      function which has "current" dereference inside. By dealing with can_do_mlock()
      mm.h can be detached from sched.h which is good. See below, why.
      
      This patch
      a) removes unconditional inclusion of sched.h from mm.h
      b) makes can_do_mlock() normal function in mm/mlock.c
      c) exports can_do_mlock() to not break compilation
      d) adds sched.h inclusions back to files that were getting it indirectly.
      e) adds less bloated headers to some files (asm/signal.h, jiffies.h) that were
         getting them indirectly
      
      Net result is:
      a) mm.h users would get less code to open, read, preprocess, parse, ... if
         they don't need sched.h
      b) sched.h stops being dependency for significant number of files:
         on x86_64 allmodconfig touching sched.h results in recompile of 4083 files,
         after patch it's only 3744 (-8.3%).
      
      Cross-compile tested on
      
      	all arm defconfigs, all mips defconfigs, all powerpc defconfigs,
      	alpha alpha-up
      	arm
      	i386 i386-up i386-defconfig i386-allnoconfig
      	ia64 ia64-up
      	m68k
      	mips
      	parisc parisc-up
      	powerpc powerpc-up
      	s390 s390-up
      	sparc sparc-up
      	sparc64 sparc64-up
      	um-x86_64
      	x86_64 x86_64-up x86_64-defconfig x86_64-allnoconfig
      
      as well as my two usual configs.
      Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      e8edc6e0
  14. 27 6月, 2006 1 次提交
  15. 23 6月, 2006 1 次提交
  16. 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