24 Oct, 2008

1 commit

  • * git://git.kernel.org/pub/scm/linux/kernel/git/viro/bdev: (66 commits)
    [PATCH] kill the rest of struct file propagation in block ioctls
    [PATCH] get rid of struct file use in blkdev_ioctl() BLKBSZSET
    [PATCH] get rid of blkdev_locked_ioctl()
    [PATCH] get rid of blkdev_driver_ioctl()
    [PATCH] sanitize blkdev_get() and friends
    [PATCH] remember mode of reiserfs journal
    [PATCH] propagate mode through swsusp_close()
    [PATCH] propagate mode through open_bdev_excl/close_bdev_excl
    [PATCH] pass fmode_t to blkdev_put()
    [PATCH] kill the unused bsize on the send side of /dev/loop
    [PATCH] trim file propagation in block/compat_ioctl.c
    [PATCH] end of methods switch: remove the old ones
    [PATCH] switch sr
    [PATCH] switch sd
    [PATCH] switch ide-scsi
    [PATCH] switch tape_block
    [PATCH] switch dcssblk
    [PATCH] switch dasd
    [PATCH] switch mtd_blkdevs
    [PATCH] switch mmc
    ...

    Linus Torvalds
     

23 Oct, 2008

24 commits


21 Oct, 2008

2 commits

  • ubd_ioctl() doesn't need BKL, so unlocked_ioctl() it becomes...

    Signed-off-by: Al Viro

    Al Viro
     
  • To keep the size of changesets sane we split the switch by drivers;
    to keep the damn thing bisectable we do the following:
    1) rename the affected methods, add ones with correct
    prototypes, make (few) callers handle both. That's this changeset.
    2) for each driver convert to new methods. *ALL* drivers
    are converted in this series.
    3) kill the old (renamed) methods.

    Note that it _is_ a flagday; all in-tree drivers are converted and by the
    end of this series no trace of old methods remain. The only reason why
    we do that this way is to keep the damn thing bisectable and allow per-driver
    debugging if anything goes wrong.

    New methods:
    open(bdev, mode)
    release(disk, mode)
    ioctl(bdev, mode, cmd, arg) /* Called without BKL */
    compat_ioctl(bdev, mode, cmd, arg)
    locked_ioctl(bdev, mode, cmd, arg) /* Called with BKL, legacy */

    Signed-off-by: Al Viro

    Al Viro
     

20 Oct, 2008

2 commits

  • Fix

    arch/um/sys-i386/signal.c: In function 'copy_sc_from_user':
    arch/um/sys-i386/signal.c:182: warning: dereferencing 'void *' pointer
    arch/um/sys-i386/signal.c:182: error: request for member '_fxsr_env' in something not a structure or union

    Signed-off-by: WANG Cong
    Cc: Jeff Dike
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    WANG Cong
     
  • This patch implements a new freezer subsystem in the control groups
    framework. It provides a way to stop and resume execution of all tasks in
    a cgroup by writing in the cgroup filesystem.

    The freezer subsystem in the container filesystem defines a file named
    freezer.state. Writing "FROZEN" to the state file will freeze all tasks
    in the cgroup. Subsequently writing "RUNNING" will unfreeze the tasks in
    the cgroup. Reading will return the current state.

    * Examples of usage :

    # mkdir /containers/freezer
    # mount -t cgroup -ofreezer freezer /containers
    # mkdir /containers/0
    # echo $some_pid > /containers/0/tasks

    to get status of the freezer subsystem :

    # cat /containers/0/freezer.state
    RUNNING

    to freeze all tasks in the container :

    # echo FROZEN > /containers/0/freezer.state
    # cat /containers/0/freezer.state
    FREEZING
    # cat /containers/0/freezer.state
    FROZEN

    to unfreeze all tasks in the container :

    # echo RUNNING > /containers/0/freezer.state
    # cat /containers/0/freezer.state
    RUNNING

    This is the basic mechanism which should do the right thing for user space
    task in a simple scenario.

    It's important to note that freezing can be incomplete. In that case we
    return EBUSY. This means that some tasks in the cgroup are busy doing
    something that prevents us from completely freezing the cgroup at this
    time. After EBUSY, the cgroup will remain partially frozen -- reflected
    by freezer.state reporting "FREEZING" when read. The state will remain
    "FREEZING" until one of these things happens:

    1) Userspace cancels the freezing operation by writing "RUNNING" to
    the freezer.state file
    2) Userspace retries the freezing operation by writing "FROZEN" to
    the freezer.state file (writing "FREEZING" is not legal
    and returns EIO)
    3) The tasks that blocked the cgroup from entering the "FROZEN"
    state disappear from the cgroup's set of tasks.

    [akpm@linux-foundation.org: coding-style fixes]
    [akpm@linux-foundation.org: export thaw_process]
    Signed-off-by: Cedric Le Goater
    Signed-off-by: Matt Helsley
    Acked-by: Serge E. Hallyn
    Tested-by: Matt Helsley
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Matt Helsley
     

