(2015/01/15 0:39), Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> As the set_ftrace_filter affects both the function tracer as well as the
> function graph tracer, the ops that represent each have a shared
> ftrace_ops_hash structure. This allows both to be updated when the filter
>
On Thu, Jan 15, 2015 at 01:55:52AM +0100, Daniel Vetter wrote:
> On Wed, Jan 14, 2015 at 08:34:31PM +, Chris Wilson wrote:
> > This (partially) reverts
> >
> > commit 5537252b6b6d71fb1a8ed7395a8e5babf91953fd
> > Author: Chris Wilson
> > Date: Tue Mar 25 13:23:06 2014 +
> >
> > drm/i9
I'm announcing the release of the 3.12.36 kernel.
All users of the 3.12 kernel series must upgrade.
The updated 3.12.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.12.y
and can be browsed at the normal kernel.org git web browser:
On Tue, Jan 13, 2015 at 07:33:57PM +, Luis Henriques wrote:
> On Mon, Jan 12, 2015 at 06:03:12PM +, Luis Henriques wrote:
> > 3.16.7-ckt4 -stable review patch. If anyone has any objections, please let
> > me know.
> >
>
> Hi Daniel and Chris,
>
> Thomas Voegtle (on Cc:) reported a regre
Commit 7232398abc6a ("ARM: tegra: Convert PMC to a driver") changed
tegra_resume()
location storing from late to early and, as a result, broke suspend on Tegra20.
PMC scratch register 41 is used by tegra LP1 resume code for retrieving stored
physical memory address of common resume function and in
Commit 7232398abc6a ("ARM: tegra: Convert PMC to a driver") changed
tegra_resume()
location storing from late to early and, as a result, broke suspend on Tegra20.
PMC scratch register 41 is used by tegra LP1 resume code for retrieving stored
physical memory address of common resume function and in
Hi, this is third attempt to fix Tegra20 suspend bug. First was to use other
PMC scratch register for tegra_resume() address store and second to use syscore
ops for PMC driver.
Thierry Reding proposed other solution: to use IRAM instead of PMC scratch
register. I prepared two implementation varian
Commit 7232398abc6a ("ARM: tegra: Convert PMC to a driver") changed
tegra_resume()
location storing from late to early and, as a result, broke suspend on Tegra20.
PMC scratch register 41 is used by tegra LP1 resume code for retrieving stored
physical memory address of common resume function and in
Commit 7232398abc6a ("ARM: tegra: Convert PMC to a driver") changed
tegra_resume()
location storing from late to early and, as a result, broke suspend on Tegra20.
PMC scratch register 41 is used by tegra LP1 resume code for retrieving stored
physical memory address of common resume function and in
On Mon, Jan 12, 2015 at 06:09:33PM +, Stefano Stabellini wrote:
> Hi all,
> I would like to request a backport of the following commit:
>
>
> commit a4dba130891271084344c12537731542ec77cb85
> Author: Stefano Stabellini
> Date: Fri Nov 21 11:07:39 2014 +
>
> xen/arm/arm64: introduc
From: Sasha Levin
From: Sasha Levin
commit a3a8784454692dd72e5d5d34dcdab17b4420e74c upstream
When a key is being garbage collected, it's key->user would get put before
the ->destroy() callback is called, where the key is removed from it's
respective tracking structures.
This leaves a key hang
On Tue, Jan 13, 2015 at 12:47:59PM +, Zhiqiang Zhang wrote:
> From:Jiri Olsa
>
> commit f61ff6c06dc8f32c7036013ad802c899ec590607 upstream
>
Thank you, I'll queue this for the 3.16 kernel as well.
Cheers,
--
Luís
> Linus reported perf report command being interrupted due to processing
> of
On Wed, Jan 14, 2015 at 11:15:25AM +0100, Jan Kara wrote:
> Hello,
>
> can you guys please push commit 6424babfd68dd (fsnotify: next_i is freed
> during fsnotify_unmount_inodes) to stable trees? It fixes occasional hangs
> / softlockups (due to use after free issues) when unmounting a filesyst
(2015/01/15 0:40), Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Using just the filter for checking for trampolines or regs is not enough
> when updating the code against the records that represent all functions.
> Both the filter hash and the notrace hash need to be checked.
>
>
Hi Steven,
Thank you for fixing this bug!
(2015/01/15 0:40), Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> If the function graph tracer traces a jprobe callback, the system will
> crash. This can easily be demonstrated by compiling the jprobe
> sample module that is in the kernel
From: Linus Lüssing
[ upstream commit f0b4eeced518c632210ef2aea44fc92cc9e86cce ]
Ebtables on the OUTPUT chain (NF_BR_LOCAL_OUT) would not work as expected
for both locally generated IGMP and MLD queries. The IP header specific
filter options are off by 14 Bytes for netfilter (actual output on
in
From: Dan Carpenter
[ upstream commit 2196937e12b1b4ba139806d132647e1651d655df ]
We could be reading 8 bytes into a 4 byte buffer here. It seems
harmless but adding a check is the right thing to do and it silences a
static checker warning.
Cc: # 3.2.x
Cc: # 3.4.x
Cc: # 3.10.x
Cc: # 3.12.x
From: David Hildenbrand
Patch 0759d0681cae ("KVM: s390: cleanup handle_wait by reusing
kvm_vcpu_block") changed the way pending guest clock comparator
interrupts are detected. It was assumed that as soon as the hrtimer
wakes up, the condition for the guest ckc is satisfied.
This is however only
From: David Hildenbrand
The hrtimer that handles the wait with enabled timer interrupts
should not be disturbed by changes of the host time.
This patch changes our hrtimer to be based on a monotonic clock.
Signed-off-by: David Hildenbrand
Acked-by: Cornelia Huck
Cc: stable@vger.kernel.org
Sig
Hi,
On Thu, Jan 15, 2015 at 05:00:37AM +0300, Dmitry Eremin-Solenikov wrote:
> enable_irq_wakeup returns 0 in case it correctly enabled the IRQ to
> generate the wakeup event (and thus resume should call disable_irq_wake).
> Currently gpio-charger driver has this logic inverted. Correct that thus
On Thu, 15 Jan 2015 19:59:36 +0900
Masami Hiramatsu wrote:
> > @@ -3637,6 +3639,7 @@ int
> > register_ftrace_function_probe(char *glob, struct ftrace_probe_ops
> > *ops, void *data)
> > {
> > + struct ftrace_ops_hash old_hash_ops;
>
> Would it be better to be old_ops_hash? since it's not an
On Thu, 15 Jan 2015 20:57:29 +0900
Masami Hiramatsu wrote:
>
> > If the function tracer traces the jprobe handler, the hook function
> > for that handler will not be called, and its saved return address
> > will be used for the next function. This will result in a kernel
> > crash.
>
> Actually,
Simon Wunderlich writes:
>> I did not dig how the hw->conf.radar_enabled flag is set in monitor mode,
>> but if it is same as for master (i.e. set for DFS channels), then it would
>> be a better approach to prevent calling ath9k_dfs_process_phyerr()
>> altogether from ath9k_rx_skb_preprocess() if
From: "Steven Rostedt (Red Hat)"
As the set_ftrace_filter affects both the function tracer as well as the
function graph tracer, the ops that represent each have a shared
ftrace_ops_hash structure. This allows both to be updated when the filter
files are updated.
But if function graph is enabled
From: "Steven Rostedt (Red Hat)"
If the function graph tracer traces a jprobe callback, the system will
crash. This can easily be demonstrated by compiling the jprobe
sample module that is in the kernel tree, loading it and running the
function graph tracer.
# modprobe jprobe_example.ko
# echo
From: "Steven Rostedt (Red Hat)"
Using just the filter for checking for trampolines or regs is not enough
when updating the code against the records that represent all functions.
Both the filter hash and the notrace hash need to be checked.
To trigger this bug (using trace-cmd and perf):
# per
Hey Kalle,
On Thursday 15 January 2015 16:30:51 Kalle Valo wrote:
> Simon Wunderlich writes:
> >> I did not dig how the hw->conf.radar_enabled flag is set in monitor mode,
> >> but if it is same as for master (i.e. set for DFS channels), then it
> >> would
> >> be a better approach to prevent cal
This was accidently lost in 76a0df859def.
Signed-off-by: Alex Deucher
Cc: stable@vger.kernel.org
---
drivers/gpu/drm/radeon/radeon_asic.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_asic.c
b/drivers/gpu/drm/radeon/radeon_
From: "Ahmed S. Darwish"
Flooding the Kvaser CAN to USB dongle with multiple reads and
writes in high frequency caused seemingly-random panics in the
kernel.
On further inspection, it seems the driver erroneously freed the
to-be-transmitted packet upon getting tight on URBs and returning
NETDEV_
From: Oliver Hartkopp
When changing flags in the CAN drivers ctrlmode the provided new content has to
be checked whether the bits are allowed to be changed. The bits that are to be
changed are given as a bitfield in cm->mask. Therefore checking against
cm->flags is wrong as the content can hold a
From: "Ahmed S. Darwish"
Recent Leaf firmware versions (>= 3.1.557) do not allow to send
commands for non-existing channels. If a command is sent for a
non-existing channel, the firmware crashes.
Reported-by: Christopher Storah
Signed-off-by: Olivier Sobrie
Signed-off-by: Ahmed S. Darwish
Cc
From: "Ahmed S. Darwish"
Flooding the Kvaser CAN to USB dongle with multiple reads and
writes in very high frequency (*), closing the CAN channel while
all the transmissions are on (#), opening the device again (@),
then sending a small number of packets would make the driver
enter an almost infi
From: Oliver Hartkopp
During the CAN FD standardization process within the ISO it turned out that
the failure detection capability has to be improved.
The CAN in Automation organization (CiA) defined the already implemented CAN
FD controllers as 'non-ISO' and the upcoming improved CAN FD control
this was very wrong - mempool_alloc() only guarantees success with GFP_WAIT.
bcache uses GFP_NOWAIT in various other places where we have a fallback,
circuits must've gotten crossed when writing this code or something.
Signed-off-by: Kent Overstreet
---
The bug was introduced in v3.11, fixed in
Oh, here's the commit id: bcf090e0040e30f8409e6a535a01e6473afb096f
Le 15/01/2015 17:26, Gabriel de Perthuis a écrit :
this was very wrong - mempool_alloc() only guarantees success with
GFP_WAIT.
bcache uses GFP_NOWAIT in various other places where we have a fallback,
circuits must've gotten cros
The commit 3b8a3c010969 ("powerpc/pseries: Fix endiannes issue in RTAS
call from xmon") was fixing an endianness issue in the call made from
xmon to RTAS.
However, as Michael Ellerman noticed, this fix was not complete, the
token value was not byte swapped. This lead to call an unexpected and
most
On Thu, Jan 15, 2015 at 05:26:37PM +0100, Gabriel de Perthuis wrote:
> this was very wrong - mempool_alloc() only guarantees success with GFP_WAIT.
> bcache uses GFP_NOWAIT in various other places where we have a fallback,
> circuits must've gotten crossed when writing this code or something.
>
>
Philipp Zabel writes:
> Hi,
>
> Am Montag, den 12.01.2015, 14:13 -0800 schrieb Olof Johansson:
>> On Mon, Jan 12, 2015 at 05:17:06PM +0100, Maxime Ripard wrote:
>> > On Mon, Jan 12, 2015 at 07:54:46AM -0800, Tyler Baker wrote:
>> > > Call spin_lock_init() before the spinlocks are used, both in ea
Hi,
no objections of course,
actually it was written and tested with 3.14 in mind.
On Thu, Jan 15, 2015 at 12:45 AM, Miquel van Smoorenburg
wrote:
> [first sent to lkml, now to netdev and the original patch author]
>
> When running 'lxc' on the latest -stable kernel, 3.14.28, I'm seeing these
>
From: Hemmo Nieminen
As printk() invocation can cause e.g. a TLB miss, printk() cannot be
called before the exception handlers have been properly initialized.
This can happen e.g. when netconsole has been loaded as a kernel module
and the TLB table has been cleared when a CPU was offline.
Call c
octeon_cpu_disable() will unconditionally enable interrupts when called
with interrupts disabled. Fix that.
The patch fixes the following crash when offlining a CPU:
[ 93.818785] [ cut here ]
[ 93.823421] WARNING: CPU: 1 PID: 10 at kernel/smp.c:231
flush_smp_call_func
On 01/15/2015 10:49 AM, Aaro Koskinen wrote:
octeon_cpu_disable() will unconditionally enable interrupts when called
with interrupts disabled. Fix that.
interrupts are always disabled here, so...
[...]
Reported-by: Hemmo Nieminen
Signed-off-by: Aaro Koskinen
Cc: stable@vger.kernel.org
NA
On Wed, Jan 14, 2015 at 9:34 PM, Chris Wilson wrote:
> This (partially) reverts
>
> commit 5537252b6b6d71fb1a8ed7395a8e5babf91953fd
> Author: Chris Wilson
> Date: Tue Mar 25 13:23:06 2014 +
>
> drm/i915: Invalidate our pages under memory pressure
Shouldn't we also revert the hunk in i9
On 01/15/2015 09:23 AM, Laurent Dufour wrote:
> The commit 3b8a3c010969 ("powerpc/pseries: Fix endiannes issue in RTAS
> call from xmon") was fixing an endianness issue in the call made from
> xmon to RTAS.
>
> However, as Michael Ellerman noticed, this fix was not complete, the
> token value was
Hi,
On Thu, Jan 15, 2015 at 11:36:12AM -0800, David Daney wrote:
> On 01/15/2015 10:49 AM, Aaro Koskinen wrote:
> >octeon_cpu_disable() will unconditionally enable interrupts when called
> >with interrupts disabled. Fix that.
>
> interrupts are always disabled here, so...
Is that also true for a
On 01/15/2015 11:53 AM, Aaro Koskinen wrote:
Hi,
On Thu, Jan 15, 2015 at 11:36:12AM -0800, David Daney wrote:
On 01/15/2015 10:49 AM, Aaro Koskinen wrote:
octeon_cpu_disable() will unconditionally enable interrupts when called
with interrupts disabled. Fix that.
interrupts are always disable
Hello,
Please consider including mainline commit c12f07d and bd9b2f9 in the
next v3.16.y-ckt release. They
were included in the mainline tree as of v3.17-rc1. A test kernel has
been built and tested, which was confirmed to resolve:
http://bugs.launchpad.net/bugs/1406767 .
commit c12f07d17c12193
Hi,
On Thu, Jan 15, 2015 at 12:10:08PM -0800, David Daney wrote:
> On 01/15/2015 11:53 AM, Aaro Koskinen wrote:
> >Hi,
> >
> >On Thu, Jan 15, 2015 at 11:36:12AM -0800, David Daney wrote:
> >>On 01/15/2015 10:49 AM, Aaro Koskinen wrote:
> >>>octeon_cpu_disable() will unconditionally enable interrup
On Thu, Jan 15, 2015 at 08:36:15PM +0100, Daniel Vetter wrote:
> On Wed, Jan 14, 2015 at 9:34 PM, Chris Wilson
> wrote:
> > This (partially) reverts
> >
> > commit 5537252b6b6d71fb1a8ed7395a8e5babf91953fd
> > Author: Chris Wilson
> > Date: Tue Mar 25 13:23:06 2014 +
> >
> > drm/i915: I
From: Hemmo Nieminen
As printk() invocation can cause e.g. a TLB miss, printk() cannot be
called before the exception handlers have been properly initialized.
This can happen e.g. when netconsole has been loaded as a kernel module
and the TLB table has been cleared when a CPU was offline.
Call c
octeon_cpu_disable() will unconditionally enable interrupts when called.
We can assume that the routine is always called with interrupts disabled,
so just delete the incorrect local_irq_disable/enable().
The patch fixes the following crash when offlining a CPU:
[ 93.818785] [ cut he
God dag,
Jeg er Rose Butler, den udøvende agent på et generelt anerkendt legitimt
långivende selskab kaldet YesGrowth Lån, der ligger i Det Forenede Kongerige.
Vi låner penge til enkeltpersoner og virksomheder, der har brug finansiel
bistand. Har du har en dårlig kredit, eller du har brug fo
Reduce the attack vector and stop generating IPv6 Fragment Header for
paths with an MTU smaller than the minimum required IPv6 MTU
size (1280 byte) - called atomic fragments.
See IETF I-D "Deprecating the Generation of IPv6 Atomic Fragments" [1]
for more information and how this "feature" can be m
The patch titled
Subject: axonram: fix bug in direct_access
has been removed from the -mm tree. Its filename was
axonram-fix-bug-in-direct_access.patch
This patch was dropped because it was merged into mainline or a subsystem tree
--
This is the start of the review cycle for the Linux 3.13.11-ckt14 stable kernel.
This version contains 19 new patches, summarized below. The new patches are
posted as replies to this message and also available in this git branch:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=linux-3.13.y-rev
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Jan Kara
commit 4e2024624e678f0ebb916e6192bd23c1f9fdf696 upstream.
We didn't check length of rock ridge ER records before printing them.
Thus corrupted isofs image can cause us to a
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Andy Lutomirski
commit 41bdc78544b8a93a9c6814b8bbbfef966272abbe upstream.
Installing a 16-bit RW data segment into the GDT defeats espfix.
AFAICT this will not affect glibc, Wine, o
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: "Eric W. Biederman"
commit be7c6dba2332cef0677fbabb606e279ae76652c3 upstream.
As any gid mapping will allow and must allow for backwards
compatibility dropping groups don't allow an
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Al Viro
commit 946e51f2bf37f1656916eb75bd0742ba33983c28 upstream.
Signed-off-by: Al Viro
[bwh: Backported to 3.16:
- Apply name changes in all the different places we use d_alias
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: "Eric W. Biederman"
commit 80dd00a23784b384ccea049bfb3f259d3f973b9d upstream.
setresuid allows the euid to be set to any of uid, euid, suid, and
fsuid. Therefor it is safe to allow
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Andy Lutomirski
commit f647d7c155f069c1a068030255c300663516420e upstream.
Otherwise, if buggy user code points DS or ES into the TLS
array, they would be corrupted after a context s
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: "Eric W. Biederman"
commit 0542f17bf2c1f2430d368f44c8fcf2f82ec9e53e upstream.
The rule is simple. Don't allow anything that wouldn't be allowed
without unprivileged mappings.
It w
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Nadav Amit
commit 7e466f6cd5dbf3c7bd04a7e75d19475ac9f2 upstream.
[3.13-stable's first backport (f9bffe0) of this commit accidentally omitted
part of the upstream patch (the WARN
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Ronald Wahl
commit b2ba27a5c56ff7204d8a8684893d64d4afe2cee5 upstream.
Commit 7628083227b6bc4a7e33d7c381d7a4e558424b6b (usb: gadget: at91_udc:
prepare clk before calling enable) adde
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: David Ertman
commit b20a774495671f037e7160ea2ce8789af6b61533 upstream.
In commit da1e2046e5, the flow for enabling/disabling an Si errata
workaround (e1000_lv_jumbo_workaround_ich8l
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Andy Whitcroft
Fixes up 4fab907195 ("tcp: fix tcp_release_cb() to dispatch via address
family for mtu_reduced()") backport which has swapped ipv4/ipv6 callbacks
for native IPv6 and m
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Sasha Levin
commit a3a8784454692dd72e5d5d34dcdab17b4420e74c upstream.
When a key is being garbage collected, it's key->user would get put before
the ->destroy() callback is called,
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Sven Eckelmann
commit 5b6698b0e4a37053de35cc24ee695b98a7eb712b upstream.
The fragmentation code was replaced in 610bfc6bc99bc83680d190ebc69359a05fc7f605
("batman-adv: Receive fragme
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: "Eric W. Biederman"
commit 273d2c67c3e179adb1e74f403d1e9a06e3f841b5 upstream.
setgroups is unique in not needing a valid mapping before it can be called,
in the case of setgroups(0,
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Al Viro
commit ca5358ef75fc69fee5322a38a340f5739d997c10 upstream.
... by not hitting rename_retry for reasons other than rename having
happened. In other words, do _not_ restart wh
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: "Eric W. Biederman"
commit f95d7918bd1e724675de4940039f2865e5eec5fe upstream.
If you did not create the user namespace and are allowed
to write to uid_map or gid_map you should alre
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Jan Kara
commit f54e18f1b831c92f6512d2eedb224cd63d607d3d upstream.
Rock Ridge extensions define so called Continuation Entries (CE) which
define where is further space with Rock Rid
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: "Eric W. Biederman"
commit 7ff4d90b4c24a03666f296c3d4878cd39001e81e upstream.
Today there are 3 instances of setgroups and due to an oversight their
permission checking has diverged
3.13.11-ckt14 -stable review patch. If anyone has any objections, please let
me know.
--
From: Andy Lutomirski
commit 394f56fe480140877304d342dec46d50dc823d46 upstream.
The theory behind vdso randomization is that it's mapped at a random
offset above the top of the stack. To
I am announcing the release of the Linux 3.16.7-ckt4 kernel.
The updated 3.16.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.16.y
and can be browsed at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=refs/heads/linux-3.16.y;a=shortlog
The diff from v3.16.7-c
On Wed, Jan 14, 2015 at 5:54 PM, Roman Peniaev wrote:
> On Thu, Jan 15, 2015 at 5:51 AM, Kees Cook wrote:
>> On Tue, Jan 13, 2015 at 12:35 AM, Roman Peniaev wrote:
>>> On Tue, Jan 13, 2015 at 3:39 AM, Will Deacon wrote:
On Sun, Jan 11, 2015 at 02:32:30PM +, Roman Pen wrote:
> threa
76 matches
Mail list logo
