sched: Fix struct autogroup memory leak

Seems I lost a change somewhere, leaking memory.

    sched: fix struct autogroup memory leak

    Add missing change to actually use autogroup_free().

    Signed-off-by: Mike Galbraith <efault@gmx.de>
    Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
    LKML-Reference: <1294222285.8369.2.camel@marge.simson.net>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
msm: camera: Free buffers from frame queue at open

Free all pending frames in frame queue before cam_frame
thread opens frame device to avoid duplication of buffer
free
Little performance improvement for slub memory allocator @franciscofranco
msm: cpufreq: Create cpufreq workqueue for freq changes

Setting frequencies may take unbounded amount of time, use private
workqueues instead of shared system workqueue.

Ondemand governor may post to the kernel workqueue, holds rwsem and
waits. This may cause msm_cpufreq_target to repost frequency change
request to the kernel workqueue waiting on the same rwsem resulting
in watchdog reset.

Change-Id: I34cf264e5f7f2f6aad2d2d2af3e4449233efd7d6
Signed-off-by: Praveen Chidambaram <pchidamb@codeaurora.org>
[PATCH] mm: From CodeAurora
cgroup: fix cpuset permission check
msm: cpufreq: Do not call a cpu transition if selecting the same speed
fs: simple fsync race fix

It is incorrect to test inode dirty bits without participating in the inode
        writeback protocol. Inode writeback sets I_SYNC and clears I_DIRTY_?, then
        writes out the particular bits, then clears I_SYNC when it is done. BTW. it
        may not completely write all pages out, so I_DIRTY_PAGES would get set
        again.

        This is a standard pattern used throughout the kernel's writeback caches
        (I_SYNC ~= I_WRITEBACK, if that makes it clearer).

        And so it is not possible to determine an inode's dirty status just by
        checking I_DIRTY bits. Especially not for the purpose of data integrity
        syncs.

        Missing the check for these bits means that fsync can complete while
        writeback to the inode is underway. Inode writeback functions get this
        right, so call into them rather than try to shortcut things by testing
        dirty state improperly.

        Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Erase memory pages as soon as they are freed to prevent new processes getting old information (franciscofranco)
msm: audio: qdsp5: Handle EOS buffer after audio flush

EOS buffer is not getting processed in following scenario is
encountered:
-Driver Recieves FLUSH command from apps
-Application sends EOS buffer to the driver after flush
command has completed
-NEEDS_DATA messages from DSP is Recieved by driver

In above scenario driver blocks for forever in write wait queue
and EOS buffer never gets processed.

Fix this by sending wakeup when NEEDS_DATA message is received.

CRs-Fixed: 292954, 293145
Signed-off-by: Manish Dewangan <manish@codeaurora.org>
(cherry picked from commit c729e63e1adc0b1e3b542477731e3485574150cd)

Change-Id: Iba4f7850e546d3816c31389a33984af28cca6503
Signed-off-by: Sunil Joseph <sunilj@codeaurora.org>