17 Oct, 2008

1 commit


14 Oct, 2008

3 commits


12 Oct, 2008

2 commits

  • …://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip

    * 'x86-v28-for-linus-phase4-D' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip: (186 commits)
    x86, debug: print more information about unknown CPUs
    x86 setup: handle more than 8 CPU flag words
    x86: cpuid, fix typo
    x86: move transmeta cap read to early_init_transmeta()
    x86: identify_cpu_without_cpuid v2
    x86: extended "flags" to show virtualization HW feature in /proc/cpuinfo
    x86: move VMX MSRs to msr-index.h
    x86: centaur_64.c remove duplicated setting of CONSTANT_TSC
    x86: intel.c put workaround for old cpus together
    x86: let intel 64-bit use intel.c
    x86: make intel_64.c the same as intel.c
    x86: make intel.c have 64-bit support code
    x86: little clean up of intel.c/intel_64.c
    x86: make 64 bit to use amd.c
    x86: make amd_64 have 32 bit code
    x86: make amd.c have 64bit support code
    x86: merge header in amd_64.c
    x86: add srat_detect_node for amd64
    x86: remove duplicated force_mwait
    x86: cpu make amd.c more like amd_64.c v2
    ...

    Linus Torvalds
     
  • * 'for-linus' of git://git.alsa-project.org/alsa-kernel: (258 commits)
    ALSA: hda: VREF powerdown for headphones
    ALSA: hda: STAC_HP_M4
    ALSA: ASoC: Check for machine type in GTA01 machine driver
    ALSA: mtpav - Fix race in probe
    ALSA: usb-audio: dynamic detection of MIDI interfaces in uaxx-quirk
    ALSA: Add a note on dependency of RTC stuff
    ALSA: ASoC: add new param mux to dapm_mux_update_power
    ALSA: Increase components array size
    ALSA: ASoC: Correct inverted Mic PGA Switch control in wm8510 driver
    ALSA: hda: comment typo fix
    ALSA: hda: comment typo fix
    ALSA: hda - Fix PCI SSID for ASROCK K18N78FullHD-hSLI
    ALSA: snd-usb-audio: support for Edirol UA-4FX device
    ALSA: usb - Fix possible Oops at USB-MIDI disconnection
    ALSA: hda - Fix another ALC889A (rev 0x100101)
    ALSA: hda: add more board-specific information for Realtek ALC662 rev1
    ALSA: Correct Vladimir Barinov's e-mail address
    ALSA: cs46xx: Add PCI IDs for TerraTec and Hercules cards
    ALSA: hda: SPDIF stream muting support
    ALSA: hda: appletv support
    ...

    Linus Torvalds
     

09 Sep, 2008

1 commit

  • Right now, there is no notifier that is called on a new cpu, before the new
    cpu begins processing interrupts/softirqs.
    Various kernel function would need that notification, e.g. kvm works around
    by calling smp_call_function_single(), rcu polls cpu_online_map.

    The patch adds a CPU_STARTING notification. It also adds a helper function
    that sends the message to all cpu_chain handlers.

    Tested on x86-64.
    All other archs are untested. Especially on sparc, I'm not sure if I got
    it right.

    Signed-off-by: Manfred Spraul
    Signed-off-by: Ingo Molnar

    Manfred Spraul
     

07 Sep, 2008

2 commits


29 Aug, 2008

1 commit

  • sound/sound_core.c implements soundcore.ko and contains two parts -
    sound_class which is shared by both ALSA and OSS and device
    redirection support for OSS. It's always compiled when any sound
    support is enabled although it's necessary only when OSS (the actual
    one or emulation) is enabled. This is slightly wasteful and as device
    redirection always registers character device region for major 14, it
    prevents alternative implementation.

    This patch introduces a new config SOUND_OSS_CORE which is selected
    iff OSS support is actually necessary and build the OSS core part
    conditionally.

    If OSS is disabled, soundcore merely contains sound_class but leaving
    it that way seems to be the simplest approach as otherwise sound_class
    should be in ALSA core file if OSS is disabled but should be in
    soundcore if OSS is enabled. Also, there's also the user confusion
    factor.

    Signed-off-by: Tejun Heo
    Signed-off-by: Takashi Iwai
    Signed-off-by: Jaroslav Kysela

    Tejun Heo
     

15 Aug, 2008

1 commit