On Wed 2017-02-01 14:02:43, Josh Poimboeuf wrote:
> On Thu, Jan 19, 2017 at 09:46:08AM -0600, Josh Poimboeuf wrote:
> > Here's v4, based on linux-next/master. Mostly minor changes this time,
> > primarily due to Petr's v3 comments.
>
> So far, the only review comments have been related to the
This patch allows changing labels for cgroup mounts. Previously, running
chcon on cgroupfs would throw an "Operation not supported". This patch
specifically whitelist cgroupfs.
The patch could also allow containers to write only to the systemd cgroup
for instance, while the other cgroups are kept
Having a local variable of 1024 bytes on 64-bit architectures is a bit
too much, and I ran into this warning while trying to see what functions
use the largest stack:
drivers/staging/fbtft/fbtft-sysfs.c: In function 'store_gamma_curve':
drivers/staging/fbtft/fbtft-sysfs.c:132:1: warning: the
Remove unnecessary header inclusions and reorder the remaining ones.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 21 +
1 file changed, 5 insertions(+), 16 deletions(-)
diff --git a/arch/arm/mach-at91/pm.c
Instead of having separate global variables to hold IP dresses, move them
to struct at91_pm_data.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 44 +---
1 file changed, 21 insertions(+), 23
The number of register we can safely pass to at91_pm_suspend_in_sram is
limited. Instead, pass the address to the at91_pm_data structure.
The offsets are automatically generated to avoid hardcoding them.
Signed-off-by: Alexandre Belloni
---
No that C functions are used, we can always enabled PM, putting the SDRAM
in self refresh but not disabling the main clock.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 12 +++-
arch/arm/mach-at91/pm.h | 3 +++
2 files changed, 10
Hi Nicolas,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc6]
[cannot apply to next-20170202]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Nicolas-Dichtel/uapi
gcc-7.0.1 warns about old code in ttpci:
In file included from drivers/media/pci/ttpci/av7110.c:63:0:
In function 'irdebi.isra.2',
inlined from 'start_debi_dma' at drivers/media/pci/ttpci/av7110.c:376:3,
inlined from 'gpioirq' at drivers/media/pci/ttpci/av7110.c:659:3:
The driver uses a relatively large data structure on the stack, which
showed up on my radar as we get a warning with the "latent entropy"
GCC plugin:
drivers/media/usb/pvrusb2/pvrusb2-eeprom.c:153:1: error: the frame size of 1376
bytes is larger than 1152 bytes [-Werror=frame-larger-than=]
The
On Thu, Feb 2, 2017 at 3:51 PM, Jintack Lim wrote:
> On Thu, Feb 2, 2017 at 7:31 AM, Christoffer Dall wrote:
>> Hi Jintack,
>>
>> On Wed, Feb 01, 2017 at 12:43:00PM -0500, Jintack Lim wrote:
>>> The ARM architecture defines the EL1 physical timer and
This patch adds dt-binding documentation for zx2967 family thermal sensor.
Signed-off-by: Baoyou Xie
Acked-by: Rob Herring
Reviewed-by: Shawn Guo
---
.../devicetree/bindings/thermal/zx2967-thermal.txt | 114 +
1
On Thu 2017-02-02 19:03:48, Sergey Senozhatsky wrote:
> On (02/02/17 10:07), Peter Zijlstra wrote:
> > On Thu, Feb 02, 2017 at 11:11:34AM +0900, Sergey Senozhatsky wrote:
> > > On (02/01/17 16:39), Petr Mladek wrote:
> > > [..]
> > > > I guess that you are talking about the introduction of
> > > >
This patch allows changing labels for cgroup mounts. Previously, running
chcon on cgroupfs would throw an "Operation not supported". This patch
specifically whitelist cgroupfs.
The patch could also allow containers to write only to the systemd cgroup
for instance, while the other cgroups are kept
On Friday 20 January 2017 11:47 PM, David Lechner wrote:
> On 01/20/2017 05:50 AM, Sekhar Nori wrote:
>> On Wednesday 18 January 2017 10:27 PM, David Lechner wrote:
>>> On 01/18/2017 03:50 AM, Sekhar Nori wrote:
On Saturday 14 January 2017 01:30 AM, David Lechner wrote:
> This allocates
Hi Nicolas,
[auto build test ERROR on linus/master]
[also build test ERROR on v4.10-rc6 next-20170202]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Nicolas-Dichtel/uapi-export-all-headers
On 02/01/2017 03:43 PM, Jens Axboe wrote:
> On 02/01/2017 02:40 PM, Dan Williams wrote:
>> On Wed, Feb 1, 2017 at 2:35 PM, Jens Axboe wrote:
>>> On 02/01/2017 02:05 PM, Dan Williams wrote:
Warnings of the following form occur because scsi reuses a devt number
while the
This way, upower can add a simple udev rule to decide whether or not
it should use the internal unifying support or just the generic kernel
one.
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 20
hidpp->name can't be null.
Only HID++ 2.0 and above device supports the query.
Signed-off-by: Benjamin Tissoires
---
new in v2
---
drivers/hid/hid-logitech-hidpp.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff
Simple check to add, huge improvement :)
Signed-off-by: Benjamin Tissoires
---
no changes in v2
---
drivers/hid/hid-logitech-hidpp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-logitech-hidpp.c b/drivers/hid/hid-logitech-hidpp.c
index
On Thu, Feb 02, 2017 at 02:52:57PM +0100, Johannes Stezenbach wrote:
> Nope, as I've written earlier:
> > In ProductionKernelQuilts I found
> > DC-TI-PMIC-disable-power-button-support.patch so I guess it
> > might not be needed because it's probably handled by ACPI.
>
> [ +0.000338] input: Power
Building this driver without PHYLIB fails:
ERROR: "mdio_driver_unregister" [drivers/phy/phy-bcm-nsp-usb3.ko] undefined!
ERROR: "mdio_driver_register" [drivers/phy/phy-bcm-nsp-usb3.ko] undefined!
ERROR: "mdiobus_write" [drivers/phy/phy-bcm-nsp-usb3.ko] undefined!
Unfortunately selecting PHYLIB
We get a link error when CCU_MULT is not set with the
newly added driver:
drivers/clk/sunxi-ng/ccu-sun5i.o:(.data.__compound_literal.17+0x4): undefined
reference to `ccu_mult_ops'
drivers/clk/sunxi-ng/ccu-sun5i.o:(.data.__compound_literal.5+0x4): undefined
reference to `ccu_mult_ops'
Fixes:
On Wed, 1 Feb 2017, Josh Poimboeuf wrote:
> For live patching and possibly other use cases, a stack trace is only
> useful if it can be assured that it's completely reliable. Add a new
> save_stack_trace_tsk_reliable() function to achieve that.
>
> Note that if the target task isn't the current
Putting 128 pointers on the stack is rather wasteful, in particular
on 64-bit architectures:
drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c: In function
'RxPktPendingTimeout':
drivers/staging/rtl8192u/ieee80211/rtl819x_TSProc.c:92:1: warning: the frame
size of 1072 bytes is larger than
When going to standby, there is no point calling the assembly function
at91_pm_suspend_in_sram(). It does exactly the same operations as the C
standby functions.
This allows to remove a few loads and tests in the suspend/resume path.
Signed-off-by: Alexandre Belloni
Instead of rely on the SoC type to select the memory controller type, use
the device tree ids as they are parsed anyway.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 29 +++--
1 file changed, 19 insertions(+), 10
As already explained for pm_suspend.S, the DDRSDR controller fails to put
LPDDR1 memories in self-refresh. Force the controller to think it has DDR2
memories during the self-refresh period, as the DDR2 self-refresh spec is
equivalent to LPDDR1, and is correctly implemented in the controller.
The two i2c probe functions use a lot of stack since they put
an i2c_client structure in a local variable:
drivers/media/usb/em28xx/em28xx-camera.c: In function
'em28xx_probe_sensor_micron':
drivers/media/usb/em28xx/em28xx-camera.c:205:1: error: the frame size of 1256
bytes is larger than 1152
The cx231xx_do_i2c_scan function needs a lot of stack because
it puts an i2c_client structure on it:
drivers/media/usb/cx231xx/cx231xx-i2c.c: In function 'cx231xx_do_i2c_scan':
drivers/media/usb/cx231xx/cx231xx-i2c.c:518:1: error: the frame size of 1248
bytes is larger than 1152 bytes
mxl111sf uses a lot of kernel stack memory as it puts an i2c_client
structure on the stack:
drivers/media/usb/dvb-usb-v2/mxl111sf.c: In function 'mxl111sf_init':
drivers/media/usb/dvb-usb-v2/mxl111sf.c:953:1: error: the frame size of 1248
bytes is larger than 1152 bytes
On 2017-02-01 11:34, Rob Herring wrote:
On Tue, Jan 31, 2017 at 09:43:56AM -0600, eaja...@linux.vnet.ibm.com
wrote:
From: "Edward A. James"
Add code to tie the hwmon sysfs code and the POWER8 OCC code together,
as
well as probe the entire driver from the I2C bus. I2C is
Hi,
On 02-02-17 16:01, Andy Shevchenko wrote:
On Thu, Feb 2, 2017 at 4:45 PM, Hans de Goede wrote:
Hi,
On 02-02-17 15:25, Arnd Bergmann wrote:
The new driver cannot be a loadable module, so if I2C is loadable, we get
this
link error:
drivers/platform/built-in.o: In
On Thu, Feb 2, 2017 at 5:10 PM, Hans de Goede wrote:
> On 02-02-17 16:01, Andy Shevchenko wrote:
>> On Thu, Feb 2, 2017 at 4:45 PM, Hans de Goede wrote:
>>> Thank you.
>>>
>>> Acked-by: Hans de Goede
>>
>>
>> I'm a bit confused
Hi Bjorn,
Thanks for the patch!
On 01/30/2017 06:55 PM, Bjorn Andersson wrote:
> Pushing the SCM calls into the MDT loader reduces duplication in the
> callers and allows for non-remoteproc clients to use the helper for
> parsing and loading MDT files.
>
> Cc: Andy Gross
This is a patch to fix "WARNING: line over 80 characters" found by
checkpatch.pl in vvp_page.c.
Signed-off-by: Zhengyi Shen
---
drivers/staging/lustre/lustre/llite/vvp_page.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
On Thu, Feb 2, 2017 at 5:22 PM, Michal Hocko wrote:
> On Thu 02-02-17 16:55:49, vinayak menon wrote:
>> On Thu, Feb 2, 2017 at 4:18 PM, Michal Hocko wrote:
>> > On Thu 02-02-17 11:44:22, Michal Hocko wrote:
>> >> On Tue 31-01-17 14:32:08, Vinayak Menon
On Thu, Feb 2, 2017 at 9:06 AM, eajames wrote:
> On 2017-02-01 11:34, Rob Herring wrote:
>>
>> On Tue, Jan 31, 2017 at 09:43:56AM -0600, eaja...@linux.vnet.ibm.com
>> wrote:
>>>
>>> From: "Edward A. James"
>>>
>>> Add code to tie the hwmon sysfs
On Thu, Jan 26, 2017 at 02:41:28PM -0500, Boris Ostrovsky wrote:
> Make sure they don't use these devices since they are not emulated
> for unprivileged PVH guest.
This description seems weird for what it's actually done. AFAICT you are not
really preventing the guest from using the PIC or the IO
On Thu, Feb 02, 2017 at 01:10:54PM +0100, Borislav Petkov wrote:
> Now on to run the same thing on a bigger bulldozer.
It looks differently on the bigger box:
before:
Performance counter stats for 'make -s -j17 bzImage' (3 runs):
1333240.579196 task-clock (msec) #9.271
On Thu, Feb 02, 2017 at 04:42:43PM +0100, Johannes Stezenbach wrote:
> On Thu, Feb 02, 2017 at 05:02:12PM +0200, Mika Westerberg wrote:
> > OK, I guess it is easier if I just order one of those machines here and
> > figure out how to get the PMIC driver working.
>
> Oh, I assumed the bottleneck
On Thu 02-02-17 21:00:10, vinayak menon wrote:
> On Thu, Feb 2, 2017 at 5:22 PM, Michal Hocko wrote:
> > On Thu 02-02-17 16:55:49, vinayak menon wrote:
> >> On Thu, Feb 2, 2017 at 4:18 PM, Michal Hocko wrote:
> >> > On Thu 02-02-17 11:44:22, Michal Hocko
On Thu 2017-02-02 09:34:09, Steven Rostedt wrote:
> On Thu, 2 Feb 2017 11:02:57 +0900
> Sergey Senozhatsky wrote:
>
> > On (02/01/17 11:37), Steven Rostedt wrote:
> > > This looks fine, but I'm curious if you tested it. That is, added a
> > > bunch of printks
> case PR_GET_FP_MODE:
> error = GET_FP_MODE(me);
> break;
> +#ifdef CONFIG_TASK_ISOLATION
> + case PR_SET_TASK_ISOLATION:
> + error = task_isolation_set(arg2);
> + break;
> + case PR_GET_TASK_ISOLATION:
> + error =
On Thu, Feb 02, 2017 at 10:18:12AM -0600, Bjorn Helgaas wrote:
> PCI fixes:
>
> - configure ASPM on the link from a PCI-to-PCIe bridge (avoids a NULL
> pointer dereference on topologies including these bridges)
Any reason you didn't include the affinity use outside the allocate
range fix
On 02/02/2017 02:19 AM, Paolo Valente wrote:
> The scheme is clear. One comment, in case it could make sense and
> avoid more complexity: since put_rq_priv is invoked in two different
> contexts, process or interrupt, I didn't feel so confusing that, when
> put_rq_priv is invoked in the context
On Tue, 31 Jan 2017, Thierry Reding wrote:
> On Tue, Jan 31, 2017 at 10:15:10AM -0800, Eric Anholt wrote:
>> I would love for drm-panel to be moved under -misc.
>
> Like that's going to magically motivate people to spend their time
> reviewing other patches. The only
Le 02/02/2017 à 15:47, kbuild test robot a écrit :
> Hi Nicolas,
>
> [auto build test ERROR on linus/master]
> [also build test ERROR on v4.10-rc6]
> [cannot apply to next-20170202]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve
On 2 February 2017 at 15:43, Laura Abbott wrote:
> On 02/02/2017 01:17 AM, Ard Biesheuvel wrote:
>> On 1 February 2017 at 21:50, Laura Abbott wrote:
>>> On 02/01/2017 09:36 AM, Ard Biesheuvel wrote:
On 1 February 2017 at 16:58, Laura Abbott
hiya,
Removing this method makes the diff to FreeBSD larger, as "vif" in
FreeBSD is a different pointer.
(Yes, I have ath10k on freebsd working and I'd like to find a way to
reduce the diff moving forward.)
-adrian
On 02/02/2017 10:35 AM, Roger Pau Monné wrote:
> On Thu, Jan 26, 2017 at 02:41:28PM -0500, Boris Ostrovsky wrote:
>> Make sure they don't use these devices since they are not emulated
>> for unprivileged PVH guest.
> This description seems weird for what it's actually done. AFAICT you are not
>
The issue is described here, with a nice testcase:
https://bugzilla.kernel.org/show_bug.cgi?id=192931
The problem is that shmat() calls do_mmap_pgoff() with MAP_FIXED, and
the address rounded down to 0. For the regular mmap case, the protection
mentioned above is that the kernel gets to
On 02/02/2017 01:17 AM, Ard Biesheuvel wrote:
> On 1 February 2017 at 21:50, Laura Abbott wrote:
>> On 02/01/2017 09:36 AM, Ard Biesheuvel wrote:
>>> On 1 February 2017 at 16:58, Laura Abbott wrote:
On 10/19/2016 09:22 AM, Will Deacon wrote:
> On
On Thu, Feb 02, 2017 at 05:02:12PM +0200, Mika Westerberg wrote:
> OK, I guess it is easier if I just order one of those machines here and
> figure out how to get the PMIC driver working.
Oh, I assumed the bottleneck is developer time, not lack of hardware...
> Is the model Asus E200HA?
Hi Baoyou,
This version looks better - just a couple of comments below on things I didn't
notice before.
On Thu, Feb 02, 2017 at 05:16:35PM +0800, Baoyou Xie wrote:
> This patch adds watchdog controller driver for ZTE's zx2967 family.
>
> Signed-off-by: Baoyou Xie
> ---
We need this patch set to tighten security inside of containers to only
allow certain directories in the cgroup file system to be used by the
containers. In order to make this work, SELinux policy also needs to be
modified.
On 02/02/2017 10:22 AM, Antonio Murdaca wrote:
> This patch allows
On Tue, Jan 31, 2017 at 1:36 AM, Peter Rosin wrote:
> On 2017-01-30 18:20, Rob Herring wrote:
>> On Sat, Jan 28, 2017 at 4:42 PM, Peter Rosin wrote:
>>> On 2017-01-27 20:39, Rob Herring wrote:
On Wed, Jan 18, 2017 at 04:57:10PM +0100, Peter Rosin wrote:
* Borislav Petkov wrote:
> On Thu, Feb 02, 2017 at 01:10:54PM +0100, Borislav Petkov wrote:
> > Now on to run the same thing on a bigger bulldozer.
>
> It looks differently on the bigger box:
>
> before:
>
> Performance counter stats for 'make -s -j17 bzImage' (3 runs):
>
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Thursday, February 2, 2017 7:11 AM
>
> Context switches have dropped, cache misses are the same and we have a
> rise in cpu-migrations. That last bit is interesting and I don't have an
> answer yet. Maybe peterz
PCI fixes:
- configure ASPM on the link from a PCI-to-PCIe bridge (avoids a NULL
pointer dereference on topologies including these bridges)
The following changes since commit 4d191b1b63c209e37bf27938ef365244d3c41084:
PCI/MSI: pci-xgene-msi: Fix CPU hotplug registration handling
Mathieu Poirier writes:
> If this is what you want to convey then
>
> + * @action:filter/start/stop
>
> needs to be fixed. This can be interpreted as "use range filter,
> start filter or stop filter" - which is exactly what I did. Something
> like
I was
On Thu, Feb 2, 2017 at 4:01 PM, Gary Tierney wrote:
> On Thu, Feb 02, 2017 at 03:42:28PM +0100, Antonio Murdaca wrote:
>> This patch allows changing labels for cgroup mounts. Previously, running
>> chcon on cgroupfs would throw an "Operation not supported". This patch
>>
On Thu, 2017-02-02 at 09:52 -0500, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
>config RESET_ZX2967
> bool "ZTE ZX2967 Reset Driver
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets remove the couple
On Thu 2017-02-02 15:05:38, Sergey Senozhatsky wrote:
> On (02/01/17 11:06), Steven Rostedt wrote:
> [..]
> > > static void printk_safe_flush_line(const char *text, int len)
> > > {
> > > /*
> > > - * The buffers are flushed in NMI only on panic. The messages must
> > > - * go only into the
+Linus W
On Thu, Feb 2, 2017 at 3:19 AM, Fabrice Gasnier wrote:
> On 02/01/2017 05:35 PM, Rob Herring wrote:
>>
>> On Mon, Jan 30, 2017 at 02:57:41PM +0100, Fabrice Gasnier wrote:
>>>
>>> Add dt documentation for st,stm32-exti-trigger.
>>> EXTi gpio signal can be routed
On Thu 2017-02-02 16:37:53, Petr Mladek wrote:
> On Thu 2017-02-02 15:05:38, Sergey Senozhatsky wrote:
> > On (02/01/17 11:06), Steven Rostedt wrote:
> > [..]
> > > > static void printk_safe_flush_line(const char *text, int len)
> > > > {
> > > > /*
> > > > -* The buffers are
On Tue, Jan 31, 2017 at 10:22:47AM -0700, Ross Zwisler wrote:
> On Tue, Jan 31, 2017 at 4:48 AM, Mike Galbraith wrote:
> > On Tue, 2017-01-31 at 16:30 +0530, Sachin Sant wrote:
Could some of you test this? It seems to cure things in my (very)
limited testing.
---
diff --git
On Thu, 2017-02-02 at 11:58 +0100, Dmitry Vyukov wrote:
> On Wed, Feb 1, 2017 at 7:45 PM, Tim Chen wrote:
> >
> > On Tue, Jan 31, 2017 at 02:16:31PM +0100, Dmitry Vyukov wrote:
> > >
> > > Hello,
> > >
> > > I am getting the following reports with low frequency
Helllo Baoyou,
Sorry I was not clear enough in my previous comment.
Please find the explanation below:
On Thu, Feb 02, 2017 at 11:08:06PM +0800, Baoyou Xie wrote:
> This patch adds thermal driver for ZTE's zx2967 family.
>
> +
> +static int zx2967_thermal_probe(struct platform_device
On 02/02/2017 09:54 AM, Ross Lagerwall wrote:
> On 02/01/2017 06:54 PM, Boris Ostrovsky wrote:
>> On 02/01/2017 10:50 AM, Ross Lagerwall wrote:
>>> Improve error handling during initialization. This fixes a crash when
>>> running out of grant refs when creating many queues across many
>>> netdevs.
On 1 February 2017 at 22:59, Jeffrey Hugo wrote:
> On 2/1/2017 2:08 PM, Jeffrey Hugo wrote:
>>
>> On 2/1/2017 10:45 AM, Ard Biesheuvel wrote:
>>>
>>> Some AArch64 UEFI implementations disable the MMU in ExitBootServices(),
>>> after which unaligned accesses to RAM are no
Em Thu, Feb 02, 2017 at 02:40:48PM +0100, Ingo Molnar escreveu:
> * Ravi Bangoria wrote:
> > After patch:
> > $ perf record -e sdt_glib:main__after_check
> > event syntax error: 'sdt_glib:idle__add'
> > \___ unknown tracepoint
> >
* Ghannam, Yazen wrote:
> Here are my results on a 32C Bulldozer system with an SSD. Also, I use ccache
> so
> I added "ccache -C" in the pre-build script so the cache gets cleared.
>
> Before:
> Performance counter stats for 'make -s -j65 bzImage' (3 runs):
>
>
Peter Zijlstra:
> Does something like the below work better? The annotation in
> downgrade_write() would look something like:
>
> + lock_downgrade(>dep_map, 1, _RET_IP_);
>
> Not even compile tested and lacks the !LOCKDEP build bits.
Thanks for the patch.
It seems working expectedly. I began
* Shuah Khan wrote:
> On 02/02/2017 04:45 PM, Dave Hansen wrote:
> > On 02/02/2017 03:36 PM, Shuah Khan wrote:
> >> This patches is already in linux-kselftest next for 4.11
> >>
> >> Is there a reason why you chose to resend these.
> >
> > Oh, my apologies! I didn't
On 2017年01月27日 16:16, Christoph Hellwig wrote:
Signed-off-by: Christoph Hellwig
---
Reviewed-by: Jason Wang
drivers/virtio/virtio_pci_common.c | 5 ++---
drivers/virtio/virtio_pci_common.h | 2 --
drivers/virtio/virtio_pci_legacy.c | 2 +-
On 2017年01月27日 16:16, Christoph Hellwig wrote:
We don't really need struct virtio_pci_vq_info, as most field in there
are redundant:
- the vq backpointer is not strictly neede to start with
- the entry in the vqs list is not needed - the generic virtqueue already
has list, we only
On Wed, Feb 01, 2017 at 04:29:50PM +, Marc Zyngier wrote:
> On 27/01/17 18:07, Will Deacon wrote:
> > The SPE buffer is virtually addressed, using the page tables of the CPU
> > MMU. Unusually, this means that the EL0/1 page table may be live whilst
> > we're executing at EL2 on non-VHE
On Thu, 2017-02-02 at 23:28 +0530, Arushi wrote:
> This patch fixes the issue by aligning the * on each line in block comments.
> [Patch v1] is rejected as the changes done is not following the linux
> coding style and [Patch v2] is rejected because forgot to mention the
> cause of rejection of
From: Serge Semin
> +static void idt_nt_write(struct idt_ntb_dev *ndev,
> + const unsigned int reg, const u32 data)
> +{
> + /*
> + * It's obvious bug to request a register exceeding the maximum possible
> + * value as well as to have it unaligned.
> + */
>
On 02/02/17 18:18, Will Deacon wrote:
> On Wed, Feb 01, 2017 at 04:29:50PM +, Marc Zyngier wrote:
>> On 27/01/17 18:07, Will Deacon wrote:
>>> The SPE buffer is virtually addressed, using the page tables of the CPU
>>> MMU. Unusually, this means that the EL0/1 page table may be live whilst
>>>
On Thu, Feb 02, 2017 at 07:03:41PM +0100, Dmitry Vyukov wrote:
> On Thu, Feb 2, 2017 at 6:55 PM, Greg Kroah-Hartman
> wrote:
> > On Thu, Feb 02, 2017 at 06:48:48PM +0100, Dmitry Vyukov wrote:
> >> Hello,
> >>
> >> Syzkaller fuzzer started crashing kernel with the
On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
> Hello,
>
> Please consider reverting commit
> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
What release can I remove it from?
It isn't in 4.4.y, and 4.9.y doesn't make much sense, unless it's
reverted in
On 02/02/2017 09:56 AM, Russell King - ARM Linux wrote:
On Thu, Feb 02, 2017 at 05:22:46PM +, Russell King - ARM Linux wrote:
I thought, maybe, it's the IPU overwriting past the end of the buffer,
but I've added checks and that doesn't seem to have fired. I also
wondered if it was some
On Thu, Feb 02, 2017 at 03:48:17PM +0100, Jan Kara wrote:
> > * ->page_mkwrite() instances sometimes return VM_FAULT_RETRY; AFAICS,
> > it's only (ab)used there as 'not zero, but doesn't contain any error bits';
> > VM_FAULT_RETRY from that source does *not* reach handle_mm_fault() callers,
>
On Thu, Feb 02 2017 at 12:58pm -0500,
Randy Dunlap wrote:
> On 02/01/17 23:21, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20170201:
> >
>
> on x86_64:
>
> drivers/built-in.o: In function `dm_blk_ioctl':
> dm.c:(.text+0x1a5121): undefined reference to
Hi,
On top of previous pull request.
Best regards,
Krzysztof
The following changes since commit dfaf06baad0c088a55570f7a324949c498f2106c:
ARM: dts: exynos: Fix indentation of EHCI and OHCI ports (2017-01-29 21:03:46
+0200)
are available in the git repository at:
Hi,
Minor improvements of PM domain driver.
Best regards,
Krzysztof
The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88:
Linux 4.10-rc2 (2017-01-01 14:31:53 -0800)
are available in the git repository at:
Hi,
This includes clk-v4.11-samsung-dphy tag from Sylwester (clock) and a pinctrl
header acked by Linus pinctrl header. The header goes through my tree but I
provided
a separate tag also for Linus.
On top of previous pull request.
Best regards,
Krzysztof
The following changes since commit
Hi,
There was still some activity these days so I pushed to you second round of
updates a little bit earlier. I wanted to be sure it gets in and also make room
for new patches. These are the late commits but some of them were in a review
for quite long.
1. No conflicts expected.
2. Almost
On Thu, Feb 02, 2017 at 05:30:34PM +0200, Jani Nikula wrote:
> On Tue, 31 Jan 2017, Thierry Reding wrote:
> > On Tue, Jan 31, 2017 at 10:15:10AM -0800, Eric Anholt wrote:
> >> I would love for drm-panel to be moved under -misc.
> >
> > Like that's going to magically
This patch fixes the issue by aligning the * on each line in block comments.
Signed-off-by: Arushi
---
drivers/staging/speakup/fakekey.c| 10 +-
drivers/staging/speakup/i18n.c | 14 +++---
drivers/staging/speakup/main.c
On Thu 2017-02-02 12:53:47, Sergey Senozhatsky wrote:
> Hello,
>
> thanks for taking a look, Petr.
>
> On (01/25/17 16:02), Petr Mladek wrote:
> [..]
> > > Signed-off-by: Sergey Senozhatsky
> > > ---
> > > kernel/printk/printk.c | 11 ++-
> > > 1 file
From: Djalal Harouni
This adds the Timgad module. Timgad allows to apply restrictions on
which task is allowed to load or unload kernel modules. Auto-load module
feature is also handled. The settings can also be applied globally using
a sysctl interface, this allows to complete
On Thu, Feb 02, 2017 at 11:30:19AM -0500, Boris Ostrovsky wrote:
> On 02/02/2017 10:35 AM, Roger Pau Monné wrote:
> > On Thu, Jan 26, 2017 at 02:41:28PM -0500, Boris Ostrovsky wrote:
> >> Make sure they don't use these devices since they are not emulated
> >> for unprivileged PVH guest.
> > This
From: Djalal Harouni
Hi list,
This RFC introduces Timgad a Linux Security Module that adds restrictions
on module load and unload operations. The original idea and inspiration is
from grsecurity 'GRKERNSEC_MODHARDEN'. However this was adapted to fit
more as an LSM and also to
On Thu, Feb 02, 2017 at 05:09:16PM +0100, Ingo Molnar wrote:
> If there's any doubt about the validity of the measurement I'd suggest doing:
>
> perf stat -a --sync --repeat 3 ...
>
> ... so that there's no perf overhead and skew from the many processes of a
> kernel
> build workload,
On February 2, 2017 8:48:30 AM PST, Andy Shevchenko
wrote:
>On Thu, 2017-02-02 at 08:39 -0800, Dmitry Torokhov wrote:
>> From: Dmitry Torokhov
>>
>> Data that is fed into property arrays should not be modified, so
>let's
>> mark
>>
On Thu, 02 Feb 2017 20:50:48 +1100
Michael Ellerman wrote:
> Michael Ellerman writes:
>
> > Currently the kconfig logic for VFIO_IOMMU_SPAPR_TCE and VFIO_SPAPR_EEH
> > is broken when SPAPR_TCE_IOMMU=n. Leading to:
> >
> > warning: (VFIO) selects
A typical SMP system expects cache coherency. Initial NPS platform
support was slated to be SMP w/o cache coherency.
However it seems the platform now selects that option, so there is no
point in keeping it around.
Signed-off-by: Vineet Gupta
---
arch/arc/Kconfig
601 - 700 of 1530 matches
Mail list logo