The patch
regulator: stm32-vrefbuf: fix check on ready flag
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On Thu, 8 Feb 2018 19:59:24 +0900
Namhyung Kim wrote:
> > @@ -347,6 +361,8 @@ static long long get_arg(struct func_arg *arg, unsigned
> > long val)
> > char buf[8];
> > int ret;
> >
> > + val += arg->index;
> > +
> > if (!arg->indirect)
> > return val;
>
> So this
On Wed, Feb 07, 2018 at 04:08:25PM +0800, Jason Wang wrote:
> To avoid slab to warn about exceeded size, fail early if queue
> occupies more than KMALLOC_MAX_SIZE.
>
> Reported-by: syzbot+e4d4f9ddd42955397...@syzkaller.appspotmail.com
> Signed-off-by: Jason Wang
> ---
> include/linux/ptr_ring.h
On Thu, Feb 08, 2018 at 04:05:58PM +0100, Vincent Guittot wrote:
> On 8 February 2018 at 15:00, Peter Zijlstra wrote:
> > On Tue, Feb 06, 2018 at 08:23:05PM +0100, Vincent Guittot wrote:
> >
> >> @@ -9207,13 +9231,15 @@ void nohz_balance_enter_idle(int cpu)
> >> if (!housekeeping_cpu(cpu,
On Wed, Feb 07, 2018 at 11:02:26AM -0800, Dave Hansen wrote:
> On 02/07/2018 04:59 AM, Kirill A. Shutemov wrote:
> > IA32_TME_ACTIVATE MSR (0x982) can be used to check if BIOS has enabled
> > TME and MKTME. It includes which encryption policy/algorithm is selected
> > for TME or available for
On Thu, Feb 08, 2018 at 03:30:31PM +, Will Deacon wrote:
> On Thu, Feb 08, 2018 at 03:00:05PM +0100, Peter Zijlstra wrote:
> > Without this ordering I think it would be possible to loose has_blocked
> > and not observe the CPU either.
>
> I had a quick look at this, and I think you're right.
Originally, UBSAN's __ubsan_handle_type_mismatch took a struct
type_mismatch_data, as defined in lib/ubsan.h. This has an unsigned long
alignment field.
New versions of UBSAN call __ubsan_handle_type_mismatch_v1, which is
similar to __ubsan_handle_type_mismatch, but takes a different struct
where
On Thu, 8 Feb 2018 20:03:41 +0900
Namhyung Kim wrote:
> > @@ -76,6 +76,7 @@ typedef u64 x64;
> > typedef u32 x32;
> > typedef u16 x16;
> > typedef u8 x8;
> > +typedef void * symbol;
> >
> > #define TYPE_TUPLE(type) \
> > { #type, sizeof(type), is_signed_type(type) }
>
On Thu, 8 Feb 2018 12:20:14 +0100
Jiri Olsa wrote:
> On Wed, Feb 07, 2018 at 03:24:03PM -0500, Steven Rostedt wrote:
>
> SNIP
>
> > +
> > +void create_function_event_file(struct dentry *d_tracer)
> > +{
> > + struct dentry *d;
> > +
> > + d = trace_create_file("function_events", 0644,
On 02/07/2018 09:01 PM, Chris Chiu wrote:
Hi,
We are working with a new desktop Acer Veriton Z4640G and get
stumbled on failing to enter S3 suspend with kernel version 4.14 even
the latest 4.15+. Here's the kernel log
https://gist.github.com/mschiu77/76888f1fd4eb56aa8959d76759a912bb.
This
On Thu, Feb 8, 2018 at 7:29 AM, Jim Mattson wrote:
> Similarly, the correct L1 CR4 value should be in vmcs01's CR4
> read shadow field.
Sorry; that's wrong. L1's CR4 value has to be reconstructed from the
vmcs01 guest CR4 field and CR4 shadow field using the cr4 guest/host
mask. But there is no
Jianchao,
Given the discussion on this set, you plan to respin again
for 4.16?
On Thu, Jan 18, 2018 at 9:13 PM, Corentin Labbe
wrote:
> img-ascii-lcd select un-existing SYSCON kconfig name.
> This patch fix this error by using the correct MFD_SYSCON kconfig name.
>
CC'ing Paul & Ralf in case they want to ack.
The mistake seems to be in the tree since the addition of the
On 08/02/2018 13:54, Jiri Olsa wrote:
On Wed, Feb 07, 2018 at 01:45:00AM +0800, John Garry wrote:
Hi Jirka,
I'll try to combine some responses, below:
SNIP
+static void fixup_field(char *from, char **to)
+{
+ *to = malloc(strlen(from));
+
+ strcpy(*to, from);
+}
+
+#define
On Thu, 8 Feb 2018 12:20:31 +0100
Jiri Olsa wrote:
> > +Symbols (function names)
> > +
> > +
> > +To display kallsyms "%pS" type of output, use the special type "symbol".
> > +
> > +Again, using gdb to find the offset of the "func" field of struct
> > work_struct
> > +
>
Don't put buffers of data to be handed to crypto on the stack as this may
cause an assertion failure in the kernel (see below). Fix this by using an
kmalloc'd buffer instead.
kernel BUG at ./include/linux/scatterlist.h:147!
...
RIP: 0010:rxkad_encrypt_response.isra.6+0x191/0x1b0 [rxrpc]
RSP:
On 7 February 2018 at 14:03, Kim Phillips wrote:
> Commit 1c8859848dbb ("coresight replicator: Cleanup programmable
> replicator naming") changed the Kconfig symbol name from
> QCOM_REPLICATOR, which, whilst not in the single arm64 defconfig,
> was being set in my juno build script, which left
On Thu, Feb 08, 2018 at 04:46:43PM +0100, Peter Zijlstra wrote:
> On Thu, Feb 08, 2018 at 03:30:31PM +, Will Deacon wrote:
> > On Thu, Feb 08, 2018 at 03:00:05PM +0100, Peter Zijlstra wrote:
>
> > > Without this ordering I think it would be possible to loose has_blocked
> > > and not observe
I think it'd be simpler to have blk_poll set it back to running if
need_resched is true rather than repeat this patter across all the
callers:
---
diff --git a/block/blk-mq.c b/block/blk-mq.c
index df93102e2149..40285fe1c8ad 100644
--- a/block/blk-mq.c
+++ b/block/blk-mq.c
@@ -3164,6 +3164,7
On 02/07/2018 08:57 PM, David Miller wrote:
From: Grygorii Strashko
Date: Tue, 6 Feb 2018 19:17:06 -0600
It was discovered that simple program which indefinitely sends 200b UDP
packets and runs on TI AM574x SoC (SMP) under RT Kernel triggers network
watchdog timeout in TI CPSW driver (<6
On 02/08/2018 06:46 PM, Mark Rutland wrote:
> Originally, UBSAN's __ubsan_handle_type_mismatch took a struct
> type_mismatch_data, as defined in lib/ubsan.h. This has an unsigned long
> alignment field.
>
> New versions of UBSAN call __ubsan_handle_type_mismatch_v1, which is
> similar to
Okay, I will send it later.
On Thu, Feb 8, 2018 at 11:42 PM, Mark Brown wrote:
> On Thu, Feb 08, 2018 at 04:25:10PM +0200, Andy Shevchenko wrote:
>> On Fri, Jan 26, 2018 at 9:16 AM, Donglin Peng wrote:
>
>> > I can send another patch after the following patch is merged:
>> >
On Thu, Feb 08, 2018 at 12:12:37PM +, Suzuki K Poulose wrote:
> So far we have restricted the scopes for the capabilities
> as follows :
> 1) Errata workaround check are run all CPUs (i.e, always
> SCOPE_LOCAL_CPU)
> 2) Arm64 features are run only once after the sanitised
> feature
> I commented the device tree reading property:
> arm,cpu-registers-not-fw-configured , from the arch/arm/kernel/vdso.c
Don't do that, please. The presence of that property indicates that the counter
is not suitable for use by the OS. There is nothing we can do in Linux to make
the VDSO useful
On 07/02/18 21:03, Kim Phillips wrote:
Commit 1c8859848dbb ("coresight replicator: Cleanup programmable
replicator naming") changed the Kconfig symbol name from
QCOM_REPLICATOR, which, whilst not in the single arm64 defconfig,
was being set in my juno build script, which left the new symbol
The following changes since commit d8a5b80568a9cb66810e75b182018e9edb68e8ff:
Linux 4.15 (2018-01-28 13:20:33 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
for you to fetch changes up to
Hi Patrick,
Il 06/02/2018 19:36, Patrick Bellasi ha scritto:
On 06-Feb 19:14, Claudio Scordino wrote:
Hi Patrick,
At first glance, your proposal below makes to make sense.
However, I'm wondering if we cannot get it working using
rq->dl's provided information instead of flags?
Yes, we can
http://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.git/log/?h=afs-next
tagged thusly:
afs-next-20180208
David
---
David Howells (7):
afs: Add missing afs_put_cell()
afs: Fix missing cursor clearance
afs: Need to clear responded flag in addr cursor
afs: Fix se
Remove some old unused code.
Signed-off-by: David Howells
---
fs/afs/rotate.c | 235 ---
1 file changed, 235 deletions(-)
diff --git a/fs/afs/rotate.c b/fs/afs/rotate.c
index 892a4904fd77..cfe0931e7844 100644
--- a/fs/afs/rotate.c
+++
afs_alloc_volume() needs to release the cell ref it obtained in the case of
an error. Fix this by adding an afs_put_cell() call into the error path.
This can triggered when a lookup for a cell in a dynamic root or an
autocell mount returns an error whilst trying to look up the server (such
as
Fix server list handling in the following ways:
(1) In afs_alloc_volume(), remove duplicate server list build code. This
was already done by afs_alloc_server_list() which afs_alloc_volume()
previously called. This just results in twice as many VL RPCs.
(2) In
Rearrange afs_select_fileserver() a little to put the use_server chunk
before the next_server chunk so that with the removal of a couple of gotos
the main path through the function is all one sequence.
Signed-off-by: David Howells
---
fs/afs/rotate.c | 42
afs_select_fileserver() ends the address cursor it is using in the case in
which we get some sort of network error and run out of addresses to iterate
through, before it jumps to try the next server. This also needs to be
done when the server aborts with some sort of error that means we should
In afs_select_fileserver(), we need to clear the ->responded flag in the
address list when reusing it. We should also clear it in
afs_select_current_fileserver().
To this end, just memset() the object before initialising it.
Fixes: d2ddc776a458 ("afs: Overhaul volume and server record caching
Support the AFS dynamic root which is a pseudo-volume that doesn't connect
to any server resource, but rather is just a root directory that
dynamically creates mountpoint directories where the name of such a
directory is the name of the cell.
Such a mount can be created thus:
mount -t
On Thu, Feb 08, 2018 at 07:05:14PM +0300, Andrey Ryabinin wrote:
> On 02/08/2018 06:46 PM, Mark Rutland wrote:
> > Originally, UBSAN's __ubsan_handle_type_mismatch took a struct
> > type_mismatch_data, as defined in lib/ubsan.h. This has an unsigned long
> > alignment field.
> >
> > New versions
On Thu 08-02-18 15:18:11, Dmitry Vyukov wrote:
> On Thu, Feb 8, 2018 at 3:08 PM, Jan Kara wrote:
> > On Thu 08-02-18 14:28:08, Dmitry Vyukov wrote:
> >> On Thu, Feb 8, 2018 at 10:28 AM, Jan Kara wrote:
> >> > On Wed 07-02-18 07:52:29, Andi Kleen wrote:
> >> >> > #0: (>bd_mutex){+.+.}, at:
On Thu 08-02-18 06:49:18, Andi Kleen wrote:
> > > It seems multiple processes deadlocked on the bd_mutex.
> > > Unfortunately there's no backtrace for the lock acquisitions,
> > > so it's hard to see the exact sequence.
> >
> > Well, all in the report points to a situation where some IO was
This works with bool, int, hex, string types.
For bool, the symbol is set to 'y' or 'n' depending on the exit value
of the command.
For int, hex, string, the symbol is set to the value to the stdout
of the command. (only the first line of the stdout)
The following shows how to write this and
This function returns realloc'ed memory, so the returned pointer
must be passed to free() when done. Change the return value type
to save casting.
Signed-off-by: Masahiro Yamada
---
scripts/kconfig/lkc_proto.h | 2 +-
scripts/kconfig/symbol.c| 2 +-
scripts/kconfig/util.c | 4 ++--
3
Moving compiler option tests to Kconfig means you need to re-run
Kconfig when you update your compiler. All CC_HAS_... symbols
and other symbols that depend on them must be re-calculated.
It will be nice to detect the compiler update and automatically
invoke silentoldconfig.
This can be done by
Add CC_HAS_STACKPROTECTOR(_STRONG) and proper dependency.
I re-arranged the choice values, _STRONG, _REGULAR, _NONE in this order
because the default of choice is the first visible symbol.
TODO:
Broken stackprotector is not tested.
scripts/gcc-$(SRCARCH)_$(BITS)-has-stack-protector.sh should be
We have xmalloc(), xcalloc() already. Add xrealloc() as well to save
tedious error handling.
Signed-off-by: Masahiro Yamada
---
scripts/kconfig/confdata.c | 2 +-
scripts/kconfig/lkc.h | 1 +
scripts/kconfig/nconf.gui.c | 2 +-
scripts/kconfig/symbol.c| 2 +-
Em Thu, Feb 08, 2018 at 10:59:00AM -0500, Steven Rostedt escreveu:
> On Thu, 8 Feb 2018 12:20:31 +0100
> Jiri Olsa wrote:
>
> > > +Symbols (function names)
> > > +
> > > +
> > > +To display kallsyms "%pS" type of output, use the special type "symbol".
> > > +
> > >
With compiler flag tests moved to the configuration phase, the
result of $(call cc-option,...) will be cached in the .config file.
Remove kbuild cache to make it easier to move on.
Revert the following commits:
Commit 9a234a2e384349 ("kbuild: create directory for make cache only when
necessary")
Add minimum environments to start with.
Signed-off-by: Masahiro Yamada
---
init/Kconfig | 8
1 file changed, 8 insertions(+)
diff --git a/init/Kconfig b/init/Kconfig
index 64f9dd2..31fbc6e 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -25,6 +25,14 @@ config CC_VERSION_TEXT
On 02/08/2018 07:18 PM, Jan Kara wrote:
>> By "full kernel crashdump" you mean kdump thing, or something else?
>
> Yes, the kdump thing (for KVM guest you can grab the memory dump also from
> the host in a simplier way and it should be usable with the crash utility
> AFAIK).
>
In QEMU
This was prompted by the email from Linus today's morning.
I implmented this in a rush today, so there are still many TODOs,
but I put it here to start discussion.
I think it is working, but as you notice, it is tedious to repeat something
like follows:
config CC_HAS_STACKPROTECTOR
bool
On Thu, Feb 8, 2018 at 2:53 PM, Borislav Petkov wrote:
> On Thu, Feb 08, 2018 at 01:55:48PM +, Rolf Neugebauer wrote:
>> On the 4.4 kernel, 1f161f67a272c ("x86/microcode: Do the family check
>> first") does not apply cleanly. Looks like it relies on 309aac77768c0
>> ("x86/microcode: Decrease
On Thu, Feb 8, 2018 at 4:46 AM, Kai-Heng Feng
wrote:
> The affected system (0x0813) is pretty similar to another one (0x0812),
> it also needs to use ATPX power control.
>
> Signed-off-by: Kai-Heng Feng
Applied. thanks!
Alex
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c | 1 +
>
On Wed, Feb 07, 2018 at 06:29:18PM +0900, Sergey Senozhatsky wrote:
> Not every object can be share its zspage with other objects, e.g.
> when the object is as big as zspage or nearly as big a zspage.
> For such objects zsmalloc has a so called huge class - every object
> which belongs to huge
On Thu, Feb 08, 2018 at 01:03:49PM +0300, Kirill Tkhai wrote:
> On 07.02.2018 21:38, Dave Hansen wrote:
> > On 02/07/2018 08:14 AM, Kirill Tkhai wrote:
> >> Sometimes it is possible to meet a situation,
> >> when irq stack is corrupted, while innocent
> >> callback function is being executed. This
On 08/02/18 16:10, Dave Martin wrote:
On Thu, Feb 08, 2018 at 12:12:37PM +, Suzuki K Poulose wrote:
So far we have restricted the scopes for the capabilities
as follows :
1) Errata workaround check are run all CPUs (i.e, always
SCOPE_LOCAL_CPU)
2) Arm64 features are run only once
In this laptop we have the following PCI device:
02:00.0 Network controller [0280]: Broadcom Limited BCM43142 802.11b/g/n
[14e4:4365] (rev 01)
Subsystem: Hewlett-Packard Company BCM43142 802.11b/g/n [103c:804a]
[...]
Region 0: Memory at 9100 (64-bit, non-prefetchable)
On 02/08/2018 03:44 AM, Ulf Magnusson wrote:
> The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove
> support for AVR32 architecture").
You forgot the Signed-off-by tag.
> ---
> Changes in v2:
> Remove the AVR32 reference from the help text too.
>
> drivers/spi/Kconfig | 4
On Wed, Feb 07, 2018 at 04:31:59PM +, Rolf Neugebauer wrote:
> On Wed, Feb 7, 2018 at 2:34 PM, Greg KH wrote:
> > On Tue, Feb 06, 2018 at 03:24:44PM +0100, Borislav Petkov wrote:
> >> On Tue, Feb 06, 2018 at 02:09:35PM +, Rolf Neugebauer wrote:
> >> > The backport of 7e702d17ed1
@@ -1189,6 +1183,12 @@ static enum blk_eh_timer_return nvme_timeout(struct
request *req, bool reserved)
struct nvme_command cmd;
u32 csts = readl(dev->bar + NVME_REG_CSTS);
+ /* If PCI error recovery process is happening, we cannot reset or
+* the recovery mechanism
Hi Sakari,
On 02/07/2018 03:59 PM, Sakari Ailus wrote:
Hi Gustavo,
On Tue, Feb 06, 2018 at 10:47:50AM -0600, Gustavo A. R. Silva wrote:
Add suffix ULL to constants 1 and 100 in order to give the
compiler complete information about the proper arithmetic to use.
Notice that these
On Thu, Feb 08, 2018 at 04:25:58PM +, Rolf Neugebauer wrote:
> On Thu, Feb 8, 2018 at 2:53 PM, Borislav Petkov wrote:
> > On Thu, Feb 08, 2018 at 01:55:48PM +, Rolf Neugebauer wrote:
> >> On the 4.4 kernel, 1f161f67a272c ("x86/microcode: Do the family check
> >> first") does not apply
On 08/02/2018 16:54, Jim Mattson wrote:
> On Thu, Feb 8, 2018 at 7:29 AM, Jim Mattson wrote:
>> Similarly, the correct L1 CR4 value should be in vmcs01's CR4
>> read shadow field.
> Sorry; that's wrong. L1's CR4 value has to be reconstructed from the
> vmcs01 guest CR4 field and CR4 shadow field
On Thu, Feb 8, 2018 at 5:30 PM, Josh Poimboeuf wrote:
> On Thu, Feb 08, 2018 at 01:03:49PM +0300, Kirill Tkhai wrote:
>> On 07.02.2018 21:38, Dave Hansen wrote:
>> > On 02/07/2018 08:14 AM, Kirill Tkhai wrote:
>> >> Sometimes it is possible to meet a situation,
>> >> when irq stack is corrupted,
On Fri, Feb 09, 2018 at 01:19:05AM +0900, Masahiro Yamada wrote:
> This was prompted by the email from Linus today's morning.
>
> I implmented this in a rush today, so there are still many TODOs,
> but I put it here to start discussion.
>
> I think it is working, but as you notice, it is tedious
'USB devices not seen with newest kernel'
--
Cheers, Bev
In theory there is no difference between theory and practice,
but in practice there is.
Hi Philippe,
Thank you for the patch.
On Thursday, 8 February 2018 16:58:05 EET Philippe Cornu wrote:
> Add SPDX identifiers to the Synopsys DesignWare MIPI DSI
> host controller driver.
>
> Signed-off-by: Philippe Cornu
Reviewed-by: Laurent Pinchart
> ---
> Changes in v2: Update to
On Thu 2018-02-08 23:53:07, Sergey Senozhatsky wrote:
> On (02/08/18 14:04), Petr Mladek wrote:
> > We mark for waking up klogd whenever we see a new message sequence in
> > the main loop. However, the actual wakeup is always at the end of the
> > function and we can easily test for the wakeup
On 8 February 2018 at 16:44, Peter Zijlstra wrote:
> On Thu, Feb 08, 2018 at 04:05:58PM +0100, Vincent Guittot wrote:
>> On 8 February 2018 at 15:00, Peter Zijlstra wrote:
>> > On Tue, Feb 06, 2018 at 08:23:05PM +0100, Vincent Guittot wrote:
>> >
>> >> @@ -9207,13 +9231,15 @@ void
Hiya,
On 25 January 2018 at 17:55, Channagoud Kadabi wrote:
> Documentation for last level cache controller device tree bindings,
> client bindings usage examples.
[snippety snip]
> +- llcc-bank-off:
> + Usage: required
> + Value Type:
> + Definition: Offsets of llcc banks
On Thursday 08 February 2018 01:12:26 Alexander Abrosimov wrote:
> Fixed a mistake in which several entries were duplicated in the DMI list
> from the below commit
> fe486138 platform/x86: dell-laptop: Add 2-in-1 devices to the DMI whitelist
>
> Signed-off-by: Alexander Abrosimov
Reviewed-by:
On Thu, Feb 8, 2018 at 9:41 PM, Lynch, Nathan wrote:
>> I commented the device tree reading property:
>> arm,cpu-registers-not-fw-configured , from the arch/arm/kernel/vdso.c
>
> Don't do that, please. The presence of that property indicates that the
> counter is not suitable for use by the OS.
On 08/02/18 12:26, Marc Zyngier wrote:
On 08/02/18 12:19, Suzuki K Poulose wrote:
On 07/02/18 10:39, Dave Martin wrote:
On Wed, Jan 31, 2018 at 06:28:04PM +, Suzuki K Poulose wrote:
We defend against branch predictor training based exploits by
taking specific actions (based on the CPU
From: Arnd Bergmann
> Sent: 08 February 2018 15:23
...
> The Winchip is what eventually turned into the VIA Nano, which does
> have speculative execution, but I don't think the earlier C3 and C7 did,
> they are much closer to the original Winchip design.
We had terrible trouble getting (IIRC) the
When the SCHED_DEADLINE scheduling class increases the CPU utilization,
we should not wait for the rate limit, otherwise we may miss some deadline.
Tests using rt-app on Exynos5422 have shown reductions of about 10% of deadline
misses for tasks with low RT periods.
The patch applies on top of
On 02/08/2018 03:49 AM, Rafael J. Wysocki wrote:
On Wednesday, February 7, 2018 12:36:17 AM CET Gustavo A. R. Silva wrote:
Add suffix ULL to constant 500 in order to give the compiler complete
information about the proper arithmetic to use. Notice that this
constant is used in a context that
From: Borislav Petkov
commit 1f161f67a272cc4f29f27934dd3f74cb657eb5c4 upstream with adjustments.
On CPUs like AMD's Geode, for example, we shouldn't even try to load
microcode because they do not support the modern microcode loading
interface.
However, we do the family check *after* the other
From: Borislav Petkov
commit a15a753539eca8ba243d576f02e7ca9c4b7d7042 upstream with minor
adjustments.
Doing so is completely void of sense for multiple reasons so prevent
it. Set dis_ucode_ldr to true and thus disable the microcode loader by
default to address xen pv guests which execute the
2018-02-08 9:57 GMT+09:00 Kees Cook :
> On Thu, Feb 8, 2018 at 10:44 AM, Masahiro Yamada
> wrote:
>> 2018-02-08 2:55 GMT+09:00 Linus Torvalds :
>>> What I would really want - and this is entirely unrelated to this
>>> particular case - is to have those damn compiler option tests as part
>>> of
On 08/02/2018 16:00, Matthew Wilcox wrote:
> On Thu, Feb 08, 2018 at 03:35:58PM +0100, Laurent Dufour wrote:
>> I reviewed that part of code, and I think I could now change the way
>> pte_unmap_safe() is checking for the pte's value. Since we now have all the
>> needed details in the vm_fault
On 08-Feb-18 8:46 PM, Andy Shevchenko wrote:
> On Thu, Feb 8, 2018 at 2:55 PM, Vignesh R wrote:
>> Currently, data in RX FIFO is read based on UART_LSR register state even
>> if RDI and RLSI interrupts are disabled in UART_IER register.
>> This is because when IRQ handler is called due to TX
MC portals may not be available at the initial probing attempt
due to dependencies on other modules.
Check the return value of the MC portal allocation function and
defer probing in case it's not available yet. For all other error
cases the behaviour stays the same.
Signed-off-by: Ioana
On Thu, Feb 8, 2018 at 5:23 PM, Andrey Ryabinin wrote:
>
>
> On 02/08/2018 07:18 PM, Jan Kara wrote:
>
>>> By "full kernel crashdump" you mean kdump thing, or something else?
>>
>> Yes, the kdump thing (for KVM guest you can grab the memory dump also from
>> the host in a simplier way and it
On Thu, Feb 8, 2018 at 8:19 AM, Masahiro Yamada
wrote:
> This was prompted by the email from Linus today's morning.
Thanks.
> I implmented this in a rush today, so there are still many TODOs,
> but I put it here to start discussion.
>
> I think it is working, but as you notice, it is tedious to
On 08/02/18 11:00, Christoffer Dall wrote:
On Tue, Jan 09, 2018 at 07:04:03PM +, Suzuki K Poulose wrote:
On arm/arm64 we pre-allocate the entry level page tables when
a VM is created and is free'd when either all the mm users are
gone or the KVM is about to get destroyed. i.e,
On Thu, Feb 08, 2018 at 05:41:19PM +0100, Dmitry Vyukov wrote:
> On Thu, Feb 8, 2018 at 5:30 PM, Josh Poimboeuf wrote:
> > On Thu, Feb 08, 2018 at 01:03:49PM +0300, Kirill Tkhai wrote:
> >> On 07.02.2018 21:38, Dave Hansen wrote:
> >> > On 02/07/2018 08:14 AM, Kirill Tkhai wrote:
> >> >>
2018-02-09 1:19 GMT+09:00 Masahiro Yamada :
> Moving compiler option tests to Kconfig means you need to re-run
> Kconfig when you update your compiler. All CC_HAS_... symbols
> and other symbols that depend on them must be re-calculated.
>
> It will be nice to detect the compiler update and
On 08/02/18 11:01, Christoffer Dall wrote:
On Tue, Jan 09, 2018 at 07:04:04PM +, Suzuki K Poulose wrote:
We allocate the entry level page tables for stage2 when the
VM is created. This doesn't give us the flexibility of configuring
the physical address space size for a VM. In order to allow
On Thu, 8 Feb 2018 08:59:30 -0700
Mathieu Poirier wrote:
> On 7 February 2018 at 14:03, Kim Phillips wrote:
> > Commit 1c8859848dbb ("coresight replicator: Cleanup programmable
> > replicator naming") changed the Kconfig symbol name from
> > QCOM_REPLICATOR, which, whilst not in the single
On 08/02/18 11:00, Christoffer Dall wrote:
On Tue, Jan 09, 2018 at 07:04:09PM +, Suzuki K Poulose wrote:
Now that we can manage the stage2 page table per VM, switch the
configuration details to per VM instance. We keep track of the
IPA bits, number of page table levels and the VTCR bits
On Thu, 2018-02-08 at 15:35 +0100, Philippe Ombredanne wrote:
> However checking that licenses ids are known and listed in the kernel
> doc is essential IMHO to avoid drift and insulate the kernel from SPDX
> updates. Case in point the new SPDX "GPL-2.0-only" is NOT what was
> documented by tglx
On Thu, Feb 08, 2018 at 05:12:04PM +, Rolf Neugebauer wrote:
> From: Borislav Petkov
>
> commit 1f161f67a272cc4f29f27934dd3f74cb657eb5c4 upstream with adjustments.
This also seems to work for 4.9, thanks! Both now queued up.
greg k-h
On Thu, Feb 08, 2018 at 03:49:59AM +0100, Greg KH wrote:
> On Tue, Feb 06, 2018 at 09:05:46PM +, Woodhouse, David wrote:
> >
> >
> > On Tue, 2018-02-06 at 19:01 +0100, Paolo Bonzini wrote:
> > > On 06/02/2018 18:29, David Woodhouse wrote:
> > > > I've put together a linux-4.9.y branch at
>
On Thu, Feb 8, 2018 at 12:02 PM, David Laight wrote:
> From: Arnd Bergmann
>> Sent: 08 February 2018 15:23
> ...
>> The Winchip is what eventually turned into the VIA Nano, which does
>> have speculative execution, but I don't think the earlier C3 and C7 did,
>> they are much closer to the
On Tue, 30 Jan 2018 14:42:01 PST (-0800), antonynpav...@gmail.com wrote:
From: Palmer Dabbelt
As part of the MIPS conversion to use the generic GCC library routines,
Matt Redfearn discovered that I'd missed a notrace on __ucmpdi2(). This
patch rectifies the problem.
CC: Matt Redfearn
CC:
On Thu, Feb 8, 2018 at 1:13 AM, Peter Zijlstra wrote:
>
> _The_ problem is that new binutils cannot sanely decode any function
> that has a WARN in (this very much includes perf annotate):
Ugh.
Is there any reason why we don't just use UD2 and avoid this whole issue?
Do we even *do* anything
On Thu, Feb 08, 2018 at 04:31:47PM +, Suzuki K Poulose wrote:
> On 08/02/18 16:10, Dave Martin wrote:
> >On Thu, Feb 08, 2018 at 12:12:37PM +, Suzuki K Poulose wrote:
> >>So far we have restricted the scopes for the capabilities
> >>as follows :
> >> 1) Errata workaround check are run all
On Thu, Feb 8, 2018 at 5:02 AM, Peter Zijlstra wrote:
>
> Fix this by creating a 'jump-stack' which we can 'unwind' during
> reversal, thereby skipping over much of the in-between code.
I'm assuming this will come through the normal tip trees, since that's
where objtool stuff generally comes
On Wed, 31 Jan 2018 08:07:51 PST (-0800), matt.redfe...@mips.com wrote:
Hi,
On 31/01/18 15:33, Antony Pavlov wrote:
The commit b35cd9884fa5 ("lib: Add shared copies of
some GCC library routines") makes it possible
to share generic GCC library routines by several
architectures.
This commit
On 5 February 2018 at 01:21, Ulf Magnusson wrote:
> The MIPS_SEAD3 symbol was removed in commit 64601cb1343f ("leds: Remove SEAD-3
> driver").
>
> Remove the MIPS_SEAD3 dependency from IMG_ASCII_LCD.
Its not a dependency, just a default (presumably so that existing
kernel configs get updated
Hi Huang,
On Thu, Feb 08, 2018 at 11:27:50PM +0800, huang ying wrote:
> On Wed, Feb 7, 2018 at 3:00 PM, Huang, Ying wrote:
> > From: Huang Ying
> >
> > It was reported by Sergey Senozhatsky that if THP (Transparent Huge
> > Page) and frontswap (via zswap) are both enabled, when memory goes low
If it was interrupted by a signal, the 9p client may need to send some
more requests to the server for cleanup before returning to userspace.
To avoid such a last minute request to be interrupted right away, the
client memorizes if a signal is pending, clear TIF_SIGPENDING, handle
the request and
On Thu, Feb 8, 2018 at 1:47 AM, Ingo Molnar wrote:
>
> So for those reasons I'm really tempted by the all around simplification
> offered
> by this series:
>
>2 files changed, 62 insertions(+), 160 deletions(-)
>
> Basically in this specific case I'd like to turn the argument around,
> use
1101 - 1200 of 1548 matches
Mail list logo
