When mmc host HW supports busy signalling (using R1B as response), We
shouldn't use 'host->max_busy_timeout' as the limitation when deciding
the max discard sectors that we tell the generic BLOCK layer about.
Instead, we should pick one preferred erase size as the max discard
sectors.
If the host
Useful when tracing nested setups where the guest may trigger more than
the host usually does. But even some typical host exits were missing.
Signed-off-by: Jan Kiszka
---
arch/x86/include/uapi/asm/svm.h | 44 ++---
1 file changed, 41 insertions(+), 3 deletion
Specifically the change from hex to decimal helps correlating events.
Signed-off-by: Jan Kiszka
---
include/trace/events/kvm.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/trace/events/kvm.h b/include/trace/events/kvm.h
index 526fb3d..f28292d 100644
--- a/inc
Hi Linus,
Here's the main drm pull request for 4.7, it's been
a busy one, and I've been a bit more distracted in
real life this merge window. Lots more ARM drivers,
not sure if it'll ever end. I think I've at least
one more coming the next merge window.
But changes are all over the place, suppor
Fixed following checkpatch.pl warnings:
Prefer 'unsigned int' to bare use of 'unsigned'
Prefer READ_ONCE() over ACCESS_ONCE()
Signed-off-by: Shyam Saini
---
drivers/staging/rdma/hfi1/sdma.c | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git
Fixed following checkpatch.pl warnings:
Prefer 'unsigned int' to bare use of 'unsigned'
Prefer READ_ONCE() over ACCESS_ONCE()
Signed-off-by: Shyam Saini
---
drivers/staging/rdma/hfi1/rc.c | 12 ++--
drivers/staging/rdma/hfi1/ruc.c | 6 +++---
2 files changed, 9 insertions(+), 9 del
On 2016年05月05日 17:34, Tomeu Vizoso wrote:
On 20 April 2016 at 16:23, Tomeu Vizoso wrote:
On 11 April 2016 at 03:15, Mark yao wrote:
On 2016年04月08日 18:54, Tomeu Vizoso wrote:
On 8 April 2016 at 03:07, Mark yao wrote:
On 2016年04月06日 18:14, Tomeu Vizoso wrote:
When a plane is being disabled
Hi Felipe,
On Friday 20 May 2016 12:06 AM, Felipe Balbi wrote:
>
> Hi,
>
> Tony Lindgren writes:
>> * Peter Ujfalusi [160519 01:10]:
>>> On 05/18/2016 10:30 PM, Tony Lindgren wrote:
Ideally the adma support would be a separate loadable module,
similar how the cppi41dma is a child of
On Fri, Apr 15, 2016 at 4:27 PM, Sebastian Reichel wrote:
> Hi,
>
> On Wed, Mar 30, 2016 at 09:49:48AM +0900, Krzysztof Kozlowski wrote:
>> Enable the COMPILE_TEST to get build coverage, except on platforms
>> !HAS_IOMEM (required by selected MFD_SYSCON).
>>
>> Signed-off-by: Krzysztof Kozlowski
On 2016年05月11日 00:03, John Keeping wrote:
The first patch wasn't found by sparse, but is something I noticed while
in the area. The following two fix all of the sparse warnings inside
drm/rockchip.
John Keeping (3):
drm/rockchip: dw_hdmi: remove unused #include
drm/rockchip: fb: add missi
On Mon, May 23, 2016 at 08:32:09AM +0800, Honggang LI wrote:
> From: Honggang Li
>
> [ 598.852037] [ cut here ]
> [ 598.856698] WARNING: at lib/dma-debug.c:887 check_unmap+0xf8/0x920()
> [ 598.863079] cxgb3 :01:00.0: DMA-API: device driver frees DMA memory
> with d
Hi Marcel,
> > From: Amitkumar Karwar [mailto:akar...@marvell.com]
> > Sent: Friday, May 06, 2016 9:02 PM
> > To: linux-blueto...@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org; Ganapathi Bhat; Amitkumar Karwar
> > Subject: [PATCH v11 3/3] Bluetooth: hci_uart: Support firmware
> > download
Hello Sergey,
I talked with Joonsoo today and he has no time to support it at the moment
and I can't wait zlib support for zram until crypto work is merged.
So, I want to merge your work.
If you have an interest, still, could you mind resending the work
rebased on recent zram?
Thanks.
On Thu, Au
On Sun, 2016-05-22 at 08:54 -0700, Guenter Roeck wrote:
> Hi Oliver,
>
> On 05/20/2016 11:43 PM, Oliver Neukum wrote:
> > On Fri, 2016-05-20 at 22:51 -0700, Guenter Roeck wrote:
> >> On 05/20/2016 06:37 AM, Oliver Neukum wrote:
> >>> On Fri, 2016-05-20 at 14:24 +0300, Heikki Krogerus wrote:
>
2016-05-23 13:28 GMT+08:00 Kishon Vijay Abraham I :
> Hi,
>
> On Monday 23 May 2016 10:51 AM, Axel Lin wrote:
>> Signed-off-by: Axel Lin
>
> however obvious the patch maybe, it's nice to add a little commit log.
I think the subject line is already very clear about the intention.
In additional, che
Hi,
On Monday 23 May 2016 10:51 AM, Axel Lin wrote:
> Signed-off-by: Axel Lin
however obvious the patch maybe, it's nice to add a little commit log.
Thanks
Kishon
> ---
> drivers/phy/phy-brcm-sata.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/phy/phy-brcm-
Hello Guenter,
On Sun, May 22, 2016 at 06:06:24PM -0700, Guenter Roeck wrote:
> On 05/22/2016 11:21 AM, Uwe Kleine-König wrote:
> >On Sun, May 22, 2016 at 08:41:23AM -0700, Guenter Roeck wrote:
> >>I am not exactly in favor of forcing GPIOLIB to be enabled for every
> >>system with Ethernet suppor
Hi Chris,
On Sun, May 22, 2016 at 6:42 PM, Chris J Arges
wrote:
> I've noticed crashes when using my x60t using a coreboot bios. When using
> the pen I can produce a crash simply by tapping a few times. This
> generates an event which has an idx of 0xc. This in turn crashes the
> machine because
Signed-off-by: Axel Lin
---
drivers/phy/phy-brcm-sata.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/phy/phy-brcm-sata.c b/drivers/phy/phy-brcm-sata.c
index 6c4c5cb..5d7fad4b 100644
--- a/drivers/phy/phy-brcm-sata.c
+++ b/drivers/phy/phy-brcm-sata.c
@@ -288,7 +288,7
On 05/19/2016 06:20 PM, Rob Herring wrote:
On Thu, May 19, 2016 at 7:28 AM, Nicolas Ferre wrote:
Le 19/05/2016 01:29, Rob Herring a écrit :
On Wed, May 18, 2016 at 06:02:46PM +0530, Raashid Muhammed wrote:
From: Raashid Muhammed
sam9-l9260 is a low cost board designed by Olimex.
More inf
Hi all,
Please do not add any v4.8 destined material to your linux-next included
branches until after v4.7-rc1 has been released.
Changes since 20160520:
The drm-intel tree gained a build failure so I used the version from
next-20160520.
Non-merge commits (relative to Linus' tree): 2283
1939 f
On Sun, May 22, 2016 at 7:34 PM, Josh Poimboeuf wrote:
> On Sun, May 22, 2016 at 10:59:38AM -0700, Andy Lutomirski wrote:
>> cc: Josh Poimboeuf: do you care about the exact stack layout of the
>> bottom of the stack of an inactive task?
>
> So there's one minor issue with this patch, relating to u
On Sun, May 22, 2016 at 08:28:06AM -0700, Paul E. McKenney wrote:
> On Sun, May 22, 2016 at 02:26:49PM +0800, Boqun Feng wrote:
> > Hi Paul,
> >
> > On Sat, May 21, 2016 at 10:24:22PM -0700, Paul E. McKenney wrote:
> > > On Sun, May 22, 2016 at 10:36:00AM +0800, kernel test robot wrote:
> > > > Gr
Currently sdhci-arasan 5.1 can support enhanced strobe function,
and we now limit it just for "arasan,sdhci-5.1". Add
mmc-hs400-enhanced-strobe in DT to enable the function if we're
sure our controller can support it.
Signed-off-by: Shawn Lin
Acked-by: Adrian Hunter
Reviewed-by: Doug Anderson
-
We introduce HS400 with enhanced strobe function, so we need
to add it for debug show.
Signed-off-by: Shawn Lin
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/mmc/core/debugfs.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/
Controllers use data strobe line to latch data from devices
under hs400 mode, but not for cmd line. So since emmc 5.1, JEDEC
introduces enhanced strobe mode for latching cmd response from
emmc devices to host controllers. This new feature is optional,
so it depends both on device's cap and host's c
This patch introduce mmc-hs400-enhanced-strobe for platforms
which want to enable enhanced strobe function from DT if the
mmc host controller claims to support enhanced strobe.
Signed-off-by: Shawn Lin
---
Changes in v5:
- avoid to call hs400_enhanced+_strobe in mmc_set_initial_state
if no se
Hello all,
This patch is going to support enhanced strobe function
for emmc version 5.1+ introduced by JEDEC recently.
Enchanced strobe is a optional function, so we add a new cap* for drivers to
decide whether to use it.
When introduing hs400 mode, JEDEC asks controllers to use data strobe lin
mmc-hs400-enhanced-strobe is used to claim that the
host can support hs400 mode with enhanced strobe
introduced by emmc 5.1 spec.
Signed-off-by: Shawn Lin
Acked-by: Rob Herring
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
Documentation/devicetree/binding
From: Jaime Arrocha
Fixed checkpatch.pl warning about 'line over 80 characters'.
Signed-off-by: Jaime Arrocha
---
drivers/staging/android/ion/ion.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/android/ion/ion.c
b/drivers/staging/android/ion/ion.c
i
On 20-05-16, 23:33, Rafael J. Wysocki wrote:
> The policy rwsem is really only needed in cpufreq_stats_create_table(),
> because
> the policy notifier is gone when _free_table() runs, so another version of the
> patch goes below.
Right. I saw that while reading your previous version but didn't re
Hi, Doug Ledford
In hns_roce_cmd_wait and hns_roce_cmd_poll, there are down&up
seminal operations,
So, there are not deadlock and conflict, right?
static int hns_roce_cmd_poll(struct hns_roce_dev *hr_dev, u64 in_param,
u64 *out_param, unsigned long in_modifier
On 2016/5/23 8:48, Shawn Lin wrote:
On 2016/5/21 5:13, Heiko Stuebner wrote:
Hi Shawn,
I haven't had any contact with PCI yet, so my comments below will likely
address more generic findings only.
As you might've guessed from the binding comments, to me it looks like
the
phy handling should be
There are two paths calling this function.
For direct compact, there is no need to check the zone watermark here.
For kswapd wakeup kcompactd, since there is a reclaim before this.
It makes sense to do compact even the watermark is ok at this time.
Signed-off-by: Chen Feng
---
mm/compaction.c |
On Sat, May 21, 2016 at 10:29:40AM +0800, Peter Chen wrote:
> On Thu, May 19, 2016 at 10:32:44AM +0300, Roger Quadros wrote:
> > On 18/05/16 17:46, Jun Li wrote:
> > >
> > >
> >
> > I didn't want to have complex Kconfig so decided to have otg as
> > built-in only.
> > What do
There are multi codec devices on the RK3399 platform, we can use
this patch support and control these codecs.
Signed-off-by: Xing Zheng
---
.../sound/rockchip-max98357a-rt5514-da7219.txt | 15 +
sound/soc/rockchip/Kconfig | 11 +
sound/soc/rockchip/Makefile
On Thu, May 19, 2016 at 11:18:43AM -0400, Dan Streetman wrote:
> Change the return type of zs_pool_stat_create() to void, and
> remove the logic to abort pool creation if the stat debugfs
> dir/file could not be created.
>
> The debugfs stat file is for debugging/information only, and doesn't
> af
On Sun, May 22, 2016 at 10:59:38AM -0700, Andy Lutomirski wrote:
> cc: Josh Poimboeuf: do you care about the exact stack layout of the
> bottom of the stack of an inactive task?
So there's one minor issue with this patch, relating to unwinding the
stack of a newly forked task. For detecting relia
On 22-05-16, 11:05, Geert Uytterhoeven wrote:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
>
> Signed-off-by: Geert Uytterhoeven
> Cc: "Rafael J. Wysocki"
> Cc: Viresh Kumar
> Cc: linux...@vger.kernel.org
> ---
> Please apply
Hi all,
After merging the drm-intel tree, today's linux-next build (x86_64
allmodconfig) failed like this:
In file included from drivers/gpu/drm/i915/i915_trace.h:10:0,
from drivers/gpu/drm/i915/i915_drv.h:2735,
from drivers/gpu/drm/i915/i915_drv.c:34:
drivers/gp
As the comment block of of_parse_phandle_with_fixed_args() says,
the caller is responsible to call of_node_put() on the returned
node when done.
Signed-off-by: Masahiro Yamada
---
drivers/gpio/gpiolib-of.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpio/gpiolib-of.c b/drivers/g
A platform_driver need not set an owner since it will be populated
by platform_driver_register().
Likewise for mcb_driver (gpio-menz127.c).
Signed-off-by: Masahiro Yamada
---
drivers/gpio/gpio-menz127.c| 1 -
drivers/gpio/gpio-palmas.c | 1 -
drivers/gpio/gpio-rdc321x.c| 1 -
driver
I've noticed crashes when using my x60t using a coreboot bios. When using
the pen I can produce a crash simply by tapping a few times. This
generates an event which has an idx of 0xc. This in turn crashes the
machine because the array access is greater than W8001_MAX_LENGTH. This
patch checks for b
From: Simon
When rk_iommu_attach_device or rk_iommu_detach_device be called, the second
parameter "dev" represent the device who own the iommu, so it is not resonable
using "dev" for devm_request_irq's first parameter. To avoid potential error,
we must use iommu device itself "iommu->dev" instead
From: Simon
We mark DRM as "virtual" device by checking it's group,
which may no longer true with the new rockchip drm drv in
https://patchwork.kernel.org/patch/8876331/.
Checking the group->iommu_data for virtual device.
Signed-off-by: Simon
---
drivers/iommu/rockchip-iommu.c | 7 ++-
1
From: Simon
Signed-off-by: Simon
---
drivers/iommu/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig
index ad08603..5572621 100644
--- a/drivers/iommu/Kconfig
+++ b/drivers/iommu/Kconfig
@@ -218,7 +218,7 @@ config OMAP_IOMM
From: Simon
The iommu_dma_alloc() in iommu/dma-iommu.c calls iommu_map_sg()
that requires the callback iommu_ops .map_sg(). Adding the
default_iommu_map_sg() to rockchip iommu accordingly.
Signed-off-by: Simon
---
drivers/iommu/rockchip-iommu.c | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Simon
Signed-off-by: Simon
---
drivers/iommu/rockchip-iommu.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/iommu/rockchip-iommu.c b/drivers/iommu/rockchip-iommu.c
index 043d18c..1741b65 100644
--- a/drivers/iommu/rockchip-iommu.c
+++ b/drivers/iommu/rockchip-iommu.c
@@
Fix a few bugs for rockchip iommu and enable for ARM64.
Simon (5):
iommu/rockchip: fix devm_request_irq and devm_free_irq parameter
iommu/rockchip: add map_sg callback for rk_iommu_ops
iommu/rockchip: add sanity check for virtual device
iommu/rockchip: add ARM64 cache flush operation for i
On 2016/5/21 2:37, David Matlack wrote:
On Thu, May 19, 2016 at 7:04 PM, Yang Zhang wrote:
On 2016/5/20 2:36, David Matlack wrote:
On Thu, May 19, 2016 at 11:01 AM, David Matlack
wrote:
On Thu, May 19, 2016 at 6:27 AM, Wanpeng Li wrote:
From: Wanpeng Li
If an emulated lapic timer will
> On Tue, May 10, 2016 at 06:18:10AM +0200, Volker Lendecke wrote:
> > On Tue, May 10, 2016 at 12:02:33AM +0200, Andreas Gruenbacher wrote:
> > > What more can I do to finally get this merged?
> >
> > While I am not the one to comment on kernel specifics, from a pure Samba
> > user space perspecti
Hi, Doug Ledford
We will modify the license description of the beginning of the code file
in patch v8.
Thanks
Regards
Wei Hu
On 2016/5/14 5:09, Doug Ledford wrote:
On 05/09/2016 11:04 PM, Lijun Ou wrote:
The HiSilicon Network Substem is a long term evolution IP which is
supposed to be used
On 05/22/2016 11:21 AM, Uwe Kleine-König wrote:
Hello Guenter,
[extending Cc: a bit]
On Sun, May 22, 2016 at 08:41:23AM -0700, Guenter Roeck wrote:
On 05/22/2016 03:10 AM, Uwe Kleine-König wrote:
On Tue, May 17, 2016 at 09:37:11PM -0700, Guenter Roeck wrote:
[9.366256] libphy: ethoc-mdio
On Sun, May 22, 2016 at 3:53 PM, Haishuang Yan
wrote:
> For ipv6 case, enclose the code block in macro IS_ENABLED(CONFIG_IPV6).
>
> Signed-off-by: Haishuang Yan
> ---
> net/ipv4/ip_tunnel.c | 5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/net/ipv4/ip_tunnel.c b/net/ip
Hi Linus,
Can you please pull the m68knommu git tree, for-next branch.
Only a single change to update my email address in the MAINTAINERS file.
Regards
Greg
The following changes since commit 44549e8f5eea4e0a41b487b63e616cb089922b99:
Linux 4.6-rc7 (2016-05-08 14:38:32 -0700)
are available i
On 2016/5/21 5:13, Heiko Stuebner wrote:
Hi Shawn,
I haven't had any contact with PCI yet, so my comments below will likely
address more generic findings only.
As you might've guessed from the binding comments, to me it looks like the
phy handling should be in a separate phy driver and looking
From: Wanpeng Li
If an emulated lapic timer will fire soon(in the scope of 10us the
base of dynamic halt-polling, lower-end of message passing workload
latency TCP_RR's poll time < 10us) we can treat it as a short halt,
and poll to wait it fire, the fire callback apic_timer_fn() will set
KVM_REQ_
From: Honggang Li
[ 598.852037] [ cut here ]
[ 598.856698] WARNING: at lib/dma-debug.c:887 check_unmap+0xf8/0x920()
[ 598.863079] cxgb3 :01:00.0: DMA-API: device driver frees DMA memory with
different size [device address=0x0331] [map size=17 bytes] [un
On Sun, May 22, 2016 at 03:25:38PM -0700, Greg Kroah-Hartman wrote:
> On Mon, May 23, 2016 at 07:49:29AM +1000, Tobin C Harding wrote:
> > kzalloc call followed by copy_to_user can be replaced by call to
> > memdup_user.
> >
> > Signed-off-by: Tobin C Harding
>
> Why did you send this twice?
Be
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-4.7
...to receive the device driver related nvdimm topic branches for 4.7.
The bulk of this update was stabilized before the merge window and
appeared in -next. The "device dax" impleme
For ipv6 case, enclose the code block in macro IS_ENABLED(CONFIG_IPV6).
Signed-off-by: Haishuang Yan
---
net/ipv4/ip_tunnel.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/net/ipv4/ip_tunnel.c b/net/ipv4/ip_tunnel.c
index a69ed94..5f3c8de 100644
--- a/net/ipv4/ip_tunnel
On May 22, 2016 2:32:59 AM PDT, "jeffrey.lin" wrote:
>Hi Dmitry:
>
>+static int raydium_i2c_read_message(struct i2c_client *client,
>+ u32 addr, void *data, size_t len)
>+{
>+ __be32 be_addr;
>+ size_t xfer_len;
>+ int error;
>+
>+ while (len) {
On Mon, May 23, 2016 at 07:49:29AM +1000, Tobin C Harding wrote:
> kzalloc call followed by copy_to_user can be replaced by call to memdup_user.
>
> Signed-off-by: Tobin C Harding
Why did you send this twice?
> ---
> drivers/gpu/drm/gma500/gma_display.c | 2 +-
> drivers/staging/lustre/l
Hallo,
Suchen Sie ein Business-Darlehen, persönliche Darlehen, Haus Darlehen,
Autokredit , Darlehen, Schuldenkonsolidierung Darlehen, ungesicherte Darlehen,
Risikokapital usw. Kontakt bishopjohnnels...@outlook.com für weitere
Informationen.
Danke und Gott schütze dich.
On 22/05/16 20:42, Max Filippov wrote:
> Hi Colin,
>
> On Sun, May 22, 2016 at 08:08:18PM +0100, Colin King wrote:
>> From: Colin Ian King
>>
>> priv is assigned to NULL however all the error exit paths to label 'free'
>> dereference priv, causing a null pointer dereference.
>>
>> Examination of
On 05/21, Tetsuo Handa wrote:
>
> On 2016/05/21 5:28, Oleg Nesterov wrote:
> > It spins in __alloc_pages_slowpath() forever, __alloc_pages_may_oom() is
> > never
> > called, it doesn't react to SIGKILL, etc.
> >
> > This is because zone_reclaimable() is always true in shrink_zones(), and the
> > p
On Sun, May 22, 2016 at 12:31 PM, Brian Gerst wrote:
> On Sun, May 22, 2016 at 1:59 PM, Andy Lutomirski wrote:
>> cc: Josh Poimboeuf: do you care about the exact stack layout of the
>> bottom of the stack of an inactive task?
>>
>> On May 21, 2016 9:05 AM, "Brian Gerst" wrote:
>>>
>>> Move the l
On 20 May 2016 at 01:49, Bjorn Helgaas wrote:
> Hi Linus,
>
> Here are the PCI changes I intend for v4.7.
>
> There is a silent conflict that needs to be resolved when you pull this:
>
> - e3156048346c ("iommu/amd: Fix checking of pci dma aliases"), which is
> already in your tree, added a u
On Sun, May 22, 2016 at 12:39:12PM +0200, Peter Zijlstra wrote:
> On Fri, May 20, 2016 at 05:53:41PM +0530, Shilpasri G Bhat wrote:
> >
> > Below are the comparisons by disabling watchdog.
> > Both schedutil and ondemand have a similar ramp-down trend. And in both the
> > cases I can see that freq
Linus,
Three more changes.
1) I forgot that I had another selftest to stress test the ftrace
instance creation. It was actually suppose to go into the 4.6
merge window, but I never committed it. I almost forgot about it
again, but noticed it was missing from your tree.
2) Soumya PN sen
Hi,
[auto build test ERROR on linus/master]
url:
https://github.com/0day-ci/linux/commits/Bjorn-Helgaas/PCI-changes-for-v4-7/20160519-235212
config: x86_64-rhel (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
# save the attached .config to linux build tree
From: Soumya PN
In ftrace.c inside the function alloc_retstack_tasklist() (which will be
invoked when function_graph tracing is on) the tasklist_lock is being
held as reader while iterating through a list of threads. Here the lock
is being held as reader with irqs disabled. The tasklist_lock is n
From: "Steven Rostedt (Red Hat)"
Add a new ftrace test that creates three threads. One that creates and
removes an ftrace instance, one that reads the instance, and one that enables
and disables events in the instance. This is a stress test for accessing and
removing instances at the same time.
From: Steven Rostedt
Matt Fleming reported seeing crashes when enabling and disabling
function profiling which uses function graph tracer. Later Namhyung Kim
hit a similar issue and he found that the issue was due to the jmp to
ftrace_stub in ftrace_graph_call was only two bytes, and when it was
Hi Colin,
On Sun, May 22, 2016 at 08:08:18PM +0100, Colin King wrote:
> From: Colin Ian King
>
> priv is assigned to NULL however all the error exit paths to label 'free'
> dereference priv, causing a null pointer dereference.
>
> Examination of the code shows that all error exits via the 'free
On 22/05/16 10:06, Geert Uytterhoeven wrote:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
>
> Signed-off-by: Geert Uytterhoeven
> Cc: Jonathan Cameron
> Cc: linux-...@vger.kernel.org
Applied - thanks.
Jonathan
> ---
> Please a
On 22/05/16 10:05, Geert Uytterhoeven wrote:
> Submitters of device tree binding documentation may forget to CC
> the subsystem maintainer if this is missing.
>
> Signed-off-by: Geert Uytterhoeven
> Cc: Jonathan Cameron
> Cc: Hartmut Knaack
> Cc: Lars-Peter Clausen
> Cc: Peter Meerwald-Stadler
On Sun, May 22, 2016 at 1:59 PM, Andy Lutomirski wrote:
> cc: Josh Poimboeuf: do you care about the exact stack layout of the
> bottom of the stack of an inactive task?
>
> On May 21, 2016 9:05 AM, "Brian Gerst" wrote:
>>
>> Move the low-level context switch code to an out-of-line asm stub instea
On Sun, May 22, 2016 at 2:01 PM, Andy Lutomirski wrote:
> On Sat, May 21, 2016 at 9:04 AM, Brian Gerst wrote:
>> Instead of setting up a fake pt_regs context, put the kernel thread
>> function pointer and arg into the unused callee-restored registers
>> of struct fork_frame.
>>
>> Signed-off-by:
PLEASE CHECK ATTACHMENT AND CAN I TRUST YOU IN THIS DEAL?
Document.rtf
Description: RTF file
From: Colin Ian King
priv is assigned to NULL however all the error exit paths to label 'free'
dereference priv, causing a null pointer dereference.
Examination of the code shows that all error exits via the 'free'
label path occur before priv is assigned to netdev_priv(netdev), hence
there is n
On Sun, May 22, 2016 at 12:48:27PM +0200, Peter Zijlstra wrote:
> On Sat, May 21, 2016 at 11:14:49PM +0300, Alexey Dobriyan wrote:
> > lockless_dereference() is supposed to take pointer not integer.
>
> Urgh :/
>
> Is there any way we can make lockless_dereference() issue a warning if
> we don't
Hello Guenter,
[extending Cc: a bit]
On Sun, May 22, 2016 at 08:41:23AM -0700, Guenter Roeck wrote:
> On 05/22/2016 03:10 AM, Uwe Kleine-König wrote:
> >On Tue, May 17, 2016 at 09:37:11PM -0700, Guenter Roeck wrote:
> >>[9.366256] libphy: ethoc-mdio: probed
> >>[9.367389] (null): could n
On Sat, May 21, 2016 at 9:04 AM, Brian Gerst wrote:
> Instead of setting up a fake pt_regs context, put the kernel thread
> function pointer and arg into the unused callee-restored registers
> of struct fork_frame.
>
> Signed-off-by: Brian Gerst
Seems reasonable. Can you make sure you explicitl
cc: Josh Poimboeuf: do you care about the exact stack layout of the
bottom of the stack of an inactive task?
On May 21, 2016 9:05 AM, "Brian Gerst" wrote:
>
> Move the low-level context switch code to an out-of-line asm stub instead of
> using complex inline asm. This allows constructing a new s
On 05/22/2016 02:06 AM, Geert Uytterhoeven wrote:
Submitters of device tree binding documentation may forget to CC
the subsystem maintainer if this is missing.
Signed-off-by: Geert Uytterhoeven
Cc: Wim Van Sebroeck
Cc: Guenter Roeck
Cc: linux-watch...@vger.kernel.org
Reviewed-by: Guenter Ro
On 22 May 2016 at 18:41, Michal Suchanek wrote:
> Hello,
>
> The debugfs output shows that spi2 is reparented under pll5 and the
> pll5 frequency remains unchanged.
>
> The request to get a 2GHz clock for spi is fulfilled on best-effort
> basis by giving the 864MHz pll5 clock which should theoreti
On 5/22/2016 2:06 AM, Geert Uytterhoeven wrote:
Submitters of device tree binding documentation may forget to CC
the subsystem maintainer if this is missing.
Signed-off-by: Geert Uytterhoeven
Cc: Santosh Shilimkar
Cc: linux-kernel@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
---
Pl
Hello,
The debugfs output shows that spi2 is reparented under pll5 and the
pll5 frequency remains unchanged.
The request to get a 2GHz clock for spi is fulfilled on best-effort
basis by giving the 864MHz pll5 clock which should theoretically
result in 432MHz SPI clock.
On 22 May 2016 at 16:58, C
On Tue, 2016-05-17 at 23:53 +0200, Miklos Szeredi wrote:
> The two methods essentially do the same: find the real dentry/inode
> belonging to an overlay dentry. The difference is in the usage:
>
> vfs_open() uses ->d_select_inode() and expects the function to
> perform copy-up if necessary based
http://lkml.iu.edu/hypermail/linux/kernel/1512.0/04117.html
http://lkml.iu.edu/hypermail/linux/kernel/1512.0/04831.html
Same issue here with kernel 4.4.10 and 4.5.4 and r8153. Mine is an USB 3.0
Hub with Gigabit Ethernet, so the common point seems to be USB 3.0. For me
it only happens when play
From: Jan Kiszka
Exceptions require individual decoding (only feasible intercepts
listed), XSETBV was missing and the AVIC brought in two new exit codes.
Signed-off-by: Jan Kiszka
---
plugin_kvm.c | 21 -
1 file changed, 20 insertions(+), 1 deletion(-)
diff --git a/plugin_
From: Jan Kiszka
On AMD, exist code -1 is also a possible value, but we use it for
terminating the list of known exit reasons. This leads to EXIT_ERR
being reported for unkown ones. Fix this by using an NULL string
pointer as terminal.
Signed-off-by: Jan Kiszka
---
plugin_kvm.c | 6 +++---
1 f
Hi Oliver,
On 05/20/2016 11:43 PM, Oliver Neukum wrote:
On Fri, 2016-05-20 at 22:51 -0700, Guenter Roeck wrote:
On 05/20/2016 06:37 AM, Oliver Neukum wrote:
On Fri, 2016-05-20 at 14:24 +0300, Heikki Krogerus wrote:
On Thu, May 19, 2016 at 04:47:17PM +0200, Oliver Neukum wrote:
Please explai
Hi Uwe,
On 05/22/2016 03:10 AM, Uwe Kleine-König wrote:
Hello,
On Tue, May 17, 2016 at 09:37:11PM -0700, Guenter Roeck wrote:
[9.366256] libphy: ethoc-mdio: probed
[9.367389] (null): could not attach to PHY
[9.368555] (null): failed to probe MDIO bus
[9.371540] Unable to hand
On Sun, May 22, 2016 at 05:17:26PM +0200, Pali Rohár wrote:
> On Sunday 22 May 2016 17:04:16 Guenter Roeck wrote:
> > On 05/22/2016 04:50 AM, Pali Rohár wrote:
> > > This patch exports standard hwmon pwmX_enable sysfs attribute for
> > > enabling or disabling automatic fan control by BIOS. Standard
On Sun, May 22, 2016 at 02:26:49PM +0800, Boqun Feng wrote:
> Hi Paul,
>
> On Sat, May 21, 2016 at 10:24:22PM -0700, Paul E. McKenney wrote:
> > On Sun, May 22, 2016 at 10:36:00AM +0800, kernel test robot wrote:
> > > Greetings,
> > >
> > > 0day kernel testing robot got the below dmesg and the fi
Currently ftrace_graph_ent{,_entry} and ftrace_graph_ret{,_entry} struct
can have padding bytes at the end due to alignment in 64-bit data type.
As these data are recorded so frequently, those paddings waste
non-negligible space. As some archs can have efficient unaligned
accesses, reducing the al
On Sunday 22 May 2016 17:11:18 Guenter Roeck wrote:
> On 05/21/2016 05:31 PM, Pali Rohár wrote:
> > On Sunday 22 May 2016 02:21:46 Guenter Roeck wrote:
> >> On 05/21/2016 07:52 AM, Pali Rohár wrote:
> >>> Some Dell machines (e.g. Dell Precision M3800) have two fans,
> >>> first with index=0 and sec
On Sunday 22 May 2016 17:04:16 Guenter Roeck wrote:
> On 05/22/2016 04:50 AM, Pali Rohár wrote:
> > This patch exports standard hwmon pwmX_enable sysfs attribute for
> > enabling or disabling automatic fan control by BIOS. Standard
> > value "1" is for disabling automatic BIOS fan control and value
1 - 100 of 203 matches
Mail list logo
