1. 16 Feb, 2007 22 commits
  2. 15 Feb, 2007 14 commits
  3. 14 Feb, 2007 4 commits
    • Linus Torvalds's avatar
      Merge branch 'linus' of master.kernel.org:/pub/scm/linux/kernel/git/perex/alsa · 724339d7
      Linus Torvalds authored
      * 'linus' of master.kernel.org:/pub/scm/linux/kernel/git/perex/alsa:
        [ALSA] version 1.0.14rc2
        [ALSA] Fix a typo in __dev* changes in portman2x4.c
        [ALSA] Change AT91 PDC register defines for 2.6.20 kernel
        [ALSA] SoC codecs - fix Kconfig - depends -> depends on
        [ALSA] Fix __devinit and __devexit issues with sound drivers
        [ALSA] hda-codec - Patch for enabling LFE on more Dell laptops
        [ALSA] hda-codec - More fixes for Conexant HD Audio support
        [ALSA] usb-audio: add PCR-A PCM support
        [ALSA] emu10k1: fix typo
        [ALSA] usbaudio - remove urb->bandwidth reference
        [ALSA] ac97 - Fix silent output problem with Cx20551 codec
        [ALSA] hda-codec - Fix Oops with probing sigmatel codec chips
      724339d7
    • Linus Torvalds's avatar
      Merge branch 'for-linus' of git://one.firstfloor.org/home/andi/git/linux-2.6 · 414f827c
      Linus Torvalds authored
      * 'for-linus' of git://one.firstfloor.org/home/andi/git/linux-2.6: (94 commits)
        [PATCH] x86-64: Remove mk_pte_phys()
        [PATCH] i386: Fix broken CONFIG_COMPAT_VDSO on i386
        [PATCH] i386: fix 32-bit ioctls on x64_32
        [PATCH] x86: Unify pcspeaker platform device code between i386/x86-64
        [PATCH] i386: Remove extern declaration from mm/discontig.c, put in header.
        [PATCH] i386: Rename cpu_gdt_descr and remove extern declaration from smpboot.c
        [PATCH] i386: Move mce_disabled to asm/mce.h
        [PATCH] i386: paravirt unhandled fallthrough
        [PATCH] x86_64: Wire up compat epoll_pwait
        [PATCH] x86: Don't require the vDSO for handling a.out signals
        [PATCH] i386: Fix Cyrix MediaGX detection
        [PATCH] i386: Fix warning in cpu initialization
        [PATCH] i386: Fix warning in microcode.c
        [PATCH] x86: Enable NMI watchdog for AMD Family 0x10 CPUs
        [PATCH] x86: Add new CPUID bits for AMD Family 10 CPUs in /proc/cpuinfo
        [PATCH] i386: Remove fastcall in paravirt.[ch]
        [PATCH] x86-64: Fix wrong gcc check in bitops.h
        [PATCH] x86-64: survive having no irq mapping for a vector
        [PATCH] i386: geode configuration fixes
        [PATCH] i386: add option to show more code in oops reports
        ...
      414f827c
    • Eric W. Biederman's avatar
      [PATCH] sysctl: hide the sysctl proc inodes from selinux · 86a71dbd
      Eric W. Biederman authored
      Since the security checks are applied on each read and write of a sysctl file,
      just like they are applied when calling sys_sysctl, they are redundant on the
      standard VFS constructs.  Since it is difficult to compute the security labels
      on the standard VFS constructs we just mark the sysctl inodes in proc private
      so selinux won't even bother with them.
      Signed-off-by: default avatarEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      86a71dbd
    • Stephen Smalley's avatar
      [PATCH] selinux: enhance selinux to always ignore private inodes · bbaca6c2
      Stephen Smalley authored
      Hmmm...turns out to not be quite enough, as the /proc/sys inodes aren't truly
      private to the fs, so we can run into them in a variety of security hooks
      beyond just the inode hooks, such as security_file_permission (when reading
      and writing them via the vfs helpers), security_sb_mount (when mounting other
      filesystems on directories in proc like binfmt_misc), and deeper within the
      security module itself (as in flush_unauthorized_files upon inheritance across
      execve).  So I think we have to add an IS_PRIVATE() guard within SELinux, as
      below.  Note however that the use of the private flag here could be confusing,
      as these inodes are _not_ private to the fs, are exposed to userspace, and
      security modules must implement the sysctl hook to get any access control over
      them.
      Signed-off-by: default avatarEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: default avatarStephen Smalley <sds@tycho.nsa.gov>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      bbaca6c2