On Fri, Dec 01, 2017 at 09:24:50AM +0800, Yixun Lan wrote:
> From: Qiufang Dai
>
> Add the required header for the clocks ID dt-bindings
> exported from various subsystem in the Meson-AXG SoC.
>
> Signed-off-by: Qiufang Dai
> Signed-off-by: Yixun Lan
> ---
> include/dt-bindings/clock/axg-clkc
On Mon, Dec 4, 2017 at 1:18 PM, Arnd Bergmann wrote:
> On Mon, Dec 4, 2017 at 9:36 PM, Deepa Dinamani wrote:
>> On Mon, Dec 4, 2017 at 6:21 AM, Arnd Bergmann wrote:
>>> On Mon, Dec 4, 2017 at 1:55 AM, Deepa Dinamani
>>> wrote:
struct timeval which is part of struct input_event to
mai
On Fri, Dec 01, 2017 at 11:43:09AM +0530, Vignesh R wrote:
> Update device tree binding documentation of TI's dra7xx PCI controller
> for enabling unaligned mem access as applicable not just in EP mode but
> in host mode as well.
>
> Signed-off-by: Vignesh R
> ---
> Documentation/devicetree/bind
Hi Sven,
On Mon, Dec 04, 2017 at 10:36:18AM -0500, Sven Van Asbroeck wrote:
> From: Sven Van Asbroeck
>
> Some multi-address eeproms in the at24 family may not automatically
> roll-over reads to the next slave address. On those eeproms, reads
> that straddle slave boundaries will not work correc
Hello, Tejun,
On 04.12.2017 23:07, Tejun Heo wrote:
> On Mon, Dec 04, 2017 at 07:12:51PM +0300, Kirill Tkhai wrote:
>> this patch set introduces accounting aio_nr and aio_max_nr per blkio cgroup.
>> It may be used to limit number of aio requests, which are available for
>> a cgroup, and could be u
On Mon, Dec 04, 2017 at 01:28:45PM -0800, Kees Cook wrote:
> On Mon, Dec 4, 2017 at 1:22 PM, Tobin C. Harding wrote:
> > Advice about what to use as a unique identifier is no longer valid since
> > patch series was merged to hash pointers printed with %p. We can use
> > this as a unique identifier
To increase the readability of the register accesses, the abstraction
of the helpers was increased from simple read and write to set bit,
clear bit and read modify write bit.
Annotation: This patch contains a lot of long lines and camel case
var names. These long lines and camel case vars weren't
Hello, Michael.
On Mon, Dec 04, 2017 at 10:35:13PM +0100, Michael Kerrisk (man-pages) wrote:
> I was trying to do some simple testing ot the CPU controller
> that is merged into 4.15, and ran immediately into some confusion.
> In the root cgroup on a freshly booted 4.150-rc1, I try the following:
On 05.12.2017 00:35, Jeff Moyer wrote:
> Kirill Tkhai writes:
>
>> Hi, Benjamin,
>>
>> On 04.12.2017 19:52, Benjamin LaHaise wrote:
>>> Hi Kirill,
>>>
>>> On Mon, Dec 04, 2017 at 07:12:51PM +0300, Kirill Tkhai wrote:
Hi,
this patch set introduces accounting aio_nr and aio_max_nr pe
On Fri, Dec 01, 2017 at 01:07:06PM +0100, Matthias Brugger wrote:
> The ethsys registers a reset controller, so we need to specify a
> reset cell. This patch fixes the documentation.
>
> Signed-off-by: Matthias Brugger
> ---
> Documentation/devicetree/bindings/arm/mediatek/mediatek,ethsys.txt |
On Fri, Dec 01, 2017 at 07:02:23PM +0200, Georgi Djakov wrote:
> Update the binding documentation for APCS to mention that the APCS
> hardware block also expose a clock controller functionality.
>
> The APCS clock controller is a mux and half-integer divider. It has the
> main CPU PLL as an input
On Mon, Dec 4, 2017 at 1:44 PM, Tobin C. Harding wrote:
> On Mon, Dec 04, 2017 at 01:28:45PM -0800, Kees Cook wrote:
>> On Mon, Dec 4, 2017 at 1:22 PM, Tobin C. Harding wrote:
>> > Advice about what to use as a unique identifier is no longer valid since
>> > patch series was merged to hash pointe
The following changes since commit
4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the Git repository at:
git://git.lwn.net/linux.git tags/docs-4.15-fixes
for you to fetch changes up to 9956cfef3409177d9e24ea4b7910148a18073a6f:
Docume
Hello, Kirill.
On Tue, Dec 05, 2017 at 12:44:00AM +0300, Kirill Tkhai wrote:
> > Can you please explain how this is a fundamental resource which can't
> > be controlled otherwise?
>
> Currently, aio_nr and aio_max_nr are global. In case of containers this
> means that a single container may occup
Hi,
Am Montag, 4. Dezember 2017, 08:08:31 CET schrieb Doug Anderson:
> On Sun, Dec 3, 2017 at 11:46 PM, Heiko Stübner wrote:
> > Am Montag, 4. Dezember 2017, 10:47:08 CET schrieb Chris Zhong:
> >> On 2017年12月02日 05:58, Heiko Stuebner wrote:
> >> > Am Freitag, 1. Dezember 2017, 13:42:46 CET schrie
crtc_state is being null checked in a previous code block, which implies
that such pointer might be null.
crtc_state is dereferenced in drm_atomic_helper_check_plane_state, hence
there is a potential null pointer dereference.
Fix this by warning-on and returning -EINVAL in case crtc_state is null
On Mon, Dec 04, 2017 at 10:52:15AM -0800, Paul E. McKenney wrote:
> On Mon, Dec 04, 2017 at 03:38:56PM +, David Howells wrote:
> > Paul E. McKenney wrote:
> >
> > > - Q = READ_ONCE(P); smp_read_barrier_depends(); D = READ_ONCE(*Q);
> > > + Q = READ_ONCE(P); D = READ_ONCE(*Q);
> > >
> > >
On Sat, Dec 2, 2017 at 5:27 AM, Sinan Kaya wrote:
> OF has of_device_get_match_data() function to extract driver specific data
> structure. Add a similar function for ACPI.
>
> Signed-off-by: Sinan Kaya
Haven't I ACKed this already?
Anyway, please resend the whole series with a CC to linux-acpi
Hi Geert,
My 2 cents:
2017-12-04 10:17 GMT+01:00 Geert Uytterhoeven :
>> EEPROMs using 9 address bits are common (e.g. M95040, 25AA040/25LC040).
>> Do EEPROMs using 17 or 25 address bits, as mentioned in
>> include/linux/spi/eeprom.h, really exist?
>> Or should we just limit it to a single odd va
On Mon, Dec 04, 2017 at 01:38:01PM -0800, Deepa Dinamani wrote:
> On Mon, Dec 4, 2017 at 1:18 PM, Arnd Bergmann wrote:
> > On Mon, Dec 4, 2017 at 9:36 PM, Deepa Dinamani
> > wrote:
> >> On Mon, Dec 4, 2017 at 6:21 AM, Arnd Bergmann wrote:
> >>> On Mon, Dec 4, 2017 at 1:55 AM, Deepa Dinamani
>
On 12/4/2017 4:59 PM, Rafael J. Wysocki wrote:
> On Sat, Dec 2, 2017 at 5:27 AM, Sinan Kaya wrote:
>> OF has of_device_get_match_data() function to extract driver specific data
>> structure. Add a similar function for ACPI.
>>
>> Signed-off-by: Sinan Kaya
>
> Haven't I ACKed this already?
>
> A
On Mon, Dec 4, 2017 at 3:32 PM, Moritz Fischer wrote:
> On Wed, Nov 15, 2017 at 02:51:48PM -0600, Alan Tull wrote:
>> Part of patchset that changes the following fpga_*_register
>> functions to not set drvdata:
>> * fpga_region_register.
>> * fpga_mgr_register
>> * fpga_bridge_register
>>
>> The r
On Sun, Dec 03, 2017 at 08:43:47PM +0100, Wolfram Sang wrote:
> > It's a bit different in that it's much more likely that a SPI controller
> > will actually do DMA than an I2C one since the speeds are higher and
> > there's frequent applications that do large transfers so it's more
> > likely that
Hallo
someone and I got an regression with e1000e since kernel 4.14.3 and it
seems there is 4.14.4 on the way without a fix.
bug report is here:
https://bugzilla.kernel.org/show_bug.cgi?id=198047
--
Greeting
Ronald
Commit-ID: b1cbacc8663a4dce62e4ae501e859c82f4aeb1ca
Gitweb: https://git.kernel.org/tip/b1cbacc8663a4dce62e4ae501e859c82f4aeb1ca
Author: Prarit Bhargava
AuthorDate: Mon, 4 Dec 2017 11:45:21 -0500
Committer: Thomas Gleixner
CommitDate: Mon, 4 Dec 2017 23:03:48 +0100
x86/smpboot: Do not u
Commit-ID: 866a79a1c98c5004a410122b06f808152f2fe53c
Gitweb: https://git.kernel.org/tip/866a79a1c98c5004a410122b06f808152f2fe53c
Author: Tom Lendacky
AuthorDate: Thu, 30 Nov 2017 16:46:40 -0600
Committer: Thomas Gleixner
CommitDate: Mon, 4 Dec 2017 23:03:29 +0100
x86/microcode/AMD: Add
On Fri, Dec 01, 2017 at 11:27:38PM -0500, Sinan Kaya wrote:
> A new version of the HIDMA IP has been released with bug fixes. Bumping the
> hardware version to differentiate from others.
>
> Signed-off-by: Sinan Kaya
> ---
> Documentation/devicetree/bindings/dma/qcom_hidma_mgmt.txt | 4 ++--
> 1
On Mon, Dec 04, 2017 at 10:54:48PM +0100, Peter Zijlstra wrote:
> On Mon, Dec 04, 2017 at 10:52:15AM -0800, Paul E. McKenney wrote:
> > On Mon, Dec 04, 2017 at 03:38:56PM +, David Howells wrote:
> > > Paul E. McKenney wrote:
> > >
> > > > - Q = READ_ONCE(P); smp_read_barrier_depends();
On Sat, Nov 25, 2017 at 01:24:44AM +0900, Masahiro Yamada wrote:
> To use a GPIO line for card detection, TMIO_MMC_USE_GPIO_CD is set
> by a legacy board (arch/sh/boards/mach-ecovec24).
>
> For DT platforms, the "cd-gpios" property is a legitimate way for that
> in case the IP-builtin card detecti
On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
> From: Dave Hansen
>
> If changing the page tables in such a way that an invalidation of all
> contexts (aka. PCIDs / ASIDs) is required, they can be actively invalidated
> by:
>
> 1. INVPCID for each PCID (works for single pages too).
>
>
> If this is truly specific to at24, then vendor prefix would be appropriate,
> plus it'd go to an at24 specific binding file. However if it isn't I'd just
> remove the above sentence. I guess the latter?
Yes, no-read-rollover is truly specific to at24.c, because it applies only
to i2c multi-addre
On Mon, Dec 04, 2017 at 01:05:51PM -0500, Sinan Kaya wrote:
> On 12/4/2017 11:23 AM, Rob Herring wrote:
> > On Fri, Dec 1, 2017 at 10:27 PM, Sinan Kaya wrote:
> >> Now that we have a get_match_data() callback as part of the firmware node,
> >> implement the OF specific piece for it.
> >>
> >> Sign
On Sunday, December 3, 2017 5:22:56 PM CET Linus Torvalds wrote:
> It's Sunday, but a few hours earlier than usual, since I'm on the east
> coast, three hours ahead of my normal release schedule.
>
> It's a slightly bigger rc2 than I would have wished for, but this
> early in the release process I
On Mon, Dec 4, 2017 at 6:08 AM, Thomas Gleixner wrote:
> From: Dave Hansen
>
> This uses INVPCID to shoot down individual lines of the user mapping
> instead of marking the entire user map as invalid. This
> could/might/possibly be faster.
>
> This for sure needs tlb_single_page_flush_ceiling to
Commit-ID: 2ee90363a838cf41ebf1ad24bad274762e467d8d
Gitweb: https://git.kernel.org/tip/2ee90363a838cf41ebf1ad24bad274762e467d8d
Author: Rafael J. Wysocki
AuthorDate: Fri, 1 Dec 2017 15:08:12 +0100
Committer: Thomas Gleixner
CommitDate: Mon, 4 Dec 2017 23:20:35 +0100
x86 / PCI: Make bro
Hello,
thanks for the feedback, is that better ?
No need to get into the submenu to disable all SSB-related
config entries.
This makes it easier to disable all SSB config options
without entering the submenu. It will also enable one
to see that en/dis-abled state from the outside menu.
This is only intended to change menuconfig UI, not change
t
On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
> From: Dave Hansen
>
> Add the pagetable helper functions do manage the separate user space page
> tables.
>
> [ tglx: Split out from the big combo kaiser patch ]
> +/*
> + * Take a PGD location (pgdp) and a pgd value that needs to be set t
[1.501264] BUG: unable to handle kernel NULL pointer dereference at
6714cfcb
[1.502335] IP: rxrpc_release+0xd5/0x1c0
[1.502865] PGD 0 P4D 0
[1.503210] Oops: [#1] SMP
[1.503589] Modules linked in:
[1.503898] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 4.15.0-rc2+
On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
> From: Dave Hansen
>
> Clone the ESPFIX alias mapping area so the entry/exit code has access to it
> even with the user space page tables.
>
> [ tglx: Remove the per cpu user mapped oddity ]
>
> Signed-off-by: Dave Hansen
> Signed-off-by: T
On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
> From: Andy Lutomirski
>
> XXX: Whenever we settle how KERNEL_PAGE_TABLE_ISOLATION gets turned on
> and off, we should do the same to this.
This is done now :)
On Sat, Dec 02, 2017 at 10:15:33PM -0500, Keno Fischer wrote:
> This is exactly the discussion I want to generate, so thank you.
> I should point out that I'm not advocating for anything other
> than clarity of what kernel behavior user space may assume.
I don't think we tend to document short-liv
On Sat, Dec 02, 2017 at 12:23:09PM +0100, Linus Walleij wrote:
> The Gemini pin controller can set drive strength for a few
> select groups of pins (not individually). Implement this
> for GMAC0 and 1 (ethernet ports), IDE and PCI.
>
> Cc: devicet...@vger.kernel.org
> Signed-off-by: Linus Walleij
On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
> From: Thomas Gleixner
>
> LDT is not really commonly used on 64bit so the overhead of populating the
> fixmap entries on context switch for the rare LDT syscall users is a
> reasonable trade off vs. having extra dynamically managed mapping
On Thu, Nov 30, 2017 at 10:35:57AM -0600, Bjorn Helgaas wrote:
> From: Bjorn Helgaas
>
> When a process uses sysfs and tries to mmap more space than is available in
> a PCI BAR, we emit a warning and a backtrace. The mmap fails anyway, so
> the backtrace is mainly for debugging. But in general
On Mon, Dec 4, 2017 at 6:08 AM, Thomas Gleixner wrote:
> From: Dave Hansen
>
> The KERNEL_PAGE_TABLE_ISOLATION code attempts to "poison" the user
> portion of the kernel page tables. It detects entries that it wants that it
> wants to poison in two ways:
>
> * Looking for addresses >= PAGE_OFFSE
On 12/04/2017 02:22 PM, Andy Lutomirski wrote:
>> +
>> + this_cpu_write(cpu_tlbstate.invalidate_other, true);
>
> Why do we need this extra variable instead of just looping over all
> other ASIDs and invalidating them? It would be something like:
>
> for (i = 1; i < TLB_NR_DYN_ASID
On Sun, Dec 03, 2017 at 02:27:20PM +0100, Jacek Anaszewski wrote:
> Dan,
>
> On 12/01/2017 05:56 PM, Dan Murphy wrote:
> > Update the lp8860 dt binding to the LED standard where
> > the LED should have a child node and also adding a
> > LED trigger entry.
> >
> > Signed-off-by: Dan Murphy
> > --
On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki wrote:
>
> So far, resume from suspend-to-RAM (ACPI S3) is broken on all of the
> systems I have tested, so it is probably safe to assume it to be
> broken everywhere.
Oh, it's definitely not broken everywhere, because I use it myself,
and was tra
On Mon, Dec 4, 2017 at 2:34 PM, Dave Hansen wrote:
> On 12/04/2017 02:22 PM, Andy Lutomirski wrote:
>>> +
>>> + this_cpu_write(cpu_tlbstate.invalidate_other, true);
>>
>> Why do we need this extra variable instead of just looping over all
>> other ASIDs and invalidating them? It would be so
On Mon, 4 Dec 2017, Linus Torvalds wrote:
> On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki wrote:
> >
> > So far, resume from suspend-to-RAM (ACPI S3) is broken on all of the
> > systems I have tested, so it is probably safe to assume it to be
> > broken everywhere.
>
> Oh, it's definitely no
Peter Zijlstra wrote:
> > Good point! How about as shown in the updated patch below?
>
> Humm, I thought the idea was to completely remove read_barrier_depends
> from the lkmm and memory-barriers.txt, making it an Alpha implementation
> detail.
memory-barriers.txt explains how the barriers use
On Mon, Dec 04, 2017 at 03:07:32PM +0100, Thomas Gleixner wrote:
> From: Thomas Gleixner
>
> There is currently no way to force CPU bug bits like CPU feature bits. That
> makes it impossible to set a bug bit once at boot and have it stick for all
> upcoming CPUs.
>
> Extend the force set/clear a
On Mon, Dec 04, 2017 at 02:00:16PM +0800, Yixun Lan wrote:
> From: Jian Hu
>
> Update the doc to explicitly support Meson-AXG
>
> Signed-off-by: Jian Hu
> Signed-off-by: Yixun Lan
> ---
> Documentation/devicetree/bindings/pwm/pwm-meson.txt | 2 ++
> 1 file changed, 2 insertions(+)
Reviewed-b
On 12/04/2017 01:02 PM, Heiko Carstens wrote:
> On Fri, Dec 01, 2017 at 12:58:47PM -0800, Randy Dunlap wrote:
>> Hi,
>>
>> I used "maxcpus=1" on a recent x86 boot (4.15-rc1) and got 4 CPUs (all of
>> them AFAICT). When I use "nr_cpus=1", I do get a hard limit of one CPU.
>>
>>
>> A few boot log ex
On Monday, December 4, 2017 11:38:54 PM CET Thomas Gleixner wrote:
> On Mon, 4 Dec 2017, Linus Torvalds wrote:
>
> > On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki
> > wrote:
> > >
> > > So far, resume from suspend-to-RAM (ACPI S3) is broken on all of the
> > > systems I have tested, so it is
Christoph Hellwig wrote:
> [1.501264] BUG: unable to handle kernel NULL pointer dereference at
> 6714cfcb
> [1.502335] IP: rxrpc_release+0xd5/0x1c0
Is it fixed by current Linus?
In particular commit c501256406fb19c306504ee1fe41a4ea208d4245:
rxrpc: Use correct netns sou
On Mon, Dec 04, 2017 at 03:09:20PM +, Bart Van Assche wrote:
> On Sun, 2017-12-03 at 00:31 +0800, Ming Lei wrote:
> > Fixes: 0df21c86bdbf ("scsi: implement .get_budget and .put_budget for
> > blk-mq")
>
> It might be safer to revert commit 0df21c86bdbf instead of trying to fix all
> issues in
On Mon, Dec 04, 2017 at 02:22:54PM -0800, Andy Lutomirski wrote:
> > +static inline void invalidate_pcid_other(void)
> > +{
> > + /*
> > +* With global pages, all of the shared kenel page tables
> > +* are set as _PAGE_GLOBAL. We have no shared nonglobals
> > +* and
On 05.12.2017 00:52, Tejun Heo wrote:
> Hello, Kirill.
>
> On Tue, Dec 05, 2017 at 12:44:00AM +0300, Kirill Tkhai wrote:
>>> Can you please explain how this is a fundamental resource which can't
>>> be controlled otherwise?
>>
>> Currently, aio_nr and aio_max_nr are global. In case of containers t
Commit-ID: cdf577209aad4cdbe3455d3efa6cf631f838c55d
Gitweb: https://git.kernel.org/tip/cdf577209aad4cdbe3455d3efa6cf631f838c55d
Author: Andy Lutomirski
AuthorDate: Thu, 30 Nov 2017 07:57:57 -0800
Committer: Thomas Gleixner
CommitDate: Mon, 4 Dec 2017 23:41:42 +0100
x86/power: Fix some
On Tue, 2017-12-05 at 06:45 +0800, Ming Lei wrote:
> On Mon, Dec 04, 2017 at 03:09:20PM +, Bart Van Assche wrote:
> > On Sun, 2017-12-03 at 00:31 +0800, Ming Lei wrote:
> > > Fixes: 0df21c86bdbf ("scsi: implement .get_budget and .put_budget for
> > > blk-mq")
> >
> > It might be safer to reve
On Mon, 4 Dec 2017, Andy Lutomirski wrote:
> On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
> > From: Thomas Gleixner
> >
> > LDT is not really commonly used on 64bit so the overhead of populating the
> > fixmap entries on context switch for the rare LDT syscall users is a
> > reasonable
On 12/04/2017 01:18 PM, Thomas Gleixner wrote:
> On Mon, 4 Dec 2017, Linus Torvalds wrote:
>> On Mon, Dec 4, 2017 at 6:07 AM, Thomas Gleixner wrote:
>>> Kernel Page Table Isolation, prefix kpti_
>>>
>>>Linus, your call :)
>> I think you probably chose the right name here. The alternatives
On Mon, Dec 04, 2017 at 02:25:43PM -0800, Andy Lutomirski wrote:
> On Mon, Dec 4, 2017 at 6:08 AM, Thomas Gleixner wrote:
> > From: Dave Hansen
> >
> > This uses INVPCID to shoot down individual lines of the user mapping
> > instead of marking the entire user map as invalid. This
> > could/might/
On Mon, Dec 4, 2017 at 2:47 PM, Peter Zijlstra wrote:
> On Mon, Dec 04, 2017 at 02:22:54PM -0800, Andy Lutomirski wrote:
>
>> > +static inline void invalidate_pcid_other(void)
>> > +{
>> > + /*
>> > +* With global pages, all of the shared kenel page tables
>> > +* are set as
On Tue, 14/11/17, Colin King wrote:
> From: Colin Ian King
> cck_poweri cannot be greated than 15 as
> is derived from the bottom 4 bits
> from riv->channels[channel -
> 1].hw_value & 0xf. Hence the check for it
> being greater than 15 is redund
On Mon, Dec 04, 2017 at 10:39:05PM +, David Howells wrote:
> Peter Zijlstra wrote:
>
> > > Good point! How about as shown in the updated patch below?
> >
> > Humm, I thought the idea was to completely remove read_barrier_depends
> > from the lkmm and memory-barriers.txt, making it an Alpha
Hello, again.
On Mon, Dec 04, 2017 at 12:22:19PM -0800, Tejun Heo wrote:
> Hello,
>
> On Mon, Dec 04, 2017 at 10:44:49AM +0530, Prateek Sood wrote:
> > Any feedback/suggestion for this patch?
>
> Sorry about the delay. I'm a bit worried because it feels like we're
> chasing a squirrel. I'll th
Kirill Tkhai writes:
> On 05.12.2017 00:52, Tejun Heo wrote:
>> Hello, Kirill.
>>
>> On Tue, Dec 05, 2017 at 12:44:00AM +0300, Kirill Tkhai wrote:
Can you please explain how this is a fundamental resource which can't
be controlled otherwise?
>>>
>>> Currently, aio_nr and aio_max_nr are
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
drivers/net/can/flexcan.c
between commit:
29c64b17a0bc ("can: flexcan: fix VF610 state transition issue")
from Linus' tree and commit:
99b7668c04b2 ("can: flexcan: adding platform specific details for LS1021A")
fr
Hi Daniel,
Am 14.11.2017 um 00:34 schrieb Andreas Färber:
> Actions S700 has two 2Hz timers like S500, and four TIMx timers like S900.
>
> Signed-off-by: Andreas Färber
> ---
> v1 -> v2:
> * Adopted TIMER_OF_DECLARE() (Daniel)
>
> drivers/clocksource/owl-timer.c | 1 +
> 1 file changed, 1 i
On Mon, Dec 04, 2017 at 02:58:25PM -0800, Tejun Heo wrote:
> Hello, again.
>
> On Mon, Dec 04, 2017 at 12:22:19PM -0800, Tejun Heo wrote:
> > Hello,
> >
> > On Mon, Dec 04, 2017 at 10:44:49AM +0530, Prateek Sood wrote:
> > > Any feedback/suggestion for this patch?
> >
> > Sorry about the delay.
Hello, Kirill.
On Tue, Dec 05, 2017 at 01:49:42AM +0300, Kirill Tkhai wrote:
> > If the only reason is kernel memory consumption protection, the only
> > thing we need to do is making sure that memory used for aio commands
> > are accounted against cgroup kernel memory consumption and
> > relaxing
On 05.12.2017 02:02, Tejun Heo wrote:
> Hello, Kirill.
>
> On Tue, Dec 05, 2017 at 01:49:42AM +0300, Kirill Tkhai wrote:
>>> If the only reason is kernel memory consumption protection, the only
>>> thing we need to do is making sure that memory used for aio commands
>>> are accounted against cgrou
On Mon, Dec 04, 2017 at 02:54:46PM -0800, Andy Lutomirski wrote:
> On Mon, Dec 4, 2017 at 2:47 PM, Peter Zijlstra wrote:
> > As is __flush_tlb_single() does user and __flush_tlb_one() does
> > user+kernel.
>
> Yep. A one-liner above the function to that effect would make it
> *way* clearer what
Signed-off-by: Scott Bauer
---
Documentation/device-mapper/dm-unstripe.txt | 82 +
1 file changed, 82 insertions(+)
create mode 100644 Documentation/device-mapper/dm-unstripe.txt
diff --git a/Documentation/device-mapper/dm-unstripe.txt
b/Documentation/device-mapper/
This device mapper module remaps and unstripes IO so it lands
solely on a single drive in a RAID 0. In a 4 drive RAID 0 the
mapper exposes 1/4th of the LBA range as a virtual drive.
Each IO to that virtual drive will land on only one of the 4
drives, selected by the user.
As an example:
Intel NVM
On 05.12.2017 01:59, Jeff Moyer wrote:
> Kirill Tkhai writes:
>
>> On 05.12.2017 00:52, Tejun Heo wrote:
>>> Hello, Kirill.
>>>
>>> On Tue, Dec 05, 2017 at 12:44:00AM +0300, Kirill Tkhai wrote:
> Can you please explain how this is a fundamental resource which can't
> be controlled otherwi
On Mon, Dec 04, 2017 at 03:07:33PM +0100, Thomas Gleixner wrote:
> From: Thomas Gleixner
>
> Many x86 CPUs leak information to user space due to missing isolation of
> user space and kernel space page tables. There are many well documented
> ways to exploit that.
>
> The upcoming software migita
Hi Chen-Yu,
On 04/12/17 05:19, Chen-Yu Tsai wrote:
> On the A64, the MMC module clocks are fixed in the new timing mode,
> i.e. they do not have a bit to select the mode. These clocks have
> a 2x divider somewhere between the clock and the MMC module.
>
> To be consistent with other SoCs supporti
On 04/12/17 05:19, Chen-Yu Tsai wrote:
> On the A64, the MMC module clocks are fixed in the new timing mode,
> i.e. they do not have a bit to select the mode. These clocks have
> a 2x divider somewhere between the clock and the MMC module.
>
> To be consistent with other SoCs supporting the new ti
On 04/12/17 05:19, Chen-Yu Tsai wrote:
> Hi,
>
> This is a small fix to get MMC performance up to proper speeds on the
Maybe a small fix for a skilled developer, but a giant leap for all
users ;-)
MMC performance goes from: (4.15-rc1)
SD: Timing buffered disk reads: 36 MB in 3.17 seconds = 1
On Mon, 2017-12-04 at 18:23 -0200, Bruno E. O. Meneguele wrote:
> Simple but useful message log to the user in case of module appraise is
> forced and fails due to the lack of file descriptor, that might be
> caused by kmod calls to compressed modules.
[]
> diff --git a/security/integrity/ima/ima_m
Hi,
Recently scripts/leaking_addresses.pl was merged into the mainline with
the hope of catching leaking kernel addresses.
Would it be in scope for this script to be run by the kbuild test robot?
Excuse my very little knowledge of the kbuild test robot but would this
lead to the script being run
On Mon, Dec 04, 2017 at 01:51:42PM -0800, Kees Cook wrote:
> On Mon, Dec 4, 2017 at 1:44 PM, Tobin C. Harding wrote:
> > On Mon, Dec 04, 2017 at 01:28:45PM -0800, Kees Cook wrote:
> >> On Mon, Dec 4, 2017 at 1:22 PM, Tobin C. Harding wrote:
> >> > Advice about what to use as a unique identifier i
On Mon, Dec 04, 2017 at 04:59:14PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.86 release.
> There are 12 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Mon, Dec 04, 2017 at 04:59:25PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.104 release.
> There are 27 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know
On Mon, Dec 04, 2017 at 04:59:40PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.67 release.
> There are 38 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On Mon, Dec 04, 2017 at 04:59:24PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.4 release.
> There are 95 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
On 04.12.2017 23:10, rwar...@gmx.de wrote:
Hallo
someone and I got an regression with e1000e since kernel 4.14.3 and it seems
there is 4.14.4 on the way without a fix.
bug report is here:
https://bugzilla.kernel.org/show_bug.cgi?id=198047
( added stable and netdev to CC )
Yes I have a bo
On 11/30/2017 08:39 AM, Will Deacon wrote:
Hi again,
This is version two of the patches previously posted here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-November/542751.html
Changes since v1 include:
* Based on v4.15-rc1
* Trampoline moved into FIXMAP area
* Exp
On Mon, Dec 04, 2017 at 04:51:04PM +, Wang Nan wrote:
> Simplify patch 1/3 following Namhyung's suggestion.
>
> Context adjustment for patch 2 and 3.
>
> Wang Nan (3):
> perf mmap: Fix perf backward recording
> perf tools: Don't discard prev in backward mode
> perf tools: Replace 'backw
On Mon, Dec 4, 2017 at 4:31 AM, Jason Wang wrote:
> This patch introduces an eBPF based queue selection method. With this,
> the policy could be offloaded to userspace completely through a new
> ioctl TUNSETSTEERINGEBPF.
>
> Signed-off-by: Jason Wang
> ---
> +static u16 tun_ebpf_select_queue(str
On 12/05/2017 12:06 AM, Claudiu Manoil wrote:
-Original Message-
From: Zumeng Chen [mailto:zumeng.c...@gmail.com]
Sent: Monday, December 04, 2017 5:22 AM
To: net...@vger.kernel.org; linux-kernel@vger.kernel.org
Cc: Claudiu Manoil ; da...@davemloft.net
Subject: [PATCH 1/1] gianfar: fix a f
On Monday, December 4, 2017 11:41:06 PM CET Rafael J. Wysocki wrote:
> On Monday, December 4, 2017 11:38:54 PM CET Thomas Gleixner wrote:
> > On Mon, 4 Dec 2017, Linus Torvalds wrote:
> >
> > > On Mon, Dec 4, 2017 at 2:25 PM, Rafael J. Wysocki
> > > wrote:
> > > >
> > > > So far, resume from sus
That seems like a convoluted path to produce an illegal RFLAGS value.
What's to prevent syzkaller from simply clearing bit 1 of RFLAGS with
the KVM_SET_REGS ioctl?
On Mon, Nov 20, 2017 at 4:34 PM, Wanpeng Li wrote:
> 2017-11-21 7:09 GMT+08:00 Paolo Bonzini :
>> On 20/11/2017 23:52, Wanpeng Li wro
Hi Arnd,
Thank you for the patch.
On Monday, 27 November 2017 15:19:54 EET Arnd Bergmann wrote:
> uvc_video_get_ts() returns a 'struct timespec', but all its users
> really want a nanoseconds variable anyway.
>
> Changing the deprecated ktime_get_ts/ktime_get_real_ts to ktime_get
> and ktime_get
Hi Arnd,
Thank you for the patch.
On Monday, 27 November 2017 15:19:53 EET Arnd Bergmann wrote:
> 'struct timespec' works fine here, but we try to migrate
> away from it in favor of ktime_t or timespec64. In this
> case, using ktime_t produces the simplest code.
>
> Signed-off-by: Arnd Bergmann
We have several places that insert struct resources into the iomem_resource
or ioport_resource trees without setting the type. This *works* fine
because it's obvious that a resource must be the same type as its parent,
but it does mean that if we ever print the resource with %pR, it doesn't
print
501 - 600 of 1242 matches
Mail list logo
