What is an estimate for the total number of exploitable bugs in the
current stable linux kernel? (Jul 24 07:59:50 UTC 2017) Total
includes private and unknown bugs too.
Also does the number decrease, increase or change in other way over
time?
If the answer is rather hard or well, ``undecidable''
Hi,
On 7/24/2017 2:45 PM, Baolin Wang wrote:
> Hi Manu,
>
> On 24 July 2017 at 16:42, Manu Gautam wrote:
>> Hi Baolin,
>>
>>
>> On 7/24/2017 11:26 AM, Baolin Wang wrote:
>>
>> Other than what I pushed in my patch -
>> ("usb: dwc3: Don't reinitialize core during host bus-suspend/resume")
Nadav Amit report zap_page_range only specifies that the caller protect
the VMA list but does not specify whether it is held for read or write
with callers using either. madvise holds mmap_sem for read meaning that a
parallel zap operation can unmap PTEs which are then potentially skipped
by madvis
The first version is in [1].
Got -EBUSY from zs_page_migrate will make migration
slow (retry) or fail (zs_page_putback will schedule_work free_work,
but it cannot ensure the success).
I noticed this issue because my Kernel patched [2]
that will remove retry in __alloc_contig_migrate_range.
This r
On 08/07/17 06:32, Jassi Brar wrote:
> Hi Roy, Matt, Nishant, Harb Abdulhamid, Loc,
>
> I have a gut feeling you guys were part of the SCMI spec committee. If
> so, could you please chime in?
>
I take complete silence as no objection.
>
> On Fri, Jul 7, 2017 at 11:09 PM, Sudeep Holla wrote:
On 7/21/2017 10:29 PM, Stephen Boyd wrote:
> On 07/21/2017 04:01 AM, Manu Gautam wrote:
>> From: Vivek Gautam
>>
>> Pipe clock comes out of the phy and is available as long as
>> the phy is turned on. Clock controller fails to gate this
>> clock after the phy is turned off and generates a warnin
Make sure that the controller is runtime resumed when system suspending
to avoid an external abort when accessing the interrupt registers:
Unhandled fault: external abort on non-linefetch (0x1008) at 0xd025840a
...
[] (musb_default_readb) from []
(musb_disable_interrupts+0x84/0xa8)
[] (mu
Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a
device with an active child"), which went into 4.10, it is no longer
permitted to set RPM_SUSPENDED state for a device with active children
(unless power.ignore_children is set).
This specifically means that the attempts to do just
Hi,
gustavo panizzo writes:
>>> On Wed, Jul 12, 2017 at 02:08:04PM +0800, Baolin Wang wrote:
Hi,
On 12 July 2017 at 11:52, gustavo panizzo wrote:
>
> The dwc3 could not release resources when the module is built-in
> because this module does not have shutdown met
Since commit a8636c89648a ("PM / Runtime: Don't allow to suspend a
device with an active child") it is no longer permitted to set
RPM_SUSPENDED state for a device with active children unless
power.ignore_children is set.
Update the documentation to reflect this.
Cc: Alan Stern
Cc: Tony Lindgren
commit bdfb95c4baab ("staging: greybus: remove timesync protocol support")
commit 1e029b836108 ("staging: greybus: arche: remove timesync remains")
Subtract timesync from greybus/staging but haven't updated MAINTAINERS
appropriately. Fix that omission now.
Signed-off-by: Bryan O'Donoghue
---
MA
On 7/21/2017 10:39 PM, Stephen Boyd wrote:
> On 07/21/2017 04:02 AM, Manu Gautam wrote:
>> Driver currently notifies only USB3 PHY for mode change.
>> Extend this to USB3 PHY so that driver based on the mode
>> can release system resources - clocks, regulators etc.
>> and can even turn off PHY du
Hi,
On 7/21/2017 10:54 PM, Stephen Boyd wrote:
> On 07/21/2017 04:01 AM, Manu Gautam wrote:
>> Driver can turn off clocks during runtime suspend.
>> Also, runtime suspend is not as a result of host mode
>> selective suspend then PHY can be powered off as well.
>>
>> Signed-off-by: Manu Gautam
>>
Commit
9a93848fe787 ("x86/debug: Implement __WARN() using UD0")
turned warnings into UD0, but the fixup code only runs after the
notify_die() chain. This is a problem, in particular, with kgdb,
which kicks in as if it was a BUG().
Fix this by running the fixup code before the notifier chain in
Hello Seeteena,
Thanks for this useful patch. Couple of suggestions below.
On Thu, Jul 6, 2017 at 12:44 PM, Seeteena Thoufeek
wrote:
> ---Steps to Reproduce---
>
> 1.Execute the cpupower monitor command to fetch all the Idle_Stats values.
>
> root:~# cpupower monitor
> |Idle_Stats
From: Shu Wang
verify_and_add_patch() allocates memory for a microcode patch and hands
it down to be added to the cache of patches. However, if the cache
already has the latest patch, the newly allocated one needs to be freed
before returning. Do that.
This issue has been found by kmemleak:
u
From: Borislav Petkov
Hi guys,
some fixes that got ready in the meantime. Yazen's goes to tip:ras/core
and the other two to tip:x86/microcode.
Thanks.
Borislav Petkov (1):
x86/microcode: Document the three loading methods
Shu Wang (1):
x86/microcode/AMD: Free unneeded patch before exit fr
From: Borislav Petkov
Paul Menzel asked recently how to load microcode
on a system and I realized that we don't really have all the methods
written down somewhere. Do that, so people can go and look them up.
Signed-off-by: Borislav Petkov
---
Documentation/x86/early-microcode.txt | 70 --
From: Yazen Ghannam
Current SMCA implementations have the same banks on each CPU with the
non-core banks only visible to a "master thread" on each die. Practically,
this means the smca_banks array, which describes the banks, only needs to
be populated once by a single master thread.
CPU 0 seemed
On Mon, Jul 24, 2017 at 01:04:28PM +0300, Alexander Shishkin wrote:
> Commit
>
> 9a93848fe787 ("x86/debug: Implement __WARN() using UD0")
>
> turned warnings into UD0, but the fixup code only runs after the
> notify_die() chain. This is a problem, in particular, with kgdb,
> which kicks in as i
Commit-ID: c3f02682a101b83424128915b14e60c156c03f02
Gitweb: http://git.kernel.org/tip/c3f02682a101b83424128915b14e60c156c03f02
Author: Kan Liang
AuthorDate: Thu, 13 Jul 2017 10:35:47 -0700
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:13:18 +0200
perf/x86/intel/uncore: Fix Sky
Commit-ID: bab4e569e80c07ba6fe5e4f2d815adeef26cee94
Gitweb: http://git.kernel.org/tip/bab4e569e80c07ba6fe5e4f2d815adeef26cee94
Author: Kan Liang
AuthorDate: Thu, 13 Jul 2017 10:35:46 -0700
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:13:18 +0200
perf/x86/intel/uncore: Fix Sky
Commit-ID: 8aa7b7b4b4a601978672dce6604b9f5630b2eeb8
Gitweb: http://git.kernel.org/tip/8aa7b7b4b4a601978672dce6604b9f5630b2eeb8
Author: Stephane Eranian
AuthorDate: Thu, 13 Jul 2017 10:35:49 -0700
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:13:18 +0200
perf/x86/intel/uncore:
Commit-ID: 38115f2f8cec8087d558c062e779c443a01f87d6
Gitweb: http://git.kernel.org/tip/38115f2f8cec8087d558c062e779c443a01f87d6
Author: Masami Hiramatsu
AuthorDate: Fri, 21 Jul 2017 23:45:52 +0900
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:14:59 +0200
kprobes/x86: Release in
Commit-ID: 80b9ece133937f08da46fa2383019fcf4374
Gitweb: http://git.kernel.org/tip/80b9ece133937f08da46fa2383019fcf4374
Author: Andy Shevchenko
AuthorDate: Fri, 30 Jun 2017 20:09:30 +0300
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:18:20 +0200
x86/io: Define IO access
Commit-ID: ba883b4abc9cd837441b01eb9cf8d9196181294d
Gitweb: http://git.kernel.org/tip/ba883b4abc9cd837441b01eb9cf8d9196181294d
Author: Stephane Eranian
AuthorDate: Thu, 13 Jul 2017 10:35:50 -0700
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:13:18 +0200
perf/x86/intel/uncore:
Commit-ID: 9ad0fbd8fcd9e6815908c772f8d792a9d764449e
Gitweb: http://git.kernel.org/tip/9ad0fbd8fcd9e6815908c772f8d792a9d764449e
Author: Kan Liang
AuthorDate: Thu, 13 Jul 2017 10:35:48 -0700
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:13:18 +0200
perf/x86/intel/uncore: Remove
Commit-ID: 3195201198aad06c151dcfcb09e2fff79b2fda0e
Gitweb: http://git.kernel.org/tip/3195201198aad06c151dcfcb09e2fff79b2fda0e
Author: Andy Shevchenko
AuthorDate: Fri, 30 Jun 2017 20:09:31 +0300
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:18:21 +0200
x86/io: Include asm-gene
On Fri, Jul 21, 2017 at 04:09:09PM +0200, Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> Fix the cases of . when any of three inputs is any
> NaN. Correct behavior of . fd, fs, ft is following:
>
> - if any of inputs is sNaN, return a sNaN using following rules: if
> only one i
Commit-ID: eabc2a7c49c01fc97ff8c764ef7d74276b904af6
Gitweb: http://git.kernel.org/tip/eabc2a7c49c01fc97ff8c764ef7d74276b904af6
Author: Andy Shevchenko
AuthorDate: Fri, 30 Jun 2017 20:09:33 +0300
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:18:21 +0200
x86/io: Remove xlate_dev
Commit-ID: c2327da06b33d8e1093ce2c28f395bc500d1b0d3
Gitweb: http://git.kernel.org/tip/c2327da06b33d8e1093ce2c28f395bc500d1b0d3
Author: Andy Shevchenko
AuthorDate: Fri, 30 Jun 2017 20:09:32 +0300
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:18:21 +0200
x86/io: Remove mem*io()
Commit-ID: 9683a64fc3cb67e663859a6bb2e0db5dcee9ed32
Gitweb: http://git.kernel.org/tip/9683a64fc3cb67e663859a6bb2e0db5dcee9ed32
Author: Andy Shevchenko
AuthorDate: Fri, 30 Jun 2017 20:09:34 +0300
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:18:21 +0200
x86/io: Make readq() / w
Commit-ID: b3625980a65db6b6b6bbd5790a77ab95ce6397c5
Gitweb: http://git.kernel.org/tip/b3625980a65db6b6b6bbd5790a77ab95ce6397c5
Author: Stephane Eranian
AuthorDate: Thu, 13 Jul 2017 10:35:45 -0700
Committer: Ingo Molnar
CommitDate: Mon, 24 Jul 2017 11:13:17 +0200
perf/x86/intel/uncore:
This series adds support for the PMU in ARM DynamIQ Shared Unit (DSU).
The DSU integrates one or more cores with an L3 memory system, control
logic, and external interfaces to form a multicore cluster. The PMU
allows counting the various events related to L3, SCU etc, using 32bit
independent counte
Export perf_event_update_userpage() so that PMU driver using them,
can be built as modules.
Cc: Peter Zilstra
Signed-off-by: Suzuki K Poulose
---
kernel/events/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 426c2ff..21aad7a 100644
--
Use the new generic helper of_device_node_get_cpu() instead
of using our own version to map a device node to logical CPU
number.
Cc: Marc Zyngier
Signed-off-by: Suzuki K Poulose
---
drivers/irqchip/irq-gic-v3.c | 30 +++---
1 file changed, 3 insertions(+), 27 deletions(-
Add support for the Cluster PMU part of the ARM DynamIQ Shared Unit (DSU).
The DSU integrates one or more cores with an L3 memory system, control
logic, and external interfaces to form a multicore cluster. The PMU
allows counting the various events related to L3, SCU etc, along with
providing a cyc
Add a helper to map a device node to a logical CPU number to avoid
duplication. Currently this is open coded in different places (e.g
gic-v3, coresight). The helper tries to map device node to a "possible"
logical CPU id, which may not be online yet. It is the responsibility
of the user to make sur
Reuse the new generic helper, of_device_node_get_cpu() to map a
given CPU phandle to a logical CPU number.
Cc: Mathieu Poirier
Cc: Leo Yan
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/of_coresight.c | 20 ++--
1 file changed, 6 insertions(+), 14 deletions(-)
This patch documents the devicetree bindings for ARM DSU PMU.
Cc: Mark Rutland
Cc: Will Deacon
Cc: Rob Herring
Signed-off-by: Suzuki K Poulose
---
.../devicetree/bindings/arm/arm-dsu-pmu.txt| 28 ++
1 file changed, 28 insertions(+)
create mode 100644 Documentation
On 23/07/17 05:56, kbuild test robot wrote:
Hi Ian,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 96080f697786e0a30006fcbcc5b53f350fcb3e9f
commit: c7acec713d14c6ce8a20154f9dfda258d6bcad3b kernel.h: handle pointer
On 23-07-17, 09:20, Ulf Hansson wrote:
> I should have been more clear. Walking the master list, then checking
> each link without using locks - why is that safe?
>
> Then even if you think it's safe, then please explain in detail why its
> needed.
>
> Walking the slave list as being done for po
On Sun, Jul 23, 2017 at 01:25:56AM -0500, Gustavo A. R. Silva wrote:
> Lesson learned, your original script should remain as is. :)
Ok, then please send Julia's script as a separate patch and then in the
EDAC patch, reference the path to that coccinelle patch so that it is
clear what has been used
On Wed, Jul 19, 2017 at 05:01:27PM +0100, Mark Rutland wrote:
> To allow EL0 (and/or EL1) to use pointer authentication functionality,
> we must ensure that pointer authentication instructions and accesses to
> pointer authentication keys are not trapped to EL2 (where we will not be
> able to handl
ATENCIÓN;
Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por
el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser
capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de
correo electrónico. Para revalidar su buzón de corr
On Sat, Jul 22, 2017 at 12:15:42AM +0200, Rafael J. Wysocki wrote:
[...]
> > + * acpi_dma_get_range() - Get device DMA parameters.
> > + *
> > + * @dev: device to configure
> > + * @dma_addr: pointer device DMA address result
> > + * @offset: pointer to the DMA offset result
> > + * @size: pointe
On Fri, Jul 21, 2017 at 04:09:10PM +0200, Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> Fix the cases of . when any of two multiplicands is
> infinity. The correct behavior in such cases is affected by the nature
> of third input. Cases of addition of infinities with opposite signs
>
Hi Wang cong,
After apply the patch, I did not hit the issue again.
Thank you~
Best Regards,
liujian
> -Original Message-
> From: Dingtianhong
> Sent: Monday, July 24, 2017 9:29 AM
> To: Cong Wang; liujian (CE)
> Cc: Willem de Bruijn; Dave Jones; alexander.le...@verizon.com;
> da...@dav
Laurent Vivier writes:
> As for commit 68baf692c435 ("powerpc/pseries: Fix of_node_put()
> underflow during DLPAR remove"), the call to of_node_put()
> must be removed from pSeries_reconfig_remove_node().
>
> dlpar_detach_node() and pSeries_reconfig_remove_node() call
> of_detach_node(), and thus
On Sat, Jul 22, 2017 at 4:09 PM, Namhyung Kim wrote:
> On Fri, Jul 21, 2017 at 01:02:50PM -0700, David Carrillo-Cisneros wrote:
>> On Fri, Jul 21, 2017 at 12:44 AM, Jiri Olsa wrote:
>> > On Thu, Jul 20, 2017 at 10:11:57PM -0700, David Carrillo-Cisneros wrote:
>> >> Fixes bug noted by Jiri in http
+Cc: Mika
On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Avoid hogging chip select GPIOs just because they are listed for the
> master. They might be mulitplexed and, if no slave device is attached,
> used for different purposes. Moreover, this strategy avoids having t
On 21/07/17 18:05, Dave Martin wrote:
On Wed, Jul 19, 2017 at 05:01:22PM +0100, Mark Rutland wrote:
We don't document our ELF hwcaps, leaving developers to interpret them
according to hearsay, guesswork, or (in exceptional cases) inspection of
the current kernel code.
This is less than optimal,
On 2017/07/24 14:34:07 +0800, Boqun Feng wrote:
> On Mon, Jul 24, 2017 at 09:04:57AM +0900, Akira Yokosawa wrote:
> [...]
>>>
>>> ->8
>>> Subject: [PATCH] kernel: Emphasize the return value of READ_ONCE() is
>>> honored
>>>
>>> READ_ONCE() is used around in kernel to provide a cont
Hi Guenter & all,
On Monday, 24 July 2017 01:39:37 BST Guenter Roeck wrote:
> The MIPS Boston board configuration tries to enable CONFIG_PCIE_XILINX.
> That doesn't work since PCIE_XILINX depends on ARCH_ZYNQ || MICROBLAZE.
> Remove that restriction.
I'd prefer that this patch does not go in stan
Am Donnerstag, den 20.07.2017, 18:53 +0800 schrieb Jeffy Chen:
> Currently we are calling usb_submit_urb directly to submit deferred tx
> urbs after unanchor them.
>
> So the usb_giveback_urb_bh would failed to unref it in usb_unanchor_urb
> and cause memory leak:
> unreferenced object 0xffc0c
On 2017-07-24 12:44, Andy Shevchenko wrote:
> +Cc: Mika
>
> On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> Avoid hogging chip select GPIOs just because they are listed for the
>> master. They might be mulitplexed and, if no slave device is attached,
>> used for diff
bnx2fc_process_new_cqes() has protection against CPU hotplug, which relies
on the per cpu thread pointer. This protection is racy because it happens
only partially with the per cpu fp_work_lock held.
If the CPU is unplugged after the lock is dropped, the wakeup code can
dereference a NULL pointer
On 19/07/17 17:01, Mark Rutland wrote:
From ARMv8.3 onwards, ID_AA64ISAR1 is no longer entirely RES0, and now
has four fields describing the presence of pointer authentication
functionality:
* APA - address authentication present, using an architected algorithm
* API - address authentication pre
The CPU hotplug related code of this driver can be simplified by:
1) Consolidating the callbacks into a single state. The CPU thread can be
torn down on the CPU which goes offline. There is no point in delaying
that to the CPU dead state
2) Let the core code invoke the online/offline callba
The conversion of the cpu hotplug locking to a percpu rwsem does not longer
allow recursive locking of the hotplug lock.
The BNX2I and BNX2FC drivers install/remove hotplug states with the hotplug
lock held. The install/removal code acquired the hotplug lock as well.
While looking into this, I no
The BNX2I module init/exit code installs/removes the hotplug callbacks with
the cpu hotplug lock held. This worked with the old CPU locking
implementation which allowed recursive locking, but with the new percpu
rwsem based mechanism this is not longer allowed.
Use the _cpuslocked() variants to fi
The BNX2FC module init/exit code installs/removes the hotplug callbacks with
the cpu hotplug lock held. This worked with the old CPU locking
implementation which allowed recursive locking, but with the new percpu
rwsem based mechanism this is not longer allowed.
Use the _cpuslocked() variants to f
The CPU hotplug related code of this driver can be simplified by:
1) Consolidating the callbacks into a single state. The CPU thread can be
torn down on the CPU which goes offline. There is no point in delaying
that to the CPU dead state
2) Let the core code invoke the online/offline callba
On 21-07-17, 15:03, Peter Zijlstra wrote:
> On Thu, Jul 13, 2017 at 12:14:37PM +0530, Viresh Kumar wrote:
> > @@ -42,6 +42,7 @@ void cpufreq_add_update_util_hook(int cpu, struct
> > update_util_data *data,
> > return;
> >
> > data->func = func;
> > + data->cpu = cpu;
> > r
On Mon, Jul 24, 2017 at 1:53 PM, Jan Kiszka wrote:
> On 2017-07-24 12:44, Andy Shevchenko wrote:
>> +Cc: Mika
>>
>> On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote:
>>> From: Jan Kiszka
>>>
>>> Avoid hogging chip select GPIOs just because they are listed for the
>>> master. They might be mulit
On Fri, 2017-07-21 at 07:51 -0700, João Paulo Rechi Vita wrote:
> These messages are not reporting a real error, just the fact that the
> firmware knows about more flags then the driver.
>
> Currently these messages are presented to the user during boot if there
> is no bootsplash covering the con
On 2017-07-24 13:02, Andy Shevchenko wrote:
> On Mon, Jul 24, 2017 at 1:53 PM, Jan Kiszka wrote:
>> On 2017-07-24 12:44, Andy Shevchenko wrote:
>>> +Cc: Mika
>>>
>>> On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote:
From: Jan Kiszka
Avoid hogging chip select GPIOs just because th
Hugh Dickins wrote:
> On Thu, 20 Jul 2017, Tetsuo Handa wrote:
> > Hugh Dickins wrote:
> > > You probably won't welcome getting into alternatives at this late stage;
> > > but after hacking around it one way or another because of its pointless
> > > lockups, I lost patience with that too_many_isola
On Mon, Jul 24, 2017 at 2:06 PM, Jan Kiszka wrote:
> On 2017-07-24 13:02, Andy Shevchenko wrote:
>> On Mon, Jul 24, 2017 at 1:53 PM, Jan Kiszka wrote:
>>> On 2017-07-24 12:44, Andy Shevchenko wrote:
+Cc: Mika
On Sat, Jul 8, 2017 at 11:41 AM, Jan Kiszka wrote:
> From: Jan Kiszk
On Mon, Jul 24, 2017 at 04:22:45AM -0500, Suravee Suthikulpanit wrote:
> For family17h, current cpu_core_id is directly taken from the value
> CPUID_Fn801E_EBX[7:0] (CoreId), which is the physical ID of the
> core within a die. However, on system with downcore configuration
> (where not all phy
On Sat 22-07-17 09:21:31, Dan Williams wrote:
> On Fri, Jul 21, 2017 at 3:39 PM, Ross Zwisler
> wrote:
> > To be able to use the common 4k zero page in DAX we need to have our PTE
> > fault path look more like our PMD fault path where a PTE entry can be
> > marked as dirty and writeable as it is f
On Fri 21-07-17 11:44:05, Ross Zwisler wrote:
> On Wed, Jul 19, 2017 at 03:58:31PM -0600, Ross Zwisler wrote:
> > On Wed, Jul 19, 2017 at 11:51:12AM -0600, Ross Zwisler wrote:
> > > On Wed, Jul 19, 2017 at 04:16:59PM +0200, Jan Kara wrote:
> > > > On Wed 28-06-17 16:01:48, Ross Zwisler wrote:
> > >
> @@ -1658,14 +1658,28 @@ static int insert_pfn(struct vm_area_struct *vma,
> unsigned long addr,
> if (!pte)
> goto out;
> retval = -EBUSY;
> - if (!pte_none(*pte))
> - goto out_unlock;
> + if (!pte_none(*pte)) {
> + if (mkwrite) {
> +
pinion
> every 6 months. It's just that I will revisit periodically the progress
> on automated testing, public availability of a cross-toolchain,
> Tested/Acked/Reviewed-by tags on these patches from interested parties.
> Since I haven't seen any of these now, I don't see an
On Mon, Jul 24, 2017 at 11:05:49AM +0100, Bryan O'Donoghue wrote:
> commit bdfb95c4baab ("staging: greybus: remove timesync protocol support")
> commit 1e029b836108 ("staging: greybus: arche: remove timesync remains")
>
> Subtract timesync from greybus/staging but haven't updated MAINTAINERS
> app
On Fri, Jul 21, 2017 at 11:02 PM, Arnd Bergmann wrote:
> gcc-7 produces this warning:
>
> mm/kasan/report.c: In function 'kasan_report':
> mm/kasan/report.c:351:3: error: 'info.first_bad_addr' may be used
> uninitialized in this function [-Werror=maybe-uninitialized]
>print_shadow_for_address
On Fri 21-07-17 16:39:52, Ross Zwisler wrote:
> dax_load_hole() will soon need to call dax_insert_mapping_entry(), so it
> needs to be moved lower in dax.c so the definition exists.
>
> dax_wake_mapping_entry_waiter() will soon be removed from dax.h and be made
> static to dax.c, so we need to mov
Simplify and improve the code so that the PID is always available in
the uevent even when debugfs is not available.
This adds a userspace_pid field to struct kvm, as per Radim's
suggestion, so that the PID can be retrieved on destruction too.
Acked-by: Janosch Frank
Fixes: 286de8f6ac9202 ("KVM:
Hi Manu,
On 24 July 2017 at 17:38, Manu Gautam wrote:
> Hi,
>
>
> On 7/24/2017 2:45 PM, Baolin Wang wrote:
>> Hi Manu,
>>
>> On 24 July 2017 at 16:42, Manu Gautam wrote:
>>> Hi Baolin,
>>>
>>>
>>> On 7/24/2017 11:26 AM, Baolin Wang wrote:
>>>
>>> Other than what I pushed in my patch -
>>
On Monday, July 24, 2017 05:43:14 AM Huaisheng HS1 Ye wrote:
> After commit 82b4e03e01bc (intel_pstate: skip scheduler hook when
> in "performance" mode) Software P-state control modes couldn't get
> dynamic value during performance mode,
Please explain what you mean here.
I guess you carried out
On Fri 21-07-17 16:39:53, Ross Zwisler wrote:
> When servicing mmap() reads from file holes the current DAX code allocates
> a page cache page of all zeroes and places the struct page pointer in the
> mapping->page_tree radix tree. This has three major drawbacks:
>
> 1) It consumes memory unneces
On Fri, Jul 21, 2017 at 04:09:11PM +0200, Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> Fix the cases of . when any of two multiplicands is
> +0 or -0, and the third input is also +0 or -0. Depending on the signs
> of inputs, certain special cases must be handled.
>
> The relevant e
On Fri 21-07-17 16:39:54, Ross Zwisler wrote:
> Now that we no longer insert struct page pointers in DAX radix trees we can
> remove the special casing for DAX in page_cache_tree_insert(). This also
> allows us to make dax_wake_mapping_entry_waiter() local to fs/dax.c,
> removing it from dax.h.
>
On 07/21/2017 10:44 PM, Stephen Boyd wrote:
> On 07/09, Rob Herring wrote:
>> On Thu, Jul 06, 2017 at 12:24:23PM +0200, Neil Armstrong wrote:
>>> On the first revision of the bindings, only the gates + resets were known
>>> in the AO Clock HW, but more registers used to configures AO clock are know
On Fri 21-07-17 16:39:55, Ross Zwisler wrote:
> Now that we no longer insert struct page pointers in DAX radix trees the
> page cache code no longer needs to know anything about DAX exceptional
> entries. Move all the DAX exceptional entry definitions from dax.h to
> fs/dax.c.
>
> Signed-off-by:
On 19/07/17 17:01, Mark Rutland wrote:
* Should the kernel remove PACs when unwinding user stacks?
This is simple to do, but it's arguably placing a policy in the kernel as to
what we expect user stacks to look like. Regardless, userspace will have to
perform this when unwinding with DWARF
On Monday, July 24, 2017 02:23:49 PM Viresh Kumar wrote:
> On 23-07-17, 18:27, Icenowy Zheng wrote:
> > Some new Allwinner SoCs get supported in the kernel after the
> > compatibles are added to cpufreq-dt-platdev driver.
> >
> > Add their compatible strings in the cpufreq-dt-platdev driver.
> >
Hi,
sorry for the delay!
> > Uwe Kleine-König had the idea to disable DMA on the i.MX6dl based
> platform via dts and this is our current workaround.
>
> Please test Ian's patch:
> http://marc.info/?l=linux-serial&m=150005865213531&w=2
>
> It should fix this DMA problem with RS485.
With this p
Hi,
this trigger for this is out-of-tree [1], but my understanding so far is
that this is an in-tree issue:
[ 14.841871] ==
[ 14.841874] WARNING: possible circular locking dependency detected
[ 14.841878] 4.13.0-rc2-dbg+ #174 Tainted: G
Hi,all
Sorry to bother you, could you spare some time to help review patch v6 that I
sended. Would you please give us your opinion?
Thnak you very much.
-邮件原件-
发件人: liwei (CM)
发送时间: 2017年7月6日 15:03
收件人: 'Guodong Xu'; Jaehoon Chung
抄送: Ulf Hansson; adrian.hun...@intel.com; Shawn Lin;
On Mon, 2017-07-24 at 13:47 +0200, Neil Armstrong wrote:
> On 07/21/2017 10:44 PM, Stephen Boyd wrote:
> > On 07/09, Rob Herring wrote:
> > > On Thu, Jul 06, 2017 at 12:24:23PM +0200, Neil Armstrong wrote:
> > > > On the first revision of the bindings, only the gates + resets were
> > > > known
> >
Hi
I've problem with my USB storage devices: WD Elements 1TB.
(Bus 004 Device 002: ID 1058:10a8 Western Digital Technologies, Inc. Elements
Portable (WDBUZG))
After kernel >4.9 when disk is attached via cable it has very low speed
(less then 1MB/s).
It can run at full speed (>22MB/s) whe
Hi Jaegeuk,
Below is the error message I got from this testcase:
---
write (Invalid argument) len 1024 dio [dax to nondax | both nodax]
read (Bad address) len [4096 | 16777216 | 67108864] dio dax to nondax
---
The write error is expected, as F2FS does not support unaligned direct
IO (1024 B).
On Fri, Jul 21, 2017 at 04:09:14PM +0200, Aleksandar Markovic wrote:
> From: Aleksandar Markovic
>
> Fix definition and usage of maddf_flags enumeration. Avoid duplicate
> definition and apply more common capitalization.
>
> This patch does not change any scenario. It just make MADDF and MSUBF
>
On 07/23/2017 07:03 PM, Joseph Kogut wrote:
> Hi Kevin,
>
> I tested on a P212 reference board, which is currently the only GXL
> based board I have.
>
> Before applying the patch, high activity on the ethernet interface
> would cause the link to break, requiring the interface to be brought
> dow
Peter Zijlstra writes:
> On Mon, Jul 24, 2017 at 04:38:06PM +1000, Michael Ellerman wrote:
>
>> What I'm not entirely clear on is what the best trade off is in terms of
>> overhead vs checks. The summary of behaviour between the fast and full
>> versions you promised Ingo will help there I think.
RHEL 7.x and clone distros are shipped with Sphinx 1.1.x,
with is incompatible with Kernel ReST markups.
So, on those systems, the only alternative is to install
it via a Python virtual environment.
While seeking for "pip" on CentOS 7.3, I noticed that it
is not really needed, as python-virtualen
Em Sun, 23 Jul 2017 20:01:44 -0300
Mauro Carvalho Chehab escreveu:
> Em Sun, 23 Jul 2017 16:08:29 -0600
> Jonathan Corbet escreveu:
>
> > On Mon, 17 Jul 2017 18:46:34 -0300
> > Mauro Carvalho Chehab wrote:
> >
> > > Sphinx installation is not trivial, as not all versions are supported,
> >
On Thu, Jul 13, 2017 at 05:19:22PM +0300, Andrey Ryabinin wrote:
> >> https://git.kernel.org/pub/scm/linux/kernel/git/kas/linux.git/commit/?h=la57/boot-switching/v2&id=13327fec85ffe95d9c8a3f57ba174bf5d5c1fb01
> >>
> >>> As for KASAN, I think it would be better just to make it work faster,
> >>> the
On Fri, Jul 21, 2017 at 06:15:26PM +0100, Marc Zyngier wrote:
> It is an unfortunate situation that CNTFRQ{,_EL0} is often
> misprogrammed from the firmware side, leaving it up to the kernel to
> work around it. This is usually done by providing an alternative
> frequency in the Device Tree.
>
> U
101 - 200 of 1020 matches
Mail list logo