GitHub PushEvent at 2014-02-08 14:58:59
Repository: linux-sunxi
Actor: amery
Payload: {"shas":[["7aee29d6482954ac9fecae3ce8a90b6759158107","1a2f18c7887fc8d384193bb926e616097dea5b69@google.com","android: configs: add TIMER_STATS back, helps with sysrq t.\n\nChange-Id: I8fe033090e38523152225dcfb7a1828f530a0757\nSigned-off-by: JP Abgrall <jpa@google.com>","JP Abgrall",false],["4a7cebd91f796fcb9d1e1e5723de27b75f1712d6","168fbe9b48536378ad61dccedb637b5a226976e8@linux.org.tw","cpufreq: interactive: fix compiling warnings\n\nThe gcc warns like:\n\n  cpufreq_interactive.c:745:6: warning: operation on 'ret' may be\nundefined [-Wsequence-point]\n\nIt was introduced by commit cf0fad49d17cb8273ce555dd5b7afab67d7923bf.\n\nSince sprintf(...) just return 1 (one character) in this case, ret\nshould not changed.\nJust discarding the result of sprintf(...) leads to the result that\nthe committer of cf0fad49d17cb8273ce555dd5b7afab67d7923bf wants.\n\nChange-Id: Ifed1cef6d6a31c3ed23dad03a567b3b9eddf3a57\nSigned-off-by: Chih-Wei Huang <cwhuang@android-x86.org>\nSigned-off-by: Dave Daynard <nardholio@gmail.com>","Chih-Wei Huang",false],["5e35d662616142d308ce24c9d552e469f60d8695","1a2f18c7887fc8d384193bb926e616097dea5b69@google.com","android: configs: add IPV6 ROUTE INFO\n\nChange-Id: I54cba86bce703647c4be8eee5592d55374ad02ef\nSigned-off-by: JP Abgrall <jpa@google.com>","JP Abgrall",false],["bc845e5405b033fadd398c5ca2884a568313c875","6a430eed381e126d51a8cce8db662f765ce314bc@gmail.com","USB: serial: fix race in generic write\n\ncommit 6f6485463aada1ec6a0f3db6a03eb8e393d6bb55 upstream.\n\nFix race in generic write implementation, which could lead to\ntemporarily degraded throughput.\n\nThe current generic write implementation introduced by commit\n27c7acf22047 (\"USB: serial: reimplement generic fifo-based writes\") has\nalways had this bug, although it's fairly hard to trigger and the\nconsequences are not likely to be noticed.\n\nSpecifically, a write() on one CPU while the completion handler is\nrunning on another could result in only one of the two write urbs being\nutilised to empty the remainder of the write fifo (unless there is a\nsecond write() that doesn't race during that time).\n\nSigned-off-by: Johan Hovold <jhovold@gmail.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Johan Hovold",true],["1461d4c794c2f98ebdd9d60f47a08c09dc4ce453","45e2ee8c8b09e76a9d512320d4eb53c0cd9925c0@intel.com","ceph: cleanup aborted requests when re-sending requests.\n\ncommit eb1b8af33c2e42a9a57fc0a7588f4a7b255d2e79 upstream.\n\nAborted requests usually get cleared when the reply is received.\nIf MDS crashes, no reply will be received. So we need to cleanup\naborted requests when re-sending requests.\n\nSigned-off-by: Yan, Zheng <zheng.z.yan@intel.com>\nReviewed-by: Greg Farnum <greg@inktank.com>\nSigned-off-by: Sage Weil <sage@inktank.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Yan, Zheng",true],["bb4e90afb0b16996ff921762ab4212db0f40535f","45e2ee8c8b09e76a9d512320d4eb53c0cd9925c0@intel.com","ceph: wake up 'safe' waiters when unregistering request\n\ncommit fc55d2c9448b34218ca58733a6f51fbede09575b upstream.\n\nWe also need to wake up 'safe' waiters if error occurs or request\naborted. Otherwise sync(2)/fsync(2) may hang forever.\n\nSigned-off-by: Yan, Zheng <zheng.z.yan@intel.com>\nSigned-off-by: Sage Weil <sage@inktank.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Yan, Zheng",true],["7898047084bed6716bbc2c08b969ddf364ca36fd","65ea93bc1ff7771dbd0685191aef504122ef52de@gmail.com","powerpc: kvm: fix rare but potential deadlock scene\n\ncommit 91648ec09c1ef69c4d840ab6dab391bfb452d554 upstream.\n\nSince kvmppc_hv_find_lock_hpte() is called from both virtmode and\nrealmode, so it can trigger the deadlock.\n\nSuppose the following scene:\n\nTwo physical cpuM, cpuN, two VM instances A, B, each VM has a group of\nvcpus.\n\nIf on cpuM, vcpu_A_1 holds bitlock X (HPTE_V_HVLOCK), then is switched\nout, and on cpuN, vcpu_A_2 try to lock X in realmode, then cpuN will be\ncaught in realmode for a long time.\n\nWhat makes things even worse if the following happens,\n  On cpuM, bitlockX is hold, on cpuN, Y is hold.\n  vcpu_B_2 try to lock Y on cpuM in realmode\n  vcpu_A_2 try to lock X on cpuN in realmode\n\nOops! deadlock happens\n\nSigned-off-by: Liu Ping Fan <pingfank@linux.vnet.ibm.com>\nReviewed-by: Paul Mackerras <paulus@samba.org>\nSigned-off-by: Alexander Graf <agraf@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","pingfan liu",true],["34ee0e8ad09ec1e58858bd3c8756a31a2b3c46bf","0da414d9d963da4039c2a0525b1844228075aa58@linux-m68k.org","TTY: pmac_zilog, check existence of ports in pmz_console_init()\n\ncommit dc1dc2f8a5dd863bf2e79f338fc3ae29e99c683a upstream.\n\nWhen booting a multi-platform m68k kernel on a non-Mac with \"console=ttyS0\"\non the kernel command line, it crashes with:\n\nUnable to handle kernel NULL pointer dereference at virtual address   (null)\nOops: 00000000\nPC: [<0013ad28>] __pmz_startup+0x32/0x2a0\n...\nCall Trace: [<002c5d3e>] pmz_console_setup+0x64/0xe4\n\nThe normal tty driver doesn't crash, because init_pmz() checks\npmz_ports_count again after calling pmz_probe().\n\nIn the serial console initialization path, pmz_console_init() doesn't do\nthis, causing the driver to crash later.\n\nAdd a check for pmz_ports_count to fix this.\n\nSigned-off-by: Geert Uytterhoeven <geert@linux-m68k.org>\nCc: Finn Thain <fthain@telegraphics.com.au>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Geert Uytterhoeven",true],["a183811472052b849d74d4fb2674265c6f874610","b3e6a3251704a94eee1cf08e0adc382e6cb535ee@atmel.com","ASoC: wm8904: fix DSP mode B configuration\n\ncommit f0199bc5e3a3ec13f9bc938556517ec430b36437 upstream.\n\nWhen wm8904 work in DSP mode B, we still need to configure it to\nwork in DSP mode. Or else, it will work in Right Justified mode.\n\nSigned-off-by: Bo Shen <voice.shen@atmel.com>\nAcked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>\nSigned-off-by: Mark Brown <broonie@linaro.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Bo Shen",true],["b86d86822526d0be85d41cca71242fba6ac3c2c7","e8d02934b600b49f55a6a87791b5e863e039320e@gmail.com","ALSA: Add SNDRV_PCM_STATE_PAUSED case in wait_for_avail function\n\ncommit ed697e1aaf7237b1a62af39f64463b05c262808d upstream.\n\nWhen the process is sleeping at the SNDRV_PCM_STATE_PAUSED\nstate from the wait_for_avail function, the sleep process will be woken by\ntimeout(10 seconds). Even if the sleep process wake up by timeout, by this\npatch, the process will continue with sleep and wait for the other state.\n\nSigned-off-by: JongHo Kim <furmuwon@gmail.com>\nSigned-off-by: Takashi Iwai <tiwai@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","JongHo Kim",true],["bc8a3912facbd66e2b88d10922aae74548b86606","8a2957e0063f2abf61bd145b6236a74a3708ac54@mork.no","usb: cdc-wdm: manage_power should always set needs_remote_wakeup\n\ncommit 4144bc861ed7934d56f16d2acd808d44af0fcc90 upstream.\n\nReported-by: Oliver Neukum <oneukum@suse.de>\nSigned-off-by: Bjørn Mork <bjorn@mork.no>\nAcked-by: Oliver Neukum <oneukum@suse.de>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Bjørn Mork",true],["351381d8cea3036cfe021eb29994584d0e5c0e73","72af4739cc81e1db6b65aae97d2a23b3b40af31c@trustedcs.com","selinux: fix broken peer recv check\n\ncommit 46d01d63221c3508421dd72ff9c879f61053cffc upstream.\n\nFix a broken networking check. Return an error if peer recv fails.  If\nsecmark is active and the packet recv succeeds the peer recv error is\nignored.\n\nSigned-off-by: Chad Hanson <chanson@trustedcs.com>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Chad Hanson",true],["58c2314ac41e8f24a2a594bd866915e38de9648e","20b70f0af00562e63758b9ee42012ecc96c58590@redhat.com","selinux: selinux_setprocattr()->ptrace_parent() needs rcu_read_lock()\n\ncommit c0c1439541f5305b57a83d599af32b74182933fe upstream.\n\nselinux_setprocattr() does ptrace_parent(p) under task_lock(p),\nbut task_struct->alloc_lock doesn't pin ->parent or ->ptrace,\nthis looks confusing and triggers the \"suspicious RCU usage\"\nwarning because ptrace_parent() does rcu_dereference_check().\n\nAnd in theory this is wrong, spin_lock()->preempt_disable()\ndoesn't necessarily imply rcu_read_lock() we need to access\nthe ->parent.\n\nReported-by: Evan McNabb <emcnabb@redhat.com>\nSigned-off-by: Oleg Nesterov <oleg@redhat.com>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Oleg Nesterov",true],["09951c9b33f8cfdc0e8c4e03fe83bc66c9d908dc","d7fac3f7b328449401fe64671e732ac315caee28@cn.fujitsu.com","ftrace: Initialize the ftrace profiler for each possible cpu\n\ncommit c4602c1c818bd6626178d6d3fcc152d9f2f48ac0 upstream.\n\nFtrace currently initializes only the online CPUs. This implementation has\ntwo problems:\n- If we online a CPU after we enable the function profile, and then run the\n  test, we will lose the trace information on that CPU.\n  Steps to reproduce:\n  # echo 0 > /sys/devices/system/cpu/cpu1/online\n  # cd <debugfs>/tracing/\n  # echo <some function name> >> set_ftrace_filter\n  # echo 1 > function_profile_enabled\n  # echo 1 > /sys/devices/system/cpu/cpu1/online\n  # run test\n- If we offline a CPU before we enable the function profile, we will not clear\n  the trace information when we enable the function profile. It will trouble\n  the users.\n  Steps to reproduce:\n  # cd <debugfs>/tracing/\n  # echo <some function name> >> set_ftrace_filter\n  # echo 1 > function_profile_enabled\n  # run test\n  # cat trace_stat/function*\n  # echo 0 > /sys/devices/system/cpu/cpu1/online\n  # echo 0 > function_profile_enabled\n  # echo 1 > function_profile_enabled\n  # cat trace_stat/function*\n  # run test\n  # cat trace_stat/function*\n\nSo it is better that we initialize the ftrace profiler for each possible cpu\nevery time we enable the function profile instead of just the online ones.\n\nLink: http://lkml.kernel.org/r/1387178401-10619-1-git-send-email-miaox@cn.fujitsu.com\n\nSigned-off-by: Miao Xie <miaox@cn.fujitsu.com>\nSigned-off-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Miao Xie",true],["5806153a870c8b6557423e495f6d79ac9ec87197","b060cfa1096cc6e8be83699ddb4ed8a77dd63af5@intel.com","intel_idle: initial IVB support\n\ncommit 6edab08c24f9141d69cfa4683a0a027d86ab303e upstream.\n\nFrom an OS point of view, IVB looks like SNB, but quicker.\n\nSigned-off-by: Len Brown <len.brown@intel.com>\nCc: Vinson Lee <vlee@twopensource.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Len Brown",true],["3be19dd5258a26cfe1d90a22132784c2ba836039","b060cfa1096cc6e8be83699ddb4ed8a77dd63af5@intel.com","intel_idle: enable IVB Xeon support\n\ncommit 23795e580cad5d6b73d47d51b9074ce3e58bf334 upstream.\n\nIVB Xeon currently shares the same parameters IVB client.\n\nSigned-off-by: Len Brown <len.brown@intel.com>\nCc: Vinson Lee <vlee@twopensource.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Len Brown",true],["510e024d1e74bb0f574d14ee19436a56ed4fc476","1fde277d5e7954dd5d21f78698dcf3bf02313493@google.com","ext4: fix use-after-free in ext4_mb_new_blocks\n\ncommit 4e8d2139802ce4f41936a687f06c560b12115247 upstream.\n\next4_mb_put_pa should hold pa->pa_lock before accessing pa->pa_count.\nWhile ext4_mb_use_preallocated checks pa->pa_deleted first and then\nincrements pa->count later, ext4_mb_put_pa decrements pa->pa_count\nbefore holding pa->pa_lock and then sets pa->pa_deleted.\n\n* Free sequence\next4_mb_put_pa (1):\t\tatomic_dec_and_test pa->pa_count\next4_mb_put_pa (2):\t\tlock pa->pa_lock\next4_mb_put_pa (3):\t\t\tcheck pa->pa_deleted\next4_mb_put_pa (4):\t\t\tset pa->pa_deleted=1\next4_mb_put_pa (5):\t\tunlock pa->pa_lock\next4_mb_put_pa (6):\t\tremove pa from a list\next4_mb_pa_callback:\t\tfree pa\n\n* Use sequence\next4_mb_use_preallocated (1):\titerate over preallocation\next4_mb_use_preallocated (2):\tlock pa->pa_lock\next4_mb_use_preallocated (3):\t\tcheck pa->pa_deleted\next4_mb_use_preallocated (4):\t\tincrease pa->pa_count\next4_mb_use_preallocated (5):\tunlock pa->pa_lock\next4_mb_release_context:\taccess pa\n\n* Use-after-free sequence\n[initial status]\t\t<pa->pa_deleted = 0, pa_count = 1>\next4_mb_use_preallocated (1):\titerate over preallocation\next4_mb_use_preallocated (2):\tlock pa->pa_lock\next4_mb_use_preallocated (3):\t\tcheck pa->pa_deleted\next4_mb_put_pa (1):\t\tatomic_dec_and_test pa->pa_count\n[pa_count decremented]\t\t<pa->pa_deleted = 0, pa_count = 0>\next4_mb_use_preallocated (4):\t\tincrease pa->pa_count\n[pa_count incremented]\t\t<pa->pa_deleted = 0, pa_count = 1>\next4_mb_use_preallocated (5):\tunlock pa->pa_lock\next4_mb_put_pa (2):\t\tlock pa->pa_lock\next4_mb_put_pa (3):\t\t\tcheck pa->pa_deleted\next4_mb_put_pa (4):\t\t\tset pa->pa_deleted=1\n[race condition!]\t\t<pa->pa_deleted = 1, pa_count = 1>\next4_mb_put_pa (5):\t\tunlock pa->pa_lock\next4_mb_put_pa (6):\t\tremove pa from a list\next4_mb_pa_callback:\t\tfree pa\next4_mb_release_context:\taccess pa\n\nAddressSanitizer has detected use-after-free in ext4_mb_new_blocks\nBug report: http://goo.gl/rG1On3\n\nSigned-off-by: Junho Ryu <jayr@google.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Junho Ryu",true],["a1192c0e5d037def6763f3873d3340615c241fe7","45077a34947a1ae82e6576c6adeb38fe04811905@gmail.com","ext4: check for overlapping extents in ext4_valid_extent_entries()\n\ncommit 5946d089379a35dda0e531710b48fca05446a196 upstream.\n\nA corrupted ext4 may have out of order leaf extents, i.e.\n\nextent: lblk 0--1023, len 1024, pblk 9217, flags: LEAF UNINIT\nextent: lblk 1000--2047, len 1024, pblk 10241, flags: LEAF UNINIT\n             ^^^^ overlap with previous extent\n\nReading such extent could hit BUG_ON() in ext4_es_cache_extent().\n\n\tBUG_ON(end < lblk);\n\nThe problem is that __read_extent_tree_block() tries to cache holes as\nwell but assumes 'lblk' is greater than 'prev' and passes underflowed\nlength to ext4_es_cache_extent(). Fix it by checking for overlapping\nextents in ext4_valid_extent_entries().\n\nI hit this when fuzz testing ext4, and am able to reproduce it by\nmodifying the on-disk extent by hand.\n\nAlso add the check for (ee_block + len - 1) in ext4_valid_extent() to\nmake sure the value is not overflow.\n\nRan xfstests on patched ext4 and no regression.\n\nCc: Lukáš Czerner <lczerner@redhat.com>\nSigned-off-by: Eryu Guan <guaneryu@gmail.com>\nSigned-off-by: \"Theodore Ts'o\" <tytso@mit.edu>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Eryu Guan",true],["3f8878956c833443d6c6e498e9ed6a18ee30e0f5","f0a29e10abf52e3965939db20f961ffd5c7f3d14@yandex.ru","sched/rt: Fix rq's cpupri leak while enqueue/dequeue child RT entities\n\ncommit 757dfcaa41844595964f1220f1d33182dae49976 upstream.\n\nThis patch touches the RT group scheduling case.\n\nFunctions inc_rt_prio_smp() and dec_rt_prio_smp() change (global) rq's\npriority, while rt_rq passed to them may be not the top-level rt_rq.\nThis is wrong, because changing of priority on a child level does not\nguarantee that the priority is the highest all over the rq. So, this\nleak makes RT balancing unusable.\n\nThe short example: the task having the highest priority among all rq's\nRT tasks (no one other task has the same priority) are waking on a\nthrottle rt_rq.  The rq's cpupri is set to the task's priority\nequivalent, but real rq->rt.highest_prio.curr is less.\n\nThe patch below fixes the problem.\n\nSigned-off-by: Kirill Tkhai <tkhai@yandex.ru>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nCC: Steven Rostedt <rostedt@goodmis.org>\nLink: http://lkml.kernel.org/r/49231385567953@web4m.yandex.ru\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Kirill Tkhai",true],["b266405d3fb1b41af54c762247da92cf9083d98e","dced371c11179e2cb83b1e305b9d7b15f379452b@gmail.com","drm/edid: add quirk for BPC in Samsung NP700G7A-S01PL notebook\n\ncommit 49d45a31b71d7d9da74485922bdb63faf3dc9684 upstream.\n\nThis bug in EDID was exposed by:\n\ncommit eccea7920cfb009c2fa40e9ecdce8c36f61cab66\nAuthor: Alex Deucher <alexander.deucher@amd.com>\nDate:   Mon Mar 26 15:12:54 2012 -0400\n\n    drm/radeon/kms: improve bpc handling (v2)\n\nWhich resulted in kind of regression in 3.5. This fixes\nhttps://bugs.freedesktop.org/show_bug.cgi?id=70934\n\nSigned-off-by: Rafał Miłecki <zajec5@gmail.com>\nSigned-off-by: Dave Airlie <airlied@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","Rafał Miłecki",true]],"size":130,"ref":"refs/heads/sunxi-3.4","head":"0c92978520e9576a0631da949c13e79bae846494"}