4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 1e4c8dafbb6bf72fb5eca035b861e39c5896c2b7 upstream.
The 12 character temporary buffer is not necessarily long enough to hold
a 'long' value. Increase it.
Signed-off-by:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Steve French
commit 1e77a8c204c9d1b655c61751b8ad0fde22421dbb upstream.
If backupuid mount option is sent, we can incorrectly retry
(on access denied on query info) with a cifs (FindFirst)
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit 3c6c6a7878d00a3ac997a779c5b9861ff25dfcc8 upstream.
The code for manual bit triple is not endian-clean. It builds the variable
"hostdword" using byte accesses, therefore
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Max Filippov
commit 0773495b1f5f1c5e23551843f87b5ff37e7af8f7 upstream.
Xtensa ABI requires stack alignment to be at least 16. In noMMU
configuration ARCH_SLAB_MINALIGN is used to align stack.
4.4-stable review patch. If anyone has any objections, please let me know.
--
commit 24962af7e1041b7e50c1bc71d8d10dc678c556b5 upstream.
The current code does not make sure to page align bss before calling
vm_brk(), and this can lead to a VM_BUG_ON() in __mm_populate() due to
4.4-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 44c445c3d1b4eacff23141fa7977c3b2ec3a45c9 ]
This patch fixes a race condition that can result into the interface being
up and carrier on, but with transmits disabled in the hardware.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Young_X
commit e4f3aa2e1e67bb48dfbaaf1cad59013d5a5bc276 upstream.
There is another cast from unsigned long to int which causes
a bounds check to fail with specially crafted input. The value is
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Edwards
commit 4542d623c7134bc1738f8a68ccb6dd546f1c264f upstream.
Commands with protection information included were not truncating the
protection iov_iter to the number of protection
On Mon 19-11-18 17:48:35, Vlastimil Babka wrote:
> On 11/19/18 5:46 PM, Vlastimil Babka wrote:
> > On 11/19/18 5:46 PM, Michal Hocko wrote:
> >> On Mon 19-11-18 17:36:21, Vlastimil Babka wrote:
> >>>
> >>> So what protects us from locking a page whose refcount dropped to zero?
> >>> and is being
4.4-stable review patch. If anyone has any objections, please let me know.
--
commit bb177a732c4369bb58a1fe1df8f552b6f0f7db5f upstream.
syzbot has noticed that a specially crafted library can easily hit
VM_BUG_ON in __mm_populate
kernel BUG at mm/gup.c:1242!
invalid
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Changwei Ge
commit 29aa30167a0a2e6045a0d6d2e89d8168132333d5 upstream.
Somehow, file system metadata was corrupted, which causes
ocfs2_check_dir_entry() to fail in function
4.4-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 4dc69c1c1fff2f587f8e737e70b4a4e7565a5c94 ]
Using memcpy() from a string that is shorter than the length copied means
the destination buffer is being filled with arbitrary data from
4.4-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 5983587c8c5ef00d6886477544ad67d495bc5479 ]
Currently if the stat type is invalid then data[i] is being set
either by dereferencing a null pointer p, or it is reading from
an
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Krzysztof Kozlowski
commit 8985167ecf57f97061599a155bb9652c84ea4913 upstream.
When driver is built as module and DT node contains clocks compatible
(e.g. "samsung,s2mps11-clk"), the module
4.4-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit d06f8a2f1befb5a3d0aa660ab1c05e9b744456ea ]
Masking/unmasking the CPU UART irq in CP0_Status (and redirecting it to
other CPUs) may cause interrupts be lost, especially in
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit c09bcc91bb94ed91f1391bffcbe294963d605732 upstream.
Reading the registers without waiting for engine idle returns
unpredictable values. These unpredictable values result
4.4-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 360fe725f8849aaddc53475fef5d4a0c439b05ae ]
After commit e509bd7da149dc349160 ("genirq: Allow migration of chained
interrupts by installing default action") Loongson-3 fails at here:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 94e6992bb560be8bffb47f287194adf070b57695 upstream.
If the read is large enough, we end up spinning in the messenger:
libceph: osd0 192.168.122.1:6801 io error
libceph:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Max Filippov
commit 40dc948f234b73497c3278875eb08a01d5854d3f upstream.
The bootloader may pass physical address of the boot parameters structure
to the MMUv3 kernel in the register a2. Code in
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Tomi Valkeinen
[ Upstream commit 538f66ba204944470a653a45f8befdf97c22 ]
A DMM timeout "timed out waiting for done" has been observed on DRA7
devices. The timeout happens rarely, and only
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: He Zhe
commit 1bd54d851f50dea6af30c3e6ff4f3e9aab5558f9 upstream.
kgdboc_option_setup does not check input argument before passing it
to strlen. The argument would be a NULL pointer if
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Miles Chen
[ Upstream commit 33a1a7be198657c8ca26ad406c4d2a89b7162bcc ]
The issue is found by a fuzzing test.
If tty_find_polling_driver() recevies an incorrect input such as
',,' or '0b',
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Mc Guire
[ Upstream commit c5d59528e24ad22500347b199d52b9368e686a42 ]
altera_hw_filt_init() which calls append_internal() assumes
that the node was successfully linked in while in
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Stefan Nuernberger
commit 076ed3da0c9b2f88d9157dbe7044a45641ae369e upstream.
commit 40413955ee26 ("Cipso: cipso_v4_optptr enter infinite loop") fixed
a possible infinite loop in the IP option
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Max Filippov
commit 40dc948f234b73497c3278875eb08a01d5854d3f upstream.
The bootloader may pass physical address of the boot parameters structure
to the MMUv3 kernel in the register a2. Code
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Vasily Averin
commit de59fae0043f07de5d25e02ca360f7d57bfa5866 upstream.
Fixes: dc6982ff4db1 ("ext4: refactor code to read directory blocks ...")
Signed-off-by: Vasily Averin
Signed-off-by:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Young_X
commit e4f3aa2e1e67bb48dfbaaf1cad59013d5a5bc276 upstream.
There is another cast from unsigned long to int which causes
a bounds check to fail with specially crafted input. The value
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Joel Stanley
[ Upstream commit ee9d21b3b3583712029a0db65a4b7c081d08d3b3 ]
When building with clang crt0's _zimage_start is not marked weak, which
breaks the build when linking the kernel
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Lukas Czerner
commit 625ef8a3acd111d5f496d190baf99d1a815bd03e upstream.
Variable retries is not initialized in ext4_da_write_inline_data_begin()
which can lead to nondeterministic number of
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Ilya Dryomov
commit 94e6992bb560be8bffb47f287194adf070b57695 upstream.
If the read is large enough, we end up spinning in the messenger:
libceph: osd0 192.168.122.1:6801 io error
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Jan Kara
commit ccd3c4373eacb044eb3832966299d13d2631f66f upstream.
The code cleaning transaction's lists of checkpoint buffers has a bug
where it increases bh refcount only after releasing
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dengcheng Zhu
[ Upstream commit dc57aaf95a516f70e2d527d8287a0332c481a226 ]
After changing CPU online status, it will not be sent any IPIs such as in
__flush_cache_all() on software coherency
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Nicolas Pitre
commit 672ca9dd13f1aca0c17516f76fc5b0e8344b3e46 upstream.
It is possible for corrupted filesystem images to produce very large
block offsets that may wrap when a length is
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: "Eric W. Biederman"
[ Upstream commit 3597dfe01d12f570bc739da67f857fd222a3ea66 ]
Instead of playing whack-a-mole and changing SEND_SIG_PRIV to
SEND_SIG_FORCED throughout the kernel to ensure
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit f823ce2a1202d47110a7ef86b65839f0be8adc38 upstream.
Follow the V4L2 spec, as warned by v4l2-compliance:
warn: v4l2-test-formats.cpp(732): TRY_FMT cannot
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit 15644bfa195bd166d0a5ed76ae2d587f719c3dac upstream.
Instead of using a register value, use an AMUX name, as otherwise
VIDIOC_G_AUDIO would fail.
Cc:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Amir Goldstein
commit 93f38b6fae0ea8987e22d9e6c38f8dfdccd867ee upstream.
printk format used %*s instead of %.*s, so hostname_len does not limit
the number of bytes accessed from hostname.
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: He Zhe
commit 277fcdb2cfee38ccdbe07e705dbd4896ba0c9930 upstream.
log_buf_len_setup does not check input argument before passing it to
simple_strtoull. The argument would be a NULL pointer if
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Wenwen Wang
commit 800a7340ab7dd667edf95e74d8e4f23a17e87076 upstream.
In copy_params(), the struct 'dm_ioctl' is first copied from the user
space buffer 'user' to 'param_kernel' and the field
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mauro Carvalho Chehab
commit afeaade90db4c5dab93f326d9582be1d5954a198 upstream.
The v4l2-compliance tool complains if a video doesn't start
with a zero sequence number.
While this shouldn't
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Corey Wright
[3.18.y only, to fix a previous patch]
__dm_destroy() takes io_barrier SRCU lock (dm_get_live_table) twice
which leads to a deadlock. Remove taking lock before holding
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit c09bcc91bb94ed91f1391bffcbe294963d605732 upstream.
Reading the registers without waiting for engine idle returns
unpredictable values. These unpredictable values result
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Ondrej Mosnacek
commit fbe1a850b3b1522e9fc22319ccbbcd2ab05328d2 upstream.
When the LRW block counter overflows, the current implementation returns
128 as the index to the precomputed
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric W. Biederman
commit 0ab93e9c99f8208c0a1a7b7170c827936268c996 upstream.
The genweq_add_file and genwqe_del_file by caching current without
using reference counting embed the assumption
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 1e4c8dafbb6bf72fb5eca035b861e39c5896c2b7 upstream.
The 12 character temporary buffer is not necessarily long enough to hold
a 'long' value. Increase it.
Signed-off-by:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Vasily Averin
commit db6aee62406d9fbb53315fcddd81f1dc271d49fa upstream.
Fixes: 1c6bd7173d66 ("ext4: convert file system to meta_bg if needed ...")
Signed-off-by: Vasily Averin
Signed-off-by:
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Vasily Averin
commit feaf264ce7f8d54582e2f66eb82dd9dd124c94f3 upstream.
Fixes: d745a8c20c1f ("ext4: reduce contention on s_orphan_lock")
Fixes: 6e3617e579e0 ("ext4: Handle non empty on-disk
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Alexandre Belloni
[ Upstream commit ae61cf5b9913027c6953a79ed3894da4f47061bd ]
When both uio and the uio drivers are built in the kernel, it is possible
for a driver to register devices
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Dominique Martinet
[ Upstream commit 62e3941776fea8678bb8120607039410b1b61a65 ]
p9stat_free is more of a cleanup function than a 'free' function as it
only frees the content of the struct;
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Axtens
[ Upstream commit f5e284803a7206d43e26f9ffcae5de9626d95e37 ]
When enumerating page size definitions to check hardware support,
we construct a constant which is (1U <<
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Theodore Ts'o
commit 9e463084cdb22e0b56b2dfbc50461020409a5fd3 upstream.
Fixes: bfe0a5f47ada ("ext4: add more mount time checks of the superblock")
Reported-by: Vasily Averin
Signed-off-by:
This is the start of the stable review cycle for the 3.18.126 release.
There are 90 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.
Responses should be made by Wed Nov 21 16:25:28 UTC 2018.
Anything
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Max Filippov
commit 4119ba211bc4f1bf638f41e50b7a0f329f58aa16 upstream.
This section collects all source .note.* sections together in the
vmlinux image. Without it .note.Linux section may be
at 8:20 PM, Masahiro Yamada wrote:
> On Sat, Nov 17, 2018 at 6:02 AM Nadav Amit wrote:
>> From: Masahiro Yamada
>> Sent: November 16, 2018 at 7:45:45 AM GMT
>>> To: Nadav Amit
>>> Cc: Ingo Molnar , Michal Marek ,
>>> Thomas Gleixner , Borislav Petkov , H.
>>> Peter Anvin , X86 ML , Linux
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Omar Sandoval
[ Upstream commit 1448a2a5360ae06f25e2edc61ae070dff5c0beb4 ]
If we fail to allocate the request queue for a disk, we still need to
free that disk, not just the previous ones.
Hi,
On Fri, Nov 16, 2018 at 7:21 PM Mark Brown wrote:
>
> The stub implementation of _set_load() returns a mode value which is
> within the bounds of valid return codes for success (the documentation
> just says that failures are negative error codes) but not sensible or
> what the actual
4.9-stable review patch. If anyone has any objections, please let me know.
--
[ Upstream commit 4dc69c1c1fff2f587f8e737e70b4a4e7565a5c94 ]
Using memcpy() from a string that is shorter than the length copied means
the destination buffer is being filled with arbitrary data from
On 11/19/18 3:30 AM, Alexey Brodkin wrote:
> It turned out we used to use default implementation of sched_clock()
> from kernel/sched/clock.c which was as precise as 1/HZ, i.e.
> by default we had 10 msec granularity of time measurement.
>
> Now given ARC built-in timers are clocked with the same
On 11/12/2018 11:42 AM, Valentin Schneider wrote:
> Hi Steve,
>
> On 09/11/2018 12:50, Steve Sistare wrote:
>> From: Steve Sistare
>>
>> Define and initialize a sparse bitmap of overloaded CPUs, per
>> last-level-cache scheduling domain, for use by the CFS scheduling class.
>> Save a pointer to
Manivannan,
On 19/11/2018 17:09, Manivannan Sadhasivam wrote:
> Add interrupt driver for RDA Micro RDA8810PL SoC.
>
> Signed-off-by: Andreas Färber
> Signed-off-by: Manivannan Sadhasivam
> ---
> arch/arm/mach-rda/Kconfig | 1 +
> drivers/irqchip/Kconfig| 4 ++
>
On Fri, 16 Nov 2018 19:09:36 PST (-0800), Olof Johansson wrote:
On Thu, Nov 8, 2018 at 11:32 AM Palmer Dabbelt wrote:
On Thu, 08 Nov 2018 11:07:00 PST (-0800), david.abdurachma...@gmail.com wrote:
> Fixes warning: 'struct module' declared inside parameter list will not be
> visible outside of
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Vasily Averin
commit 61a9c11e5e7a0dab5381afa5d9d4dd5ebf18f7a0 upstream.
Fixes: 01f795f9e0d6 ("ext4: add online resizing support for meta_bg ...")
Signed-off-by: Vasily Averin
Signed-off-by:
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Deucher
commit d9997b64c52b70bd98c48f443f068253621d1ffc upstream.
This caused a confusing error message, but there is functionally
no problem since the default method is DIRECT.
On Thu, Nov 15, 2018 at 07:00:07AM +0800, Aubrey Li wrote:
> Add a /proc//arch_state interface to expose per-task cpu specific
> state values.
>
> Exposing AVX-512 Hi16_ZMM registers usage is for the user space job
> scheduler to cluster AVX-512 using tasks together, because these tasks
> could
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Max Filippov
commit 40dc948f234b73497c3278875eb08a01d5854d3f upstream.
The bootloader may pass physical address of the boot parameters structure
to the MMUv3 kernel in the register a2. Code
On Mon, 19 Nov 2018 12:41:10 +
vitor wrote:
> Hi Coling,
>
>
> Thanks for your report.
>
> On 16/11/18 18:42, Colin King wrote:
> > From: Colin Ian King
> >
> > The masking operation on status is using a bitwise 'or' rather than
> > a bitwise 'and' operator, and hence the result is
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Axtens
[ Upstream commit f5e284803a7206d43e26f9ffcae5de9626d95e37 ]
When enumerating page size definitions to check hardware support,
we construct a constant which is (1U <<
On Wed, Nov 14, 2018 at 11:04 AM Firoz Khan wrote:
> Adding a new table entry consisting of:
> - System call number.
> - ABI.
> - System call name.
> - Entry point name.
> - Compat entry name, if required.
>
> syscallhdr.sh and syscalltbl.sh will generate
On 11/19/18 9:28 AM, Jarkko Sakkinen wrote:
> Ah, you are correct.
>
> You should add a boolean flag instead of introducing a new variable for
> holding amount that has been read because obviously one read operation
> is enough for backwards compatibility.
>
> The code could read the code to
Currently we get extra newlines on OMAP1/2 when the SoC name is printed:
[0.00] OMAP1510
[0.00] revision 2 handled as 15xx id: bc058c9b93111a16
[0.00] OMAP2420
[0.00]
Fix by using pr_cont.
Signed-off-by: Aaro Koskinen
---
arch/arm/mach-omap1/id.c | 6 +++---
Configure omap1_spi100k only on OMAP7xx. This allows running multiboard
kernels on non-OMAP7xx HW with CONFIG_SPI_OMAP_100K enabled.
Signed-off-by: Aaro Koskinen
---
arch/arm/mach-omap1/devices.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/mach-omap1/devices.c
Hi Ulf,
Got one issue in hotplug path where of_genpd_detach_cpu calls
dev_pm_qos_remove_notifier which can be sleeping as per below call
stack. I think it should be applicable for current patch as well right?
Please let me know what am I missing? why didn't you see this issue with
this
On Mon, Nov 19, 2018 at 10:46 AM Borislav Petkov wrote:
>
> From: Borislav Petkov
>
> Currently, the kernel uses
>
> [LM]FENCE; RDTSC
>
> in the timekeeping code, to guarantee monotonicity of time where the
> *FENCE is selected based on vendor.
>
> Replace that sequence with RDTSCP which is
This is required as part of the initialization sequence on certain SoCs.
If these registers are not initialized, the hardware can be unresponsive.
This fixes the driver on apq8060 (HP TouchPad device).
Signed-off-by: Jonathan Marek
---
v2: updated the commit message to be more descriptive
I
On Mon, Nov 12, 2018 at 05:01:42PM +0100, Lucas Stach wrote:
> Device drivers with optional firmware may still want to use the
> asynchronous firmware loading interface. To avoid printing a
> warining into the kernel log when the optional firmware is
> absent, add a nowarn variant of this
On Fri, 16 Nov 2018 19:32:04 PST (-0800), a...@brainfault.org wrote:
On Sat, Nov 17, 2018 at 2:43 AM Palmer Dabbelt wrote:
On Sun, 11 Nov 2018 21:55:15 PST (-0800), a...@brainfault.org wrote:
> This patch extends Linux RISC-V build system to build and install:
> Image - Flat uncompressed
Hello Hanjie, Hello Yue,
sorry for being late with my comment
On Tue, Oct 9, 2018 at 3:53 AM Hanjie Lin wrote:
>
> From: Yue Wang
>
> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
> PCI core. This patch adds documentation for the DT bindings in Meson PCIe
>
On 11/19/18 11:52 AM, Andy Lutomirski wrote:
>
> I thought I benchmarked this on Intel at some point and found the
> LFENCE;RDTSC variant to be slightly faster. But I believe you, so:
>
> Acked-by: Andy Lutomirski
>
As long as the difference isn't significant, the simplicity would seem to be
On 2018-11-19, Daniel Colascione wrote:
> > I wonder how fast it would be holding a pid with another open()ed fd.
> > And then you need to read comm (or how you filter whom to kill).
> > It seems to me that procfs will be even slower with this safe-way.
> > But I might misunderstand the idea,
On Fri, 16 Nov 2018, Tim Chen wrote:
> +static enum spectre_v2_app2app_mitigation_cmd __init
> + spectre_v2_parse_app2app_cmdline(enum spectre_v2_mitigation_cmd
> v2_cmd)
> +{
> + enum spectre_v2_app2app_mitigation_cmd cmd;
> + char arg[20];
> + int ret, i;
> +
> + if
On 2018-11-19, Christian Brauner wrote:
> + if (info) {
> + ret = __copy_siginfo_from_user(sig, , info);
> + if (unlikely(ret))
> + goto err;
> + /*
> + * Not even root can pretend to send signals from the kernel.
> +
On Mon, 19 Nov 2018, Michal Hocko wrote:
> On Mon 19-11-18 15:10:16, Michal Hocko wrote:
> [...]
> > In other words. Why cannot we do the following?
>
> Baoquan, this is certainly not the right fix but I would be really
> curious whether it makes the problem go away.
>
> > diff --git
Christian Brauner writes:
> On Mon, Nov 19, 2018 at 07:59:24AM -0800, Daniel Colascione wrote:
>> You never addressed my comment on the previous patch about your use of
>
> Sorry, that thread exploded so quickly that I might have missed it.
>
>> private_data here. Why can't you use the struct
On 11/19/2018 12:45 PM, Borislav Petkov wrote:
> From: Borislav Petkov
>
> Currently, the kernel uses
>
> [LM]FENCE; RDTSC
>
> in the timekeeping code, to guarantee monotonicity of time where the
> *FENCE is selected based on vendor.
>
> Replace that sequence with RDTSCP which is faster or
Tim,
On Mon, 19 Nov 2018, Tim Chen wrote:
> On 11/19/2018 06:57 AM, Peter Zijlstra wrote:
> > In particular, the SMT topology bits are set before we enable
> > interrrupts and similarly, are cleared after we disable interrupts for
> > the last time and die.
>
>
> Peter & Thomas,
>
> Any
Hi,
> Am 19.11.2018 um 19:44 schrieb Andreas Kemnade :
>
> Hi,
>
> On Mon, 19 Nov 2018 09:22:59 +0100
> "H. Nikolaus Schaller" wrote:
>
>> Hi,
>>
>>> Am 18.11.2018 um 22:57 schrieb Andreas Kemnade :
>>>
>>> Here is another chapter of the story to get gta04 gnss power
>>> management into the
John, thanks for the discussion at LPC. One of the concerns we
raised however was the performance test. The numbers below are
rather obviously tainted. I think we need to get a better baseline
before concluding anything...
Here's my main concern:
On 11/10/2018 3:50 AM, john.hubb...@gmail.com
Hi Jian,
Not clear to me why should be + instead of *.
ODR is expressed in Hz, so (1/Hz) = period in seconds (1 sample sampling time)
[s]
1000 * (1/Hz) = period in milliseconds (1 sample sampling time) [ms]
n * 1000 * (1/Hz) = n times period in milliseconds (n times sample sampling
time) [ms]
Hello,
I need your help to invest in your region.
Hi
On 19/11/2018 17:53, Mauro Carvalho Chehab wrote:
> Hi Takashi,
>
> Em Mon, 19 Nov 2018 16:13:29 +0100
> Takashi Iwai escreveu:
>
>> Hi,
>>
>> we've got a regression report on openSUSE Bugzilla regarding DVB-S PCI
>> card:
>> https://bugzilla.opensuse.org/show_bug.cgi?id=1116374
>>
>>
On Fri, Nov 16, 2018 at 5:46 PM Sean Wang wrote:
>
> On Fri, Nov 16, 2018 at 2:06 PM Rob Herring wrote:
> >
> > In preparation to remove the node name pointer from struct device_node,
> > convert printf users to use the %pOFn format specifier.
> >
> > Cc: Sean Wang
> > Cc: Linus Walleij
> >
Hello,
Rob Herring wrote:
> Remove directly accessing device_node.type pointer and use the accessors
> instead. This will eventually allow removing the type pointer.
>
> Cc: Ralf Baechle
> Cc: Paul Burton
> Cc: James Hogan
> Cc: linux-m...@linux-mips.org
> Signed-off-by: Rob Herring
Applied
Hello,
Maciej W. Rozycki wrote:
> Hi,
>
> This mini patch series enables correct support for DMA in the presence of
> memory outside the 32-bit address range with the Broadcom SiByte SOCs and
> the relevant development boards.
>
> There is a quirk in the BCM1250, BCM1125 and BCM1125H SOCs in
On 11/19/18 8:35 AM, Steven Rostedt wrote:
> On Mon, 19 Nov 2018 17:24:32 +0100
> Greg KH wrote:
>
>> On Mon, Nov 19, 2018 at 10:46:54AM -0500, Steven Rostedt wrote:
>>> On Mon, 19 Nov 2018 16:13:11 +0100
>>> Greg KH wrote:
>>>
> Can this patch also be applied to the stable trees? The
Quoting Evan Green (2018-10-26 10:35:43)
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
> b/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
> index eedfaf8922e2..d5fddea71a85 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
> +++ b/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
> @@ -356,6 +356,20
On Mon, 19 Nov 2018, Jerome Glisse wrote:
> > IIRC this is solved in IB by automatically calling
> > madvise(MADV_DONTFORK) before creating the MR.
> >
> > MADV_DONTFORK
> > .. This is useful to prevent copy-on-write semantics from changing the
> > physical location of a page if the parent
Thomas,
>>
>> +#ifdef CONFIG_SCHED_SMT
>> +
>> +extern struct static_key_false sched_smt_present;
>> +
>> +static inline bool cpu_smt_present(void)
>> +{
>> +if (static_branch_unlikely(_smt_present))
>> +return true;
>> +else
>> +return false;
>
> What's wrong
Hi,
On Mon, Nov 19, 2018 at 11:19 AM Stephen Boyd wrote:
>
> Quoting Evan Green (2018-10-26 10:35:43)
> > diff --git a/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
> > b/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
> > index eedfaf8922e2..d5fddea71a85 100644
> > ---
On Mon, Nov 19, 2018 at 11:07 AM Rob Herring wrote:
>
> On Fri, Nov 16, 2018 at 5:46 PM Sean Wang wrote:
> >
> > On Fri, Nov 16, 2018 at 2:06 PM Rob Herring wrote:
> > >
> > > In preparation to remove the node name pointer from struct device_node,
> > > convert printf users to use the %pOFn
On Mon, 19 Nov 2018 11:09:50 -0800
Florian Fainelli wrote:
> > I did the change against v4.2.8 below.
>
> Thanks Steven! Here is the local 4.9 backport:
Yours even updates the comment.
Reviewed-by: Steven Rostedt (VMware)
-- Steve
>
> diff --git a/kernel/sched/core.c
701 - 800 of 3448 matches
Mail list logo
