Hi Linus,
Can you please pull the updates from the tree below? These are fixes
for regressions/bugs introduced in the 4.0 merge cycle and problems
discovered during the merge window that need to be pushed back to
stable kernels ASAP.
Thanks in advance!
-Dave.
The following changes since commit
On Tue, Feb 24, 2015 at 10:20:24PM -0800, Joe Perches wrote:
> On Wed, 2015-02-25 at 08:08 +0200, Aya Mahfouz wrote:
> > What is the next step?
>
> Ideally, you understanding why the suggested patch
> is an improvement over the patch you proposed.
>
> Beyond that, submit a patch. Then submit mor
On Sun, Feb 08, 2015 at 12:25:53PM +0530, Vaishali Thakkar wrote:
> This patch introduces the use of function setup_timer.
>
> This is done using Coccinelle and semantic patch used is
> as follows:
>
> @@
> expression x,y,z;
> @@
>
> - init_timer (&x);
> + setup_timer (&x, y, z);
> - x.function
On Thu, Feb 26, 2015 at 10:20:06PM -0300, Alberto Pires de Oliveira Neto wrote:
> Signed-off-by: Alberto Pires de Oliveira Neto
>
> drivers/staging/lustre/lustre/fld/fld_request.c | 7 +++
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/staging/lustre/lustre/fld/fld
Hi Linus,
Please consider these SH drivers updates for v4.0.
I am sending this change after v4.0-rc1 has been released
as it depends on r8a7740 SoC changes which are present in that rc release.
I expect some more minor updates to the same file during the v4.1 release cycle
to reflect changes to
From: Geert Uytterhoeven
If the default PM domain using PM_CLK is used for PM runtime, the real PM
domain(s) cannot be registered from DT later.
Hence do not enable it when running a multi-platform kernel with genpd
support on an r8a7740. The R-Mobile PM domain driver will take care of
PM runtim
Quoting Stephen Boyd (2015-02-23 13:30:28)
> PXO is 25MHz, not 27MHz. Fix the table.
>
> Fixes: 24d8fba44af3 "clk: qcom: Add support for IPQ8064's global
> clock controller (GCC)"
>
> Signed-off-by: Stephen Boyd
Applied to clk-next.
Regards,
Mike
> ---
> drivers/clk/qcom/gcc-ipq806x.c | 2 +-
drivers/platform/chrome/cros_ec_lpc.c:272:3-8: No need to set .owner here. The
core will do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
CC: Bill Richardson
Signed-off-by: Fengguang Wu
---
cros_ec_lpc.
tree: git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
pci/enumeration
head: 84dad4dda42cbf93ecf029c5a6b0af35305d6f75
commit: 762f920d602e28bf32d27003c93ca05244957aff [21/30] PCI: Introduce
pci_bus_child_max_busnr()
reproduce:
# apt-get install sparse
git checkout 762f920d602
drivers/pci/pci.c:111:15: sparse: symbol 'pci_bus_max_busnr' was not declared.
Should it be static?
Signed-off-by: Fengguang Wu
---
pci.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 2abac8f..51b24f3 100644
--- a/drivers/pci/
On Thu, 2015-02-26 at 14:31 +0100, Sebastian Andrzej Siewior wrote:
> On 02/26/2015 02:02 PM, Paolo Bonzini wrote:
> >
> >
> > On 24/02/2015 00:27, Scott Wood wrote:
> >> This isn't a host PIC driver. It's guest PIC emulation, some of which
> >> is indeed not suitable for a rawlock (in particula
This patch adds the device tree bindings for ktd2692 flash LEDs
Signed-off-by: Ingi Kim
---
.../devicetree/bindings/leds/leds-ktd2692.txt | 19 +++
1 file changed, 19 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/leds-ktd2692.txt
diff --git a/Do
This patch adds vendor prefix for Kinetic technologies
Signed-off-by: Ingi Kim
---
.../devicetree/bindings/vendor-prefixes.txt|1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.
This patch supports KTD2692 flash LED driver
Ingi Kim (3):
of: Add vendor prefix for Kinetic technologies
leds: ktd2692: add device tree bindings for ktd2692
leds: Add ktd2692 flash LED driver
.../devicetree/bindings/leds/leds-ktd2692.txt | 19 ++
.../devicetree/bindings/vendor-pref
Hi Dmitry,
Thanks. I'll go through his patch and make the appropriate changes to
our driver.
Jon
On 15-02-24 03:18 PM, Dmitry Torokhov wrote:
> Jonathan,
>
>
> On Wed, Feb 11, 2015 at 10:45:34AM -0800, Jonathan Richardson wrote:
>> Pinging maintainers... Am I ok to go ahead with the current ro
This patch adds a driver to support the ktd2692 flash LEDs.
ktd2692 can control flash current by ExpressWire interface.
Signed-off-by: Ingi Kim
---
drivers/leds/Kconfig|8 ++
drivers/leds/Makefile |1 +
drivers/leds/leds-ktd2692.c | 245
(2015/02/26 23:46), Arnaldo Carvalho de Melo wrote:
> Em Thu, Feb 26, 2015 at 05:25:04PM +0900, Masami Hiramatsu escreveu:
>> Fix get_real_path to free allocated memory when comp_dir
>> is used for complementing path and getting an error.
>
>
> While reviewing this patch I noticed this is needed,
On 2015/2/27 7:57, Bjorn Helgaas wrote:
> On Thu, Feb 26, 2015 at 04:11:54PM +0800, Yijing Wang wrote:
>> v3->v4:
>> Fix the rebase issue.
>
> This did apply on v4.0-rc1, but with many whitespace complaints:
>
> Importing patch "pci-pass-pci-domain-number" ... :29: trailing
> whitespace.
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/i915_drv.h between commit b3a38998f042 ("drm/i915:
Fix a use after free, and unbalanced refcounting") from the
drm-intel-fixes tree and commit 98e1bd4ae68e ("drm/i915: Cache ringbuf
pointer in request str
From: Desmond Liu
Fixed behaviour of get_mctrl() serial driver function as documented in:
https://www.kernel.org/doc/Documentation/serial/driver
Added device-tree properties 'dcd-override', 'dsr-override',
'cts-override', and 'ri-override' specific to the Synopsis 8250
DesignWare UART driver. Al
Hi,
This patchset fixes a bug in the Synopsis 8250 serial driver which causes the
driver to hang. The bug occurs on simple 2 wire serial ports when modem control
signalling has been enabled. It can be reproduced from user space by enabling
modem control signals (stty -clocal), then opening a seria
Hi,
> From: Rafael J. Wysocki [mailto:r...@rjwysocki.net]
> Sent: Thursday, February 26, 2015 6:56 AM
>
> On Wednesday, February 25, 2015 03:01:08 PM Scot Doyle wrote:
> > On Wed, 25 Feb 2015, Zheng, Lv wrote:
> > ...
> > > > I was using "+"/"#"/"*" to filter different EC log entries
On Thu, Feb 26, 2015 at 05:30:00PM -0400, Eduardo Valentin wrote:
> On Thu, Feb 26, 2015 at 07:00:33PM +, Javi Merino wrote:
> > It's useful for tuning to be able to edit thermal_zone_parameters from
> > userspace. Export them to the thermal_zone sysfs so that they can be
> > easily changed.
>
This adds support for reporting the actual and maximum combined channels
count of the hv_netvsc driver via 'ethtool --show-channels'.
This required adding 'max_chn' to 'struct netvsc_device', and assigning
it 'rsscap.num_recv_que' in 'rndis_filter_device_add'. Now we can access
the combined maximu
On Tue, Feb 17, 2015 at 06:44:19PM +0100, Sebastian Andrzej Siewior wrote:
> * Peter Zijlstra | 2015-01-21 16:07:16 [+0100]:
>
> >On Tue, Jan 20, 2015 at 01:16:13PM -0500, Steven Rostedt wrote:
> >> I'm actually wondering if we should just nuke the _interruptible()
> >> version of swait. As it sho
On Tue, Feb 17, 2015 at 03:14:00PM -0800, Feng Kan wrote:
> The generic accessor functions for pci-xgene uses map_bus
> call that returns the base address but did not add the additional
> offset.
>
> Signed-off-by: Feng Kan
> ---
> drivers/pci/host/pci-xgene.c | 4 ++--
> 1 file changed, 2 inser
On Thu, Feb 26, 2015 at 4:11 PM, Kees Cook wrote:
> On Thu, Feb 26, 2015 at 4:06 PM, Andrew Morton
> wrote:
>> On Thu, 26 Feb 2015 15:37:37 -0800 Kees Cook wrote:
>>
>>> Agh, no, please let's avoid the CONFIG addition.
>>
>> That is precisely how we do this.
>>
>>> Hector mentioned in private ma
On 02/26/15 16:00, Stephen Boyd wrote:
> The RPM regulators are not individual devices. Creating platform
> devices for each regulator bloats the kernel's runtime memory
> footprint by ~12k. Let's rework this driver to be a single
> platform device for all the RPM regulators. This makes the
> DT ma
On Thu, Feb 26, 2015 at 2:04 PM, Amit Pundir wrote:
> Hi,
>
> I ran into series of following binder mmap failures with v4.0.0-rc1:
> [ cut here ]
> WARNING: CPU: 0 PID: 1971 at mm/vmalloc.c:130
> vmap_page_range_noflush+0x119/0x144()
> CPU: 0 PID: 1971 Comm: healthd Not tai
On Thu, Feb 26, 2015 at 3:35 PM, Gwendal Grignou wrote:
> Tested-by: Gwendal Grignou
> Reviewed-by: Gwendal Grignou
>
> Tested on a chromebook pixel with kernel 4.0.0-rc1 and ectool using
> the enclosed patch in chromiumos platform/ec tree.
> I checked the lightbar is working, check the calls wi
On Thu, 26 Feb 2015 17:18:25 -0400
Eduardo Valentin wrote:
> Steve,
>
> On Thu, Feb 26, 2015 at 05:52:59PM -0500, Steven Rostedt wrote:
> > On Thu, 26 Feb 2015 15:46:34 -0400
> > Eduardo Valentin wrote:
> >
> >
> > > I am planing to apply this series to my thermal soc tree. Do you have
> > >
The ia32 sysenter code loaded the top of the kernel stack into rsp
by loading kernel_stack and then adjusting it. It can be simplified
to just read sp0 directly.
This requires the addition of a new asm-offsets entry for sp0.
Signed-off-by: Andy Lutomirski
---
arch/x86/ia32/ia32entry.S|
We currently store references to the top of the kernel stack in
multiple places: kernel_stack (with an offset) and
init_tss.x86_tss.sp0 (no offset). The latter is defined by hardware
and is a clean canonical way to find the top of the stack. Add an
accessor so we can start using it.
This needs m
This will make modifying the semantics of kernel_stack easier.
Cc: Konrad Rzeszutek Wilk
Cc: Boris Ostrovsky
Cc: Rusty Russell
Signed-off-by: Andy Lutomirski
---
arch/x86/include/asm/thread_info.h | 3 +--
arch/x86/kernel/traps.c| 2 +-
2 files changed, 2 insertions(+), 3 deletion
Hi Mike,
On Thu, 26 Feb 2015 16:01:24 -0800 Mike Turquette wrote:
>
> It's OK. I fixed it up locally the same day that I applied it but
> didn't push the change out to my mirror in time to catch -next. It
> will be fixed the next time Stephen pulls the clk tree.
Which I have just done. Thanks.
On 02/26/15 03:13, Geert Uytterhoeven wrote:
> From: Geert Uytterhoeven
>
> Hi,
>
> This patch series improves the documentation for printk() formats, and
> adds support for printing clocks. The latter has always been a hassle if
> you wanted to support both the common and legacy clock frame
On Thu, Feb 26, 2015 at 1:09 AM, Krzysztof Kozlowski
wrote:
> On czw, 2015-02-26 at 13:14 +1100, Stephen Rothwell wrote:
>> Hi Mike,
>>
>> After merging the clk tree, today's linux-next build (x86_64 allmodconfig)
>> failed like this:
>>
>> drivers/clk/clk.c: In function 'clk_disable_unused_subtre
The RPM regulators are not individual devices. Creating platform
devices for each regulator bloats the kernel's runtime memory
footprint by ~12k. Let's rework this driver to be a single
platform device for all the RPM regulators. This makes the
DT match the schematic/datasheet closer too because no
On Thu, Feb 26, 2015 at 04:11:54PM +0800, Yijing Wang wrote:
> v3->v4:
> Fix the rebase issue.
This did apply on v4.0-rc1, but with many whitespace complaints:
Importing patch "pci-pass-pci-domain-number" ... :29: trailing
whitespace.
bus = pci_scan_root_bus(NULL,
:44: trail
Denys is right that KERNEL_STACK_OFFSET is a mess. Let's start fixing
it.
This removes all C code that *reads* kernel_stack. It also fixes the
KERNEL_STACK_OFFSET abomination in ia32_sysenter_target.
It does not fix the KERNEL_STACK_OFFSET abomination in GET_THREAD_INFO
and THREAD_INFO. I thin
On Thu, Feb 26, 2015 at 07:00:33PM +, Javi Merino wrote:
> It's useful for tuning to be able to edit thermal_zone_parameters from
> userspace. Export them to the thermal_zone sysfs so that they can be
> easily changed.
>
> Cc: Zhang Rui
> Cc: Eduardo Valentin
> Signed-off-by: Javi Merino
>
On Thu, Feb 26, 2015 at 08:08:15AM +, Wu, Feng wrote:
>
>
> > -Original Message-
> > From: Marcelo Tosatti [mailto:mtosa...@redhat.com]
> > Sent: Thursday, February 26, 2015 5:50 AM
> > To: Wu, Feng
> > Cc: t...@linutronix.de; mi...@redhat.com; h...@zytor.com; x...@kernel.org;
> > g..
On Fri, Dec 12, 2014 at 11:14:58PM +0800, Feng Wu wrote:
> This patch updates the Posted-Interrupts Descriptor when vCPU
> is blocked.
>
> pre-block:
> - Add the vCPU to the blocked per-CPU list
> - Clear 'SN'
> - Set 'NV' to POSTED_INTR_WAKEUP_VECTOR
>
> post-block:
> - Remove the vCPU from the
As this is already being logged elsewhere we shouldn't spam the log
unnecessarily upon EPROBE_DEFER.
Signed-off-by: Bjorn Andersson
---
Maybe we should have a dev_dbg() for EPROBE_DEFER to aid finding which
regulator it actually was that it deferred?
drivers/regulator/core.c | 5 +++--
drive
On Thu, 26 Feb 2015 15:34:36 -0800 Kees Cook wrote:
> >> That pointless repetition should be avoided.
> >
> > That's surprisingly hard!
> >
> > After renaming mips brk_rnd() to mmap_rnd() I had a shot. I'm not very
> > confident in the result. Does that __weak trick even work?
>
> In theory, i
On Fri, Feb 27, 2015 at 03:34:32AM +0530, Amit Pundir wrote:
> Hi,
>
> I ran into series of following binder mmap failures with v4.0.0-rc1:
> [ cut here ]
> WARNING: CPU: 0 PID: 1971 at mm/vmalloc.c:130
> vmap_page_range_noflush+0x119/0x144()
> CPU: 0 PID: 1971 Comm: health
On Thu, 26 Feb 2015, Benjamin Tissoires wrote:
> These 2 are left over from the USB dependency cleaning, so there is
> no need to keep them.
>
> Signed-off-by: Benjamin Tissoires
I have fixed the filename in the subject :) and applied. Thanks.
> ---
> drivers/hid/hid-multitouch.c | 1 -
> dr
Tested-by: Gwendal Grignou
Reviewed-by: Gwendal Grignou
Tested on a chromebook pixel with kernel 4.0.0-rc1 and ectool using
the enclosed patch in chromiumos platform/ec tree.
I checked the lightbar is working, check the calls with "strace ectool
...", check the sysfs interface calls.
---
util/
On Thu, Feb 26, 2015 at 2:38 PM, Andrew Morton
wrote:
> On Tue, 24 Feb 2015 08:39:06 +0100 Ingo Molnar wrote:
>
>>
>> * Hector Marco Gisbert wrote:
>>
>> > +unsigned long randomize_et_dyn(unsigned long base)
>> > +{
>> > + unsigned long ret;
>> > + if ((current->personality & ADDR_NO_RANDOMI
Steve,
On Thu, Feb 26, 2015 at 05:52:59PM -0500, Steven Rostedt wrote:
> On Thu, 26 Feb 2015 15:46:34 -0400
> Eduardo Valentin wrote:
>
>
> > I am planing to apply this series to my thermal soc tree. Do you have
> > any concerns if I send this patch, which touches the tracing files, via
> > my
On 2/25/2015 8:02 AM, Wolfram Sang wrote:
> From: Wolfram Sang
>
> Signed-off-by: Wolfram Sang
> ---
> drivers/i2c/busses/i2c-bcm-iproc.c | 15 +++
> 1 file changed, 7 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-bcm-iproc.c
> b/drivers/i2c/busses/i2c-bc
Hi Andrew,
[Just resending to correct addresses - sorry for those who get a duplicate]
On Thu, 26 Feb 2015 14:38:15 -0800 Andrew Morton
wrote:
>
> diff -puN
> fs/binfmt_elf.c~fix-offset2lib-issue-for-x86-arm-powerpc-and-mips-fix
> fs/binfmt_elf.c
> --- a/fs/binfmt_elf.c~fix-offset2lib-issue-f
We don't know whether x_max or y_max really hold the maximum possible
coordinates, and we don't know for sure whether we correctly interpret the
coordinates sent by the touchpad, so we clamp the reported values to
prevent confusion in userspace code.
Signed-off-by: Mathias Gottschlag
---
drivers
The size has in most cases already been fetched from the touchpad, the
hardcoded values should have been removed.
Signed-off-by: Mathias Gottschlag
---
drivers/input/mouse/focaltech.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/drivers/input/mouse/focaltech.c b/driver
These PS/2 commands make some touchpads stop responding, so this commit
adds some dummy functions to replace the generic implementation. Because
scale changes were not encapsulated in a method of struct psmouse yet, this
commit adds a method set_scale to psmouse.
Signed-off-by: Mathias Gottschlag
Hi,
Changes since the last version:
- I added a commit which clamps the reported coordinates to valid values, even
if the values reported by the touchpad are wrong/misinterpreted.
- PSMOUSE_CMD_SETSCALE11 is now encapsulated in a member function of struct
psmouse, like the other configuration
Apparently, the threshold for large contact area seems to be rather low on
some devices, causing the touchpad to frequently freeze during normal
usage. Because we do now know how we are supposed to use the value in
question, this commit just drops the related code completely.
Signed-off-by: Mathia
Me versions of the two $subject patches follow.
Thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at ht
From: Rafael J. Wysocki
Disabling interrupts at the end of cpuidle_enter_freeze() is not
useful, because its caller, cpuidle_idle_call(), re-enables them
right away after invoking it.
To avoid that unnecessary back and forth dance with interrupts,
make cpuidle_enter_freeze() enable interrupts af
From: Rafael J. Wysocki
Modify cpuidle_enter_freeze() to do the sanity checks done by
cpuidle_select() to avoid crashing the suspend-to-idle code
path in case something is missing.
Original-by: Lorenzo Pieralisi
Signed-off-by: Rafael J. Wysocki
---
drivers/cpuidle/cpuidle.c | 23 +++
On 02/25/2015 10:14 PM, Konstantin Khlebnikov wrote:
> It seems nobody needs this.
Yay!
I was just digging through an OOM on a system with 288 logical CPUs. It
sucked.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.or
On Thu, 26 Feb 2015 23:00:52 + Russell King - ARM Linux
wrote:
> On Thu, Feb 26, 2015 at 02:38:15PM -0800, Andrew Morton wrote:
> > diff -puN
> > arch/arm64/Kconfig~fix-offset2lib-issue-for-x86-arm-powerpc-and-mips-fix
> > arch/arm64/Kconfig
> > ---
> > a/arch/arm64/Kconfig~fix-offset2lib
Hi,
On Thu, Feb 26, 2015 at 11:19:50PM +0100, Pavel Machek wrote:
> Ok, it seems that new config dependencies broke my kconfig. These will
> not be enabled if you just to make oldconfig; you want to make sure
> they are on.
>
> OMAP2430 and onwards (USB_MUSB_OMAP2PLUS) [N/m/y] (NEW)
> TWL4030 US
On Thu, 26 Feb 2015 14:38:15 -0800 Andrew Morton
wrote:
> Does that __weak trick even work?
Nope.
--- a/fs/binfmt_elf.c~fix-offset2lib-issue-for-x86-arm-powerpc-and-mips-fix-fix
+++ a/fs/binfmt_elf.c
@@ -2307,10 +2307,10 @@ unsigned long __weak mmap_rnd(void)
}
/*
- * Not all architectures
On Thu, Feb 26, 2015 at 02:38:15PM -0800, Andrew Morton wrote:
> diff -puN
> arch/arm64/Kconfig~fix-offset2lib-issue-for-x86-arm-powerpc-and-mips-fix
> arch/arm64/Kconfig
> --- a/arch/arm64/Kconfig~fix-offset2lib-issue-for-x86-arm-powerpc-and-mips-fix
> +++ a/arch/arm64/Kconfig
> @@ -1,4 +1,4 @@
On Thu, Feb 26, 2015 at 04:24:53PM -0600, Rob Herring wrote:
> We really shouldn't do private implementation here. It there really
> any reason not to allow readq/writeq generically for 32-bit or just
> for arm32?
My argument has always been that drivers should do the emulation of
64-bit accesses
set_task_ioprio() could return success (zero) even if it actually failed
to set the new ioprio. This patch fixes this by returning -ENOMEM if the
call to get_task_io_context() fails.
Signed-off-by: Luis Henriques
---
block/ioprio.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-
This goto statement can simply be replaced by a break, and the label can
be dropped.
Signed-off-by: Luis Henriques
---
block/ioprio.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/block/ioprio.c b/block/ioprio.c
index 42c680a17be4..cad43c832cc3 100644
--- a/block/ioprio.c
When setting an invalid scheduler through sysfs, two log entries will be
added. Also, when running 'echo foo > /sys/block/DISK/queue/scheduler'
the second one will includes the extra '\n':
[10465.216944] elevator: type foo not found
[10465.216953] elevator: switch to foo
failed
This patch simpl
On Thu, 26 Feb 2015 15:46:34 -0400
Eduardo Valentin wrote:
> I am planing to apply this series to my thermal soc tree. Do you have
> any concerns if I send this patch, which touches the tracing files, via
> my tree?
>
Which tracing files?
-- Steve
--
To unsubscribe from this list: send the l
On Mon, 23 Feb 2015 21:17:01 +0100 Michal Hocko wrote:
> ping on this one? Should I just resend (your way Andrew)? Or are there
> any objections to the patch as is.
Were Eric's concerns all addressed?
Oleg: wake up ;)
Overall it looks like a pretty minor issue?
--
To unsubscribe from this list
> Surely I am getting old and forgetting things, but when I wrote it, my
> intent was to do:
>
> vi a.c
> build it
> perf record a
> vi a.c # change it
> build it
> perf record a
> perf diff
>
> And see if what I did while vi'ing it matched what I thought it would.
You're right of course. As you
Hyper-V allows a guest to notify the Hyper-V host that a panic
condition occured. This notification can include up to five 64
bit values. These 64 bit values are written into crash MSRs.
Once the data has been written into the crash MSRs, the host is
then notified by writing into a Crash Control
On Thu, Jan 8, 2015 at 2:43 PM, Andy Lutomirski wrote:
> On Thu, Jan 8, 2015 at 2:31 PM, Marcelo Tosatti wrote:
>> On Tue, Jan 06, 2015 at 11:49:09AM -0800, Andy Lutomirski wrote:
>>> On Tue, Jan 6, 2015 at 10:45 AM, Marcelo Tosatti
>>> wrote:
>>> > On Tue, Jan 06, 2015 at 10:26:22AM -0800, And
Hi,
On Thu, Feb 26, 2015 at 02:49:50PM +0100, Pali Rohár wrote:
> This patch series fix crypto support for omap3 devices which use DT.
>
> It enables AES and SHAM on N9/N950 and SHAM on N900. AES is still disabled
> for N900.
(Please format your lines somewhere near < 76 chars, especially in
co
From: Rafael J. Wysocki
It currently is required that all users of NO_SUSPEND interrupt
lines pass the IRQF_NO_SUSPEND flag when requesting the IRQ or the
WARN_ON_ONCE() in irq_pm_install_action() will trigger. That is
done to warn about situations in which unprepared interrupt handlers
may be r
From: Denys Vlasenko
RESTORE_EXTRA_REGS + RESTORE_C_REGS looks small, but it's
a lot of instructions (fourteen). Let's reuse them.
[I changed the labels. In vda's version of this patch, paranoid_exit_restore
was paranoid_restore1 and paranoid_exit_no_swapgs was paranoid_restore.
This still is
From: Denys Vlasenko
ARGOFFSET is zero now, removing it changes no code.
A few macros lost "offset" parameter, since it is always zero now too.
No code changes - verified with objdump.
Signed-off-by: Denys Vlasenko
CC: Linus Torvalds
CC: Oleg Nesterov
CC: Borislav Petkov
CC: "H. Peter Anvin
On 02/26/2015 02:38 PM, Andrew Morton wrote:
[...]
From: Andrew Morton
Subject: fix-offset2lib-issue-for-x86-arm-powerpc-and-mips-fix
Consolidate randomize_et_dyn() implementations into fs/binfmt_elf.c.
There doesn't seem to be a compile-time way of making randomize_et_dyn()
go away on archite
From: Denys Vlasenko
Sequences
pushl_cfi %reg
CFI_REL_OFFSET reg, 0
and
popl_cfi %reg
CFI_RESTORE reg
happen quite often. This patch adds macros which generate them.
No assembly changes (verified with objdump -dr vmlinux.o).
Link:
http://lkml.kernel.org/r/142101
From: Denys Vlasenko
Misleading and slightly wrong comments in "struct pt_regs" are fixed
(four instances).
Fix wrong comment atop EMPTY_FRAME macro.
Explain in more details what we do with stack layout during hw interrupt.
Correct comments about "partial stack frame" which are no longer true.
From: Denys Vlasenko
Constants such as SS+8 or SS+8-RIP are mysterious.
In most cases, SS+8 is just meant to be SIZEOF_PTREGS,
SS+8-RIP is RIP's offset in iret frame.
This patch changes some of these constants to be less mysterious.
No code changes (verified with objdump).
Signed-off-by: Denys
From: Denys Vlasenko
This patch does a lot of cleanup in comments and formatting,
but it does not change any code.
Rename save_paranoid to paranoid_entry: this makes naming
similar to its "non-paranoid" sibling, error_entry,
and to its counterpart, paranoid_exit.
Use the same CFI annotation ato
From: Denys Vlasenko
For some odd reason, these two functions are at the very top of the file.
save_paranoid's caller is approximately in the middle of it, move it there.
Move ret_from_fork to be right after fork/exec helpers.
This is a pure block move, nothing is changed in the function bodies.
From: Denys Vlasenko
Use of a small macro - one with conditional expansion - does more harm
than good. It obfuscates code, with minimal code reuse.
For example, because of obfuscation it's not obvious that
in ia32_sysenter_target, we can optimize loading of r9 -
currently it is loaded with a det
From: Denys Vlasenko
Avoid redundant load of %r11 (it is already loaded a few instructions before).
Do not needlessly increment %rsp - we are going to return to userspace
via SYSRET, this insn doesn't use stack for return.
Changes since v1: added a comment
Signed-off-by: Denys Vlasenko
CC: Lin
From: Denys Vlasenko
The last instance of "mysterious" SS+8 constant is replaced by SIZEOF_PTREGS.
Signed-off-by: Denys Vlasenko
CC: Linus Torvalds
CC: Steven Rostedt
CC: Ingo Molnar
CC: Borislav Petkov
CC: "H. Peter Anvin"
CC: Andy Lutomirski
CC: Oleg Nesterov
CC: Frederic Weisbecker
C
ret_from_fork checks TIF_IA32 to determine whether pt_regs and the
related state make sense for ret_from_sys_call. This is entirely
the wrong check. TS_COMPAT would make a little more sense, but
there's really no point in keeping this optimization at all.
This fixes a return to the wrong user CS
From: Denys Vlasenko
SYSCALL/SYSRET and SYSENTER/SYSEXIT have weird semantics.
Moreover, they differ in 32- and 64-bit mode.
What is saved? What is not? Is rsp set? Are interrupts disabled?
People tend to not remember these details well enough.
This patch adds comments which explain in detail
wh
From: Denys Vlasenko
64-bit code was using six stack slots less by not saving/restoring
registers which are callee-preserved according to C ABI,
and not allocating space for them.
Only when syscall needed a complete "struct pt_regs",
the complete area was allocated and filled in.
As an additional
Nothing references it any more.
Fixes: 96b6352c1271 x86_64, entry: Remove the syscall exit audit and schedule
optimizations
Reported-by: Denys Vlasenko
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/entry_64.S | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/kernel/entry_64.S b/
From: Denys Vlasenko
This is a preparatory patch for change in "struct pt_regs"
handling in entry_64.S.
trace_hardirqs thunks were (ab)using a part of pt_regs
handling code, namely SAVE_ARGS/RESTORE_ARGS macros,
to save/restore registers across C function calls.
Since SAVE_ARGS is going to be c
Hi all-
After much handwringing, painful review, and curation, here's round 1 of
the x86/asm changes. (This is not intended to imply that there will or
will not be a round 2.)
For ease of review for git users:
The following changes since commit 7453311d68f16a5c587c3cbf19563c9a4fbbd41a:
Merge
From: Denys Vlasenko
Since the last fix of this nature, few more instances have crept in.
Fix them up. No object code changes (constants have the same value).
[mea culpa --Andy]
Link:
http://lkml.kernel.org/r/1423778052-21038-1-git-send-email-dvlas...@redhat.com
Signed-off-by: Denys Vlasenko
> -Original Message-
> From: Alexander Graf [mailto:ag...@suse.de]
> Sent: Thursday, February 26, 2015 3:38 PM
> To: Yoder Stuart-B08248; a...@arndb.de
> Cc: Rivera Jose-B46482; linux-kernel@vger.kernel.org;
> gre...@linuxfoundation.org
> Subject: Re: [PATCH 0/3 v6] drivers/bus: Freescal
On Tue, 24 Feb 2015 08:39:06 +0100 Ingo Molnar wrote:
>
> * Hector Marco Gisbert wrote:
>
> > +unsigned long randomize_et_dyn(unsigned long base)
> > +{
> > + unsigned long ret;
> > + if ((current->personality & ADDR_NO_RANDOMIZE) ||
> > + !(current->flags & PF_RANDOMIZE))
> > +
On Thu, Feb 26, 2015 at 12:52:16PM -0800, Andi Kleen wrote:
> >
> > Thoughts?
>
> Just use my original patch using page tables which did not need any of these
> research projects.
Hey, some people actually like to think! And the benefit is that all
archs get a win.
--
To unsubscribe from this li
On Thu, Feb 26, 2015 at 10:49:53AM +0200, Nadav Amit wrote:
> Marcello, Radim,
>
> As you know - I can run some tests on the patches and whether they comply
> with real hardware. Please let me know which version to test and I’ll try to
> do next week.
>
> Regards,
> Nadav
>From what i understand
Embed video_device structs vdev and vbi_dev in au0828_dev.
With this change, dynamic allocation and error path logic
in au0828_analog_register() is removed as it doesn't need
to allocate and handle allocation errors. Unregister path
doesn't need to free the now static video_device structures,
hence
On 26.02.15 23:25, Stuart Yoder wrote:
>
>
>> -Original Message-
>> From: Alexander Graf [mailto:ag...@suse.de]
>> Sent: Thursday, February 26, 2015 3:38 PM
>> To: Yoder Stuart-B08248; a...@arndb.de
>> Cc: Rivera Jose-B46482; linux-kernel@vger.kernel.org;
>> gre...@linuxfoundation.org
101 - 200 of 793 matches
Mail list logo
