Commit-ID: 2decec48b0fd28ffdbf4cc684bd04e735f0839dd
Gitweb: https://git.kernel.org/tip/2decec48b0fd28ffdbf4cc684bd04e735f0839dd
Author: Raphael Gault
AuthorDate: Tue, 14 May 2019 17:47:46 -0500
Committer: Ingo Molnar
CommitDate: Wed, 15 May 2019 07:57:50 +0200
objtool: Fix whitelist
Enable USB3 HW LPM feature for lx2160a and active patch for
snps erratum A-010131. It will disable U1/U2 temperary when
initiate U3 request.
Signed-off-by: Ran Wang
---
Depend on: https://lore.kernel.org/patchwork/patch/870134/
arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi |4
1
On Wed, May 15, 2019 at 07:18:30AM +0200, Greg Kroah-Hartman wrote:
> On Wed, May 15, 2019 at 02:22:06PM +0930, Joel Stanley wrote:
> > This fixes a build break introduced in with the recent round of CPU
> > bug patches.
> >
> > arch/powerpc/kernel/security.c: In function
On 5/14/19 11:53 PM, Jeff Kletsky wrote:
> From: Jeff Kletsky
That #define in $subject is called a macro.
Seems this patch adds a lot of almost duplicate code, can it be somehow
de-duplicated ?
> The GigaDevice GD5F1GQ4UFxxG SPI NAND utilizes three-byte addresses
> for its page-read ops.
>
>
Strict module RWX is just like strict kernel RWX, but for modules - so
loadable modules aren't marked both writable and executable at the same
time. This is handled by the generic code in kernel/module.c, and
simply requires the architecture to implement the set_memory() set of
functions,
On (05/14/19 21:13), Geert Uytterhoeven wrote:
> I would immediately understand there's a missing IS_ERR() check in a
> function that can return -EINVAL, without having to add a new printk()
> to find out what kind of bogus value has been received, and without
> having to reboot, and trying to
Hi.
On Tue, May 14, 2019 at 04:51:22PM +0200, Michal Hocko wrote:
> [Forgot Hugh]
>
> On Tue 14-05-19 16:41:05, Michal Hocko wrote:
> > [This is adding a new user visible interface so you should be CCing
> > linux-api mailing list. Also CC Hugh for KSM in general. Done now]
Right, thanks for
Hi.
On Wed, May 15, 2019 at 03:53:55AM +0300, Timofey Titovets wrote:
> LGTM for whole series
>
> Reviewed-by: Timofey Titovets
>
> вт, 14 мая 2019 г. в 16:17, Oleksandr Natalenko :
> >
> > Document respective sysfs knob.
> >
> > Signed-off-by: Oleksandr Natalenko
> > ---
> >
This patch enables NO_HZ_IDLE (idle dynamic ticks) and HIGH_RES_TIMERS
(hrtimers) in RV32 and RV64 defconfigs.
Both of the above options are enabled by default for architectures
such as x86, ARM, and ARM64.
The idle dynamic ticks helps use save power by stopping timer ticks
when the system is
When the output sample rate is [8kHz, 30kHz], the limitation
of the supported ratio range is [1/24, 8]. In the driver
we use (8kHz, 30kHz) instead of [8kHz, 30kHz].
So this patch is to fix this issue and the potential rounding
issue with divider.
Fixes: fff6e03c7b65 ("ASoC: fsl_asrc: add support
Support more sample rate in asrc
Shengjiu Wang (3):
ASoC: fsl_asrc: Fix the issue about unsupported rate
ASoC: fsl_asrc: replace the process_option table with function
ASoC: fsl_asrc: Unify the supported input and output rate
Changes in RESEND V6
- change the Content-Transfer-Encoding to
> +static int change_page_ro(pte_t *ptep, pgtable_t token, unsigned long addr,
> void *data)
There are a couple way too long lines like this in the patch.
Unify the supported input and output rate, add the
12kHz/24kHz/128kHz to the support list
Signed-off-by: Shengjiu Wang
Acked-by: Nicolin Chen
---
sound/soc/fsl/fsl_asrc.c | 32 +++-
1 file changed, 19 insertions(+), 13 deletions(-)
diff --git
Oops, forgot to tell it's for 4.9. Resending with proper subject.
Le 15/05/2019 à 08:39, Christophe Leroy a écrit :
[Backport of upstream commit b45ba4a51cde29b2939365ef0c07ad34c8321789]
On powerpc32, patch_instruction() is called by apply_feature_fixups()
which is called from early_init()
When we want to support more sample rate, for example 12kHz/24kHz
we need update the process_option table, if we want to support more
sample rate next time, the table need to be updated again. which
is not flexible.
We got a function fsl_asrc_sel_proc to replace the table, which can
give the
A test for the basic NAT functionality uses ip command which
needs veth device.There is a condition where the kernel support
for veth is not compiled into the kernel and the test script
breaks.This patch contains code for reasonable error display
and correct code exit.
Signed-off-by: Jeffrin
Pointer s is allocated with kmem_cache_zalloc(). And s is used in the
follwoing codes. However, when kmem_cache_zalloc fails, using s will
cause null pointer dereference and the kernel will go wrong. Thus we
check whether the kmem_cache_zalloc fails.
Signed-off-by: Gen Zhang
---
--- mm/slub.c
Le 15/05/2019 à 08:42, Christoph Hellwig a écrit :
+static int change_page_ro(pte_t *ptep, pgtable_t token, unsigned long addr,
void *data)
There are a couple way too long lines like this in the patch.
powerpc arch accepts 90 chars per line, see arch/powerpc/tools/checkpatch.pl
Hi Miquel,
> > Add a driver for Macronix MX25F0A multifunction device controller.
> >
> > Signed-off-by: Mason Yang
> > ---
> > drivers/mfd/Kconfig | 9 ++
> > drivers/mfd/Makefile | 1 +
> > drivers/mfd/mxic-mx25f0a.c | 84 +++
> >
On 15.05.19 08:17, Marek Vasut wrote:
> On 5/14/19 11:53 PM, Jeff Kletsky wrote:
>> From: Jeff Kletsky
>
> That #define in $subject is called a macro.
>
> Seems this patch adds a lot of almost duplicate code, can it be somehow
> de-duplicated ?
We could add another parameter naddr or addrlen
On 5/15/19 1:49 AM, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> The available registers for --int-regs and --user-regs may be different,
> e.g. XMM registers.
>
> Split parse_regs into two dedicated functions for --int-regs and
> --user-regs respectively.
>
> Modify the warning
Yabin Cui writes:
> diff --git a/kernel/events/ring_buffer.c b/kernel/events/ring_buffer.c
> index 674b35383491..0b9aefe13b04 100644
> --- a/kernel/events/ring_buffer.c
> +++ b/kernel/events/ring_buffer.c
> @@ -54,8 +54,10 @@ static void perf_output_put_handle(struct
> perf_output_handle
On 14.05.19 23:53, Jeff Kletsky wrote:
> From: Jeff Kletsky
>
> The GigaDevice GD5F1GQ4UFxxG SPI NAND utilizes three-byte addresses
> for its page-read ops.
>
> http://www.gigadevice.com/datasheet/gd5f1gq4xfxxg/
>
> Signed-off-by: Jeff Kletsky
Reviewed-by: Frieder Schrempf
> ---
>
On 14.05.19 23:53, Jeff Kletsky wrote:
> From: Jeff Kletsky
>
> The GigaDevice GD5F1GQ4UFxxG SPI NAND utilizes two-byte device IDs.
>
> http://www.gigadevice.com/datasheet/gd5f1gq4xfxxg/
>
> Signed-off-by: Jeff Kletsky
Reviewed-by: Frieder Schrempf
> ---
> drivers/mtd/nand/spi/core.c | 2
On Mon, May 13, 2019 at 2:04 PM Christoph Hellwig wrote:
>
> On Mon, May 13, 2019 at 01:50:19PM +0200, Dmitry Vyukov wrote:
> > > We did have some bugs in the past (~1-2 y/ago) but AFAIK they are all
> > > fixed now. These days I build most of my kernels with a bi-endian 64-bit
> > > toolchain,
On 14.05.19 23:53, Jeff Kletsky wrote:
> From: Jeff Kletsky
>
> The GigaDevice GD5F1GQ4UFxxG SPI NAND is in current production devices
> and, while it has the same logical layout as the E-series devices,
> it differs in the SPI interfacing in significant ways.
>
> This support is contingent on
On Wed 15-05-19 08:25:23, Oleksandr Natalenko wrote:
[...]
> > > Please make sure to describe a usecase that warrants adding a new
> > > interface we have to maintain for ever.
>
> I think of two major consumers of this interface:
>
> 1) hosts, that run containers, especially similar ones and
Since commit 7d5905dc14a8 ("x86 / CPU: Always show current CPU frequency
in /proc/cpuinfo") open and read of /proc/cpuinfo sends IPI to all CPUs.
Many applications read /proc/cpuinfo at the start for trivial reasons like
counting cores or detecting cpu features. While sensitive workloads like
DPDK
On Sun, May 12, 2019 at 3:25 AM Alex Elder wrote:
> diff --git a/include/soc/qcom/rmnet.h b/include/soc/qcom/rmnet.h
> new file mode 100644
> index ..80dcd6e68c3d
> --- /dev/null
> +++ b/include/soc/qcom/rmnet.h
> @@ -0,0 +1,38 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +
> +/*
On Sun, May 12, 2019 at 3:25 AM Alex Elder wrote:
>
> Add the binding definitions for the "qcom,ipa" device tree node.
>
> Signed-off-by: Alex Elder
> ---
> .../devicetree/bindings/net/qcom,ipa.txt | 164 ++
> 1 file changed, 164 insertions(+)
> create mode 100644
On 05/15/2019 05:21 AM, Roman Gushchin wrote:
> Vmalloc() is getting more and more used these days (kernel stacks,
> bpf and percpu allocator are new top users), and the total %
> of memory consumed by vmalloc() can be pretty significant
> and changes dynamically.
>
> /proc/meminfo is the best
Hi Janusz,
On Wed, May 15, 2019 at 12:48:21AM +0200, Janusz Krzysztofik wrote:
> -static int check_crop(struct v4l2_subdev *sd, struct v4l2_subdev_crop *crop)
> +static inline int check_pad(struct v4l2_subdev *sd, __u32 pad)
> {
> - if (crop->which != V4L2_SUBDEV_FORMAT_TRY &&
> -
On Wed, 15 May 2019, masonccy...@mxic.com.tw wrote:
> Hi Jones,
>
>
> > > +
> > > +struct rpc_spi {
> > > + struct rpc_mfd *mfd;
> >
> > The term MFD isn't a real thing. What you're obtaining below is
> > driver data and is normally articulated as 'ddata' in drivers.
>
> yes, it's just
On Sun, May 12, 2019 at 3:25 AM Alex Elder wrote:
> +/** gsi_gpi_channel_scratch - GPI protocol scratch register
> + *
> + * @max_outstanding_tre:
> + * Defines the maximum number of TREs allowed in a single transaction
> + * on a channel (in Bytes). This determines the amount of
Hi Steve,
On Tue, May 14, 2019 at 9:35 PM Steven Rostedt wrote:
> On Tue, 14 May 2019 21:13:06 +0200
> Geert Uytterhoeven wrote:
> > > > Do we care about the value? "(-E%u)"?
> > >
> > > That too could be confusing. What would (-E22) be considered by a user
> > > doing an sprintf() on some
> -Original Message-
> From: Kirill A. Shutemov [mailto:kir...@shutemov.name]
> Sent: Thursday, May 09, 2019 7:14 AM
> To: Justin Piszcz
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: 5.1 kernel: khugepaged stuck at 100%
>
> On Thu, May 09, 2019 at 05:54:56AM -0400, Justin Piszcz
Hi Stephen,
On Tue, May 14, 2019 at 7:09 PM Stephen Boyd wrote:
> Now that we've gotten rid of clk_readl() we can remove io.h from the
> clk-provider header and push out the io.h include to any code that isn't
> already including the io.h header but using things like readl/writel,
> etc.
>
>
On Tue, May 14, 2019 at 11:19 PM Stephen Boyd wrote:
> Quoting Chris Paterson (2019-05-14 08:33:41)
> > Misspelling 'prohibited' is quite common in the real world, although
> > surprisingly not so much in the Linux Kernel. In addition to fixing the
> > typo we may as well add it to the spelling
Can different run time characteristics become relevant here?
>>>
>>> Internally, they should be identical.
>>
>> I got other imaginations in this area.
>
> You imagination doesn't matter in this case.
They might result in collateral software evolution.
> What matters is what the code does.
> +static void gsi_trans_tre_fill(struct gsi_tre *dest_tre, dma_addr_t addr,
> + u32 len, bool last_tre, bool bei,
> + enum ipa_cmd_opcode opcode)
> +{
> + struct gsi_tre tre;
> +
> + tre.addr = cpu_to_le64(addr);
> +
On Tue 2019-05-14 14:37:51, Steven Rostedt wrote:
>
> [ Purple is a nice shade on the bike shed. ;-) ]
>
> On Tue, 14 May 2019 11:02:17 +0200
> Geert Uytterhoeven wrote:
>
> > On Tue, May 14, 2019 at 10:29 AM David Laight
> > wrote:
> > > > And I like Steven's "(fault)" idea.
> > > > How
Add the PCIe compatible string for LS1028A
Signed-off-by: Xiaowei Bao
---
.../devicetree/bindings/pci/layerscape-pci.txt |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/layerscape-pci.txt
Hi Miquel,
> > +Macronix MX25F0A MultiFunction Device Tree Bindings
> > +
> > +
> > +MX25F0A is a MultiFunction Device with SPI and raw NAND, which
> > +supports either spi host controller or raw nand controller.
>
> Acronyms in plain
Add support for the LS1028a PCIe controller.
Signed-off-by: Xiaowei Bao
---
drivers/pci/controller/dwc/pci-layerscape.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/drivers/pci/controller/dwc/pci-layerscape.c
b/drivers/pci/controller/dwc/pci-layerscape.c
LS1028a implements 2 PCIe 3.0 controllers.
Signed-off-by: Xiaowei Bao
---
arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 52
1 files changed, 52 insertions(+), 0 deletions(-)
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
On Tue, Apr 30, 2019 at 11:45:26AM +0800, Zhao Yakui wrote:
> When the ACRN hypervisor is detected, the hypercall is needed so that the
> ACRN guest can query/config some settings. For example: it can be used
> to query the resources in hypervisor and manage the CPU/memory/device/
> interrupt for
Hi.
On Wed, May 15, 2019 at 08:53:11AM +0200, Michal Hocko wrote:
> On Wed 15-05-19 08:25:23, Oleksandr Natalenko wrote:
> [...]
> > > > Please make sure to describe a usecase that warrants adding a new
> > > > interface we have to maintain for ever.
> >
> > I think of two major consumers of
In the recent build test of linux-next, Stephen saw a build error
caused by a broken .tmp_versions/*.mod file:
https://lkml.org/lkml/2019/5/13/991
drivers/net/phy/asix.ko and drivers/net/usb/asix.ko have the same
basename, and there is a race in generating .tmp_versions/asix.mod
Kbuild has
On 05/15/2019 05:21 AM, Roman Gushchin wrote:
> __vunmap() calls find_vm_area() twice without an obvious reason:
> first directly to get the area pointer, second indirectly by calling
> vm_remove_mappings()->remove_vm_area(), which is again searching
> for the area.
>
> To remove this
On Tue, May 14, 2019 at 11:36:18AM -0700, Brendan Higgins wrote:
> On Tue, May 14, 2019 at 02:05:05PM +0200, Daniel Vetter wrote:
> > On Tue, May 14, 2019 at 8:04 AM Brendan Higgins
> > wrote:
> > >
> > > On Mon, May 13, 2019 at 04:44:51PM +0200, Daniel Vetter wrote:
> > > > On Sat, May 11, 2019
From: "Gautham R. Shenoy"
The calls to arch_add_memory()/arch_remove_memory() are always made
with the read-side cpu_hotplug_lock acquired via
memory_hotplug_begin(). On pSeries,
arch_add_memory()/arch_remove_memory() eventually call resize_hpt()
which in turn calls stop_machine() which
Timekeeping watchdog verifies doubtful clocksources using more reliable
candidates. For x86 it likely verifies 'tsc' using 'hpet'. But 'hpet'
is far from perfect too. It's better to have second opinion if possible.
We're seeing sudden jumps of hpet counter to 0x:
timekeeping watchdog on
On Wed, May 15, 2019 at 4:40 PM Masahiro Yamada
wrote:
>
> In the recent build test of linux-next, Stephen saw a build error
> caused by a broken .tmp_versions/*.mod file:
>
> https://lkml.org/lkml/2019/5/13/991
>
> drivers/net/phy/asix.ko and drivers/net/usb/asix.ko have the same
> basename,
Build in CONFIG_NVMEM_IMX_OCOTP_SCU.
Cc: Catalin Marinas
Cc: Will Deacon
Cc: Shawn Guo
Cc: Andy Gross
Cc: Maxime Ripard
Cc: Olof Johansson
Cc: Jagan Teki
Cc: Bjorn Andersson
Cc: Leonard Crestez
Cc: Marc Gonzalez
Cc: Enric Balletbo i Serra
Cc: linux-arm-ker...@lists.infradead.org
NXP i.MX8QXP is an ARMv8 SoC with a Cortex-M4 core inside as
system controller(SCU), the ocotp controller is being controlled
by the SCU, so Linux need use RPC to SCU for ocotp handling. This
patch adds binding doc for i.MX8 SCU OCOTP driver.
Cc: Mark Rutland
Cc: Shawn Guo
Cc: Ulf Hansson
Cc:
Add i.MX8QXP ocotp node
Cc: Rob Herring
Cc: Mark Rutland
Cc: Shawn Guo
Cc: Sascha Hauer
Cc: Pengutronix Kernel Team
Cc: Fabio Estevam
Cc: NXP Linux Team
Cc: Anson Huang
Cc: Daniel Baluta
Cc: devicet...@vger.kernel.org
Cc: linux-arm-ker...@lists.infradead.org
Reviewed-by: Dong Aisheng
On Wed 2019-05-15 09:23:05, Geert Uytterhoeven wrote:
> Hi Steve,
>
> On Tue, May 14, 2019 at 9:35 PM Steven Rostedt wrote:
> > On Tue, 14 May 2019 21:13:06 +0200
> > Geert Uytterhoeven wrote:
> > > > > Do we care about the value? "(-E%u)"?
> > > >
> > > > That too could be confusing. What
This patch adds i.MX8 nvmem ocotp driver to access fuse via
RPC to i.MX8 system controller.
Cc: Srinivas Kandagatla
Cc: Shawn Guo
Cc: Sascha Hauer
Cc: Pengutronix Kernel Team
Cc: Fabio Estevam
Cc: NXP Linux Team
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Peng Fan
---
V3:
Use
Hello RT Folks!
I'm pleased to announce the 4.4.179-rt181 stable release. This release
is just an update to the new stable v4.4.179 version and no RT specific
changes have been made.
You'll notice there is also a v4.4.178-rt180 release available. The
stable v4.4.178 update includes bdf3c006b9a2
On Wed, May 15, 2019 at 4:14 AM Stephen Boyd wrote:
>
> Quoting Nicolas Boichat (2019-05-13 18:37:58)
> > On Tue, May 14, 2019 at 6:29 AM Stephen Boyd wrote:
> > >
> > > Quoting Nicolas Boichat (2019-04-28 20:55:15)
> > > > During suspend/resume, mtk_eint_mask may be called while
> > > >
On Wed, May 15, 2019 at 9:36 AM Xiaowei Bao wrote:
> Signed-off-by: Xiaowei Bao
> ---
> arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 52
>
> 1 files changed, 52 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
>
On Wed, May 15, 2019 at 9:39 AM Masahiro Yamada
wrote:
>
> In the recent build test of linux-next, Stephen saw a build error
> caused by a broken .tmp_versions/*.mod file:
>
> https://lkml.org/lkml/2019/5/13/991
>
> drivers/net/phy/asix.ko and drivers/net/usb/asix.ko have the same
> basename,
On Wed, May 15, 2019 at 10:08:12AM +0200, Arnd Bergmann wrote:
> On Wed, May 15, 2019 at 9:39 AM Masahiro Yamada
> wrote:
> >
> > In the recent build test of linux-next, Stephen saw a build error
> > caused by a broken .tmp_versions/*.mod file:
> >
> > https://lkml.org/lkml/2019/5/13/991
> >
>
Since commit 88aa7cc688d4 ("mm: introduce arg_lock to protect arg_start|
end and env_start|end in mm_struct") related mm fields are protected with
separate spinlock and mmap_sem held for read is not enough for protection.
Fixes: 88aa7cc688d4 ("mm: introduce arg_lock to protect arg_start|end and
This function is used by ptrace and proc files like /proc/pid/cmdline and
/proc/pid/environ. Return 0 (bytes read) if current task is killed.
Mmap_sem could be locked for a long time or forever if something wrong.
Signed-off-by: Konstantin Khlebnikov
---
mm/memory.c |4 +++-
mm/nommu.c |
On Sun, May 12, 2019 at 3:25 AM Alex Elder wrote:
> +/* Initialize header space in IPA local memory */
> +int ipa_cmd_hdr_init_local(struct ipa *ipa, u32 offset, u32 size)
> +{
> + struct ipa_imm_cmd_hw_hdr_init_local *payload;
> + struct device *dev = >pdev->dev;
> +
On Sun, May 12, 2019 at 3:25 AM Alex Elder wrote:
>
> This patch includes the code that implements a Linux network device,
> using one TX and one RX IPA endpoint. It is used to implement the
> network device representing the modem and its connection to wireless
> networks. There are only a few
Changes in v4:
**
- Added Viresh's Acked-by to all 3 patches
- Improved commit message of patch 3/3 to explain how it has no
functional impact on existing users (Eduardo)
Changes in v3:
**
- Changed warning message for unordered tables to something more
explicit
On Sun, May 12, 2019 at 3:25 AM Alex Elder wrote:
> diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
> index 2d9c39033c1a..4f4d803e563d 100644
> --- a/arch/arm64/configs/defconfig
> +++ b/arch/arm64/configs/defconfig
> @@ -268,6 +268,7 @@ CONFIG_SMSC911X=y
>
On Wed, May 15, 2019 at 11:15:37AM +0300, Konstantin Khlebnikov wrote:
> Since commit 88aa7cc688d4 ("mm: introduce arg_lock to protect arg_start|
> end and env_start|end in mm_struct") related mm fields are protected with
> separate spinlock and mmap_sem held for read is not enough for protection.
In the current state, the perf_domain struct is fully defined only when
CONFIG_ENERGY_MODEL=y. Since we need to write code that compiles both
with or without that option in the thermal framework, make sure to
actually define the struct regardless of the config option. That allows
to avoid using
The newly introduced Energy Model framework manages power cost tables in
a generic way. Moreover, it supports several types of models since the
tables can come from DT or firmware (through SCMI) for example. On the
other hand, the cpu_cooling subsystem manages its own power cost tables
using only
The recently introduced Energy Model (EM) framework manages power cost
tables for the CPUs of the system. Its only user right now is the
scheduler, in the context of Energy Aware Scheduling (EAS).
However, the EM framework also offers a generic infrastructure that
could replace subsystem-specific
On Wed, May 15, 2019 at 06:40:47AM +, Christophe Leroy wrote:
> [Backport of upstream commit b45ba4a51cde29b2939365ef0c07ad34c8321789]
>
> On powerpc32, patch_instruction() is called by apply_feature_fixups()
> which is called from early_init()
>
> There is the following note in front of
Add i.MX SCU SoC info driver to support i.MX8QXP SoC, introduce
driver dependency into Kconfig as CONFIG_IMX_SCU must be
selected to support i.MX SCU SoC driver, also need to use
platform driver model to make sure IMX_SCU driver is probed
before i.MX SCU SoC driver.
With this patch, SoC info can
On Tue, May 14, 2019 at 08:08:03AM -0700, Andy Lutomirski wrote:
> > Putting everything together, I'd suggest to:
> > - Change EADD ioctl to take source page's VMA permission as ("upper
> > bound" of) EPCM permission. This make sure no one can circumvent LSM to
> > generate executable code on
This patch selects CONFIG_IMX_SCU_SOC by default to support
i.MX system controller unit SoC info driver.
Signed-off-by: Anson Huang
---
No changes.
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
On Wed 15-05-19 09:37:23, Oleksandr Natalenko wrote:
[...]
> > This is way too generic. Please provide something more specific. Ideally
> > with numbers. Why those usecases cannot use an existing interfaces.
> > Remember you are trying to add a new user interface which we will have
> > to maintain
On Wed, May 15, 2019 at 2:57 AM Muchun Song wrote:
>
> There is a race condition between removing glue directory and adding a new
> device under the glue directory. It can be reproduced in following test:
>
> path 1: Add the child device under glue dir
> device_add()
> get_device_parent()
>
On 15.05.2019 11:22, Oscar Salvador wrote:
On Wed, May 15, 2019 at 11:15:37AM +0300, Konstantin Khlebnikov wrote:
Since commit 88aa7cc688d4 ("mm: introduce arg_lock to protect arg_start|
end and env_start|end in mm_struct") related mm fields are protected with
separate spinlock and mmap_sem
Hi, Konstantin,
On 15.05.2019 11:15, Konstantin Khlebnikov wrote:
> Since commit 88aa7cc688d4 ("mm: introduce arg_lock to protect arg_start|
> end and env_start|end in mm_struct") related mm fields are protected with
> separate spinlock and mmap_sem held for read is not enough for protection.
>
Hi,
making this holder of mmap_sem killable was for the reasons of /proc/...
diagnostics was an idea I was pondeering too. However, I think the
approach of pretending we read 0 bytes is not correct. The API would IMO
need to be extended to allow pass a result such as EINTR to the end
caller.
Why
Do not stuck forever if something wrong.
This function also used for /proc/pid/smaps.
Signed-off-by: Konstantin Khlebnikov
---
fs/proc/task_mmu.c |6 +-
fs/proc/task_nommu.c |6 +-
2 files changed, 10 insertions(+), 2 deletions(-)
diff --git a/fs/proc/task_mmu.c
Replace the only unkillable mmap_sem lock in clear_refs_write.
Signed-off-by: Konstantin Khlebnikov
---
fs/proc/task_mmu.c |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
index 78bed6adc62d..7f84d1477b5b 100644
---
Ditto.
Signed-off-by: Konstantin Khlebnikov
---
fs/proc/task_mmu.c |8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
index 2bf210229daf..781879a91e3b 100644
--- a/fs/proc/task_mmu.c
+++ b/fs/proc/task_mmu.c
@@ -832,7 +832,10
ltp-mm-tests failed on Linux mainline kernel 5.1.0,
* overcommit_memory01 overcommit_memory
* overcommit_memory03 overcommit_memory -R 30
* overcommit_memory04 overcommit_memory -R 80
* overcommit_memory05 overcommit_memory -R 100
* overcommit_memory06 overcommit_memory -R 200
It seems ->d_revalidate() could return any error (except ECHILD) to
abort validation and pass error as result of lookup sequence.
Signed-off-by: Konstantin Khlebnikov
---
fs/proc/base.c | 27 +--
1 file changed, 21 insertions(+), 6 deletions(-)
diff --git
Ditto.
Signed-off-by: Konstantin Khlebnikov
---
fs/proc/task_mmu.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/fs/proc/task_mmu.c b/fs/proc/task_mmu.c
index 781879a91e3b..78bed6adc62d 100644
--- a/fs/proc/task_mmu.c
+++ b/fs/proc/task_mmu.c
@@ -1547,7 +1547,9 @@
On 15.05.2019 0:46, Arnaldo Carvalho de Melo wrote:
> Em Tue, May 14, 2019 at 05:20:41PM -0300, Arnaldo Carvalho de Melo escreveu:
>> Em Mon, Mar 18, 2019 at 08:44:42PM +0300, Alexey Budankov escreveu:
>>>
>>> Implemented -z,--compression_level[=] option that enables compression
>>> of mmaped
On Mon, 13 May 2019 11:11:16 +0900
Masahiro Yamada wrote:
> As of Linux 5.1, alpha and s390 are the last architectures that
> have defconfig in arch/*/ instead of arch/*/configs/.
>
> $ find arch -name defconfig | sort
> arch/alpha/defconfig
> arch/arm64/configs/defconfig
>
On 15/05/2019 10:23, Quentin Perret wrote:
> The recently introduced Energy Model (EM) framework manages power cost
> tables for the CPUs of the system. Its only user right now is the
> scheduler, in the context of Energy Aware Scheduling (EAS).
>
> However, the EM framework also offers a generic
From: Ashish Kumar
This patch is to add esdhc node and enable SD UHS-I,
eMMC HS200 for ls1028ardb/ls1028aqds board.
Signed-off-by: Ashish Kumar
Signed-off-by: Yangbo Lu
Signed-off-by: Yinbo Zhu
---
Change in v3:
replace "esdhc@" with "mmc@"
On 15.05.2019 11:38, Michal Koutný wrote:
Hi,
making this holder of mmap_sem killable was for the reasons of /proc/...
diagnostics was an idea I was pondeering too. However, I think the
approach of pretending we read 0 bytes is not correct. The API would IMO
need to be extended to allow pass a
On Tue, May 14, 2019 at 08:13:36AM -0700, Andy Lutomirski wrote:
> On Tue, May 14, 2019 at 3:43 AM Jarkko Sakkinen
> wrote:
> >
> > On Mon, May 13, 2019 at 01:29:26PM +0300, Jarkko Sakkinen wrote:
> > > I did study through SDK's file format and realized that it does not
> > > does make sense
Hi Miquel,
> > +// SPDX-License-Identifier: GPL-2.0
> > +//
> > +// Copyright (C) 2019 Macronix International Co., Ltd.
> > +//
> > +// Authors:
> > +// Mason Yang
> > +// zhengxunli
>
> This is not a valid name.
>
> Also if he appears here I suppose he should be credited in the
>
Hi Ingo,
On Wed, 15 May 2019 07:55:34 +0200
Ingo Molnar wrote:
>
> * Masami Hiramatsu wrote:
>
> > Hi,
> >
> > Here is the v9 series of probe-event to support user-space access.
> > Previous version is here.
> >
> >
On Wed, May 15, 2019 at 10:33:21AM +0200, Michal Hocko wrote:
> > For my current setup with 2 Firefox instances I get 100 to 200 MiB saved
> > for the second instance depending on the amount of tabs.
>
> What does prevent Firefox (an opensource project) to be updated to use
> the explicit
On Mon, May 13, 2019 at 01:58:44PM -0400, Len Brown wrote:
>
> This patch series does 4 things.
>
> 1. Parse the new CPUID.1F leaf to discover multi-die/package topology
>
> 2. Export multi-die topology inside the kernel
>
> 3. Update 4 places (coretemp, pkgtemp, rapl, perf) that that need to
On Wed, May 15, 2019 at 5:14 PM Greg KH wrote:
>
> On Wed, May 15, 2019 at 10:08:12AM +0200, Arnd Bergmann wrote:
> > On Wed, May 15, 2019 at 9:39 AM Masahiro Yamada
> > wrote:
> > >
> > > In the recent build test of linux-next, Stephen saw a build error
> > > caused by a broken
On 14/05/2019 20:09, Stephen Boyd wrote:
Now that we've gotten rid of clk_readl() we can remove io.h from the
clk-provider header and push out the io.h include to any code that isn't
already including the io.h header but using things like readl/writel,
etc.
For drivers/clk/ti portions:
1 - 100 of 1557 matches
Mail list logo
