On Fri, Jul 6, 2018 at 5:01 AM Rafael J. Wysocki wrote:
>
> From: Rafael J. Wysocki
>
> The devices_kset_move_last() call in really_probe() is a mistake
> as it may cause parents to follow children in the devices_kset list
> which then causes system shutdown to fail. Namely, if a device has
>
On Mon, Jul 2, 2018 at 1:59 PM Abel Vesa wrote:
> This is the sixth version for the patch series sent by Lucas.
>
> https://www.spinics.net/lists/devicetree/msg212752.html
>
> Fifth version can be found here:
>
> https://lkml.org/lkml/2018/6/22/501
>
> Changes since v5:
> * implemented Rob's
On 09/07/18 13:41, Mark Brown wrote:
AFAIU, The issue with that mechanism or EPROBEDEFER is that it works only
for first time.. for the second time(restart usecase) there are no hooks
like bind/unbind.
This is not the case, the card will be unbound at the ASoC level when
any of the
On Tue, Jul 03, 2018 at 09:55:43AM +0100, Jon Hunter wrote:
> On Tegra30 Cardhu the PCA9546 I2C mux is not ACK'ing I2C commands on
> resume from suspend (which is caused by the reset signal for the I2C
> mux not being configured correctl). However, this NACK is causing the
> Tegra30 to hang on
From: Kan Liang
Perf record will error out if both --delay and LBR are applied.
For example:
perf record -D 1000 -a -e cycles -j any -- sleep 2
Error:
dummy:HG: PMU Hardware doesn't support sampling/overflow-interrupts.
Try 'perf stat'
A dummy event is added implicitly for initial
what the problem was on Friday, fixed the problem and pushed it
> out to my git tree on Saturday.
>
Because syzbot found a C reproducer on 2018/07/09 02:29 UTC, and your fix was
not in time for a kernel version syzbot was testing, and you were not listed
as a recipient of this bug, and I di
The new rseq call arrived in 4.18-rc1, so provide it in the asm-generic
unistd.h for architectures such as arm64.
Cc: Arnd Bergmann
Signed-off-by: Will Deacon
---
include/uapi/asm-generic/unistd.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Hook up arm64 support to the rseq selftests.
Signed-off-by: Will Deacon
---
tools/testing/selftests/rseq/param_test.c | 20 +
tools/testing/selftests/rseq/rseq-arm64.h | 594 ++
tools/testing/selftests/rseq/rseq.h | 2 +
3 files changed, 616 insertions(+)
Implement calls to rseq_signal_deliver, rseq_handle_notify_resume
and rseq_syscall so that we can select HAVE_RSEQ on arm64.
Acked-by: Mark Rutland
Signed-off-by: Will Deacon
---
arch/arm64/Kconfig| 1 +
arch/arm64/include/asm/unistd.h | 2 +-
Hello,
This is version two of the patches previously posted here:
http://lkml.kernel.org/r/1529949285-11013-1-git-send-email-will.dea...@arm.com
Changes since v1 include:
* Move abort handler in-line to avoid possibility of it being
out-of-range for conditional branch instructions
I've
On Mon, Jul 09, 2018 at 01:47:14PM +0100, David Woodhouse wrote:
> On Mon, 2018-07-09 at 05:34 -0700, Paul E. McKenney wrote:
> > The reason that David's latencies went from 100ms to one second is
> > because I made this code less aggressive about invoking resched_cpu().
>
> Ten seconds. We saw
On 09-07-18, 16:16, Rohit Kumar wrote:
> > > +static int sdm845_bind(struct device *dev)
> > > +{
> > > + struct snd_soc_card *card;
> > > + struct sdm845_snd_data *data;
> > > + int ret;
> > > +
> > > + card = kzalloc(sizeof(*card), GFP_KERNEL);
> > > + if (!card)
> > > + return -ENOMEM;
Gcc cannot always see that BUG_ON(1) is guaranteed to not
return, so we get a warning message in some configurations:
drivers/gpio/gpio-aspeed.c: In function 'bank_reg':
drivers/gpio/gpio-aspeed.c:244:1: error: control reaches end of non-void
function [-Werror=return-type]
Using a plain BUG()
Quoting Jian Hu (2018-07-09 04:12:47)
> Add a Clock driver for the Everyting-Else part
Everything instead of Everyting?
> of the Amlogic Meson-G12A SoC.
>
> Signed-off-by: Jian Hu
If users access "/proc/pid/stat", the utime and stime ratio in the
current SAMPLE period are excepted, but currently cputime_adjust()
always calculates with the ratio of the WHOLE lifetime of the process.
This results in inaccurate utime and stime in "/proc/pid/stat". For
example, a process runs
Most Ethernet drivers don't enforce the MTU value as upper limit
for ingress frames. We too support receiving frames larger than
MTU, so allow that.
Remove our ndo_change_mtu implementation, letting the default
stack implementation handle things. Also, set the max frame length
allowed by hardware
One bug fix, one small functional change and a couple of
cleanup patches.
Ioana Radulescu (5):
staging: fsl-dpaa2/eth: Fix DMA mapping direction
staging: fsl-dpaa2/eth: Remove obsolete reference
staging: fsl-dpaa2/eth: Remove pointless instruction
staging: fsl-dpaa2/eth: MTU cleanup
Don't set the lower MTU limit explicitly, since we use
the default value anyway.
Signed-off-by: Ioana Radulescu
---
drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c
Commit 2b7c86eb7bf3 ("staging: fsl-dpaa2/eth: Don't enable FAS on Tx")
removed the status field from the TX confirm frame annotation,
but a reference to it remained in the description of free_tx_fd().
Remove it.
Signed-off-by: Ioana Radulescu
---
drivers/staging/fsl-dpaa2/ethernet/dpaa2-eth.c |
Clark showed me this:
| BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:974
| in_atomic(): 1, irqs_disabled(): 0, pid: 1, name: systemd
| 5 locks held by systemd/1:
| #0: (sb_writers#7){.+.+}, at: [<(ptrval)>] mnt_want_write+0x1f/0x50
| #1:
On 07/06/2018 08:47 PM, Xiubo Li wrote:
> On 2018/7/7 2:58, Mike Christie wrote:
>> On 07/05/2018 09:57 PM, xiu...@redhat.com wrote:
>>> void uio_event_notify(struct uio_info *info)
>>> {
>>> -struct uio_device *idev = info->uio_dev;
>>> +struct uio_device *idev;
>>> +
>>> +if
> On Jul 9, 2018, at 7:19 AM, Jiri Olsa wrote:
>
> We don't release tk->tp.call.print_fmt when destroying
> local uprobe. Also there's missing print_fmt kfree in
> create_local_trace_kprobe error path.
>
> Fixes: e12f03d7031a ("perf/core: Implement the 'perf_kprobe' PMU")
> Signed-off-by:
Hi George,
On 7/9/2018 4:10 AM, George Cherian wrote:
> Per Section 8.4.7.1.3 of ACPI 6.2, The platform provides performance
> feedback via set of performance counters. To determine the actual
> performance level delivered over time, OSPM may read a set of
> performance counters from the
On Mon, Jul 09, 2018 at 09:34:32AM -0700, Paul E. McKenney wrote:
> On Mon, Jul 09, 2018 at 05:26:32PM +0200, Peter Zijlstra wrote:
> > On Mon, Jul 09, 2018 at 07:29:32AM -0700, Paul E. McKenney wrote:
> > > OK, so here are our options:
> > >
> > > 1.Add the RCU conditional to
Quoting Gregory CLEMENT (2018-07-09 08:42:31)
> Hi Stephen,
>
> On ven., juil. 06 2018, Stephen Boyd wrote:
>
> > Quoting Gregory CLEMENT (2018-06-29 07:44:02)
> >> Hi,
> >>
> >> On mar., juin 19 2018, Gregory CLEMENT
> >> wrote:
> >>
> >> > Switching the CPU from the L2 or L3
From: Haiyang Zhang
If out ring is full temporarily and receive completion cannot go out,
we may still need to reschedule napi if other conditions are met.
Otherwise the napi poll might be stopped forever, and cause network
disconnect.
Fixes: 7426b1a51803 ("netvsc: optimize receive
On Mon, 9 Jul 2018 16:19:06 +0200
Jiri Olsa wrote:
> We don't release tk->tp.call.print_fmt when destroying
> local uprobe. Also there's missing print_fmt kfree in
> create_local_trace_kprobe error path.
>
> Fixes: e12f03d7031a ("perf/core: Implement the 'perf_kprobe' PMU")
> Signed-off-by:
A CFS (SCHED_OTHER, SCHED_BATCH or SCHED_IDLE policy) task's
se->runnable_weight must always be in sync with its se->load.weight.
se->runnable_weight is set to se->load.weight when the task is
forked (init_entity_runnable_average()) or reniced (reweight_entity()).
There are two cases in
From: Lokesh Vutla
MCAN is clocked by H14 divider of DPLL_GMAC. Unlike other
DPLL dividers this DPLL_GMAC H14 divider is controlled by
control module. Adding support for these clocks.
Signed-off-by: Lokesh Vutla
Signed-off-by: Faiz Abbas
---
arch/arm/boot/dts/dra76x.dtsi | 33
Add clkctrl data for the m_can clocks and register it within the
clkctrl driver
Acked-by: Rob Herring
Acked-by: Stephen Boyd
CC: Tero Kristo
Signed-off-by: Faiz Abbas
---
drivers/clk/ti/clk-7xx.c | 1 +
include/dt-bindings/clock/dra7.h | 1 +
2 files changed, 2 insertions(+)
diff
Add support for the software reset of a target interconnect
module using its sysconfig and sysstatus registers.
Signed-off-by: Faiz Abbas
---
drivers/bus/ti-sysc.c | 44 +++
1 file changed, 44 insertions(+)
diff --git a/drivers/bus/ti-sysc.c
Hi Huacai,
On Mon, Jul 09, 2018 at 10:26:38AM +0800, Huacai Chen wrote:
> After commit 7f56b58a92aaf2c ("locking/mcs: Use smp_cond_load_acquire()
> in MCS spin loop") Loongson-3 fails to boot. This is because Loongson-3
> has SFB (Store Fill Buffer) and the weak-ordering may cause READ_ONCE()
>
On Fri, 6 Jul 2018 at 17:22, Kim Phillips wrote:
>
> On Thu, 5 Jul 2018 16:13:42 -0600
> Mathieu Poirier wrote:
>
> Hi Mathieu,
>
> > This patch adds the mechanic needed for user space to send PMU specific
>
> I think you meant 'mechanism' here: mechanics fix
The following patches add dts and sysconfig support
for MCAN on TI's dra76 SOCs
Changes in v5:
Return from sysc_reset() with error if syss_mask is not
present. That is the only supported way of reset
Changes in v4:
1. Rebased to latest kernel
2. Using ddata->cfg.syss_mask instead of
On Fri, Jul 06, 2018 at 02:10:55PM -0700, Paul E. McKenney wrote:
> On Fri, Jul 06, 2018 at 04:37:21PM -0400, Alan Stern wrote:
> > On Thu, 5 Jul 2018, Andrea Parri wrote:
> >
> > > > At any rate, it looks like instead of strengthening the relation, I
> > > > should write a patch that removes it
> +static inline bool thp_swap_supported(void)
> +{
> + return IS_ENABLED(CONFIG_THP_SWAP);
> +}
This seems like rather useless abstraction. Why do we need it?
...
> -static inline int swap_duplicate(swp_entry_t swp)
> +static inline int swap_duplicate(swp_entry_t *swp, bool cluster)
> {
>
On Mon, Jul 09, 2018 at 12:06:22PM -0400, Mathieu Desnoyers wrote:
> - On Jul 9, 2018, at 10:19 AM, Will Deacon will.dea...@arm.com wrote:
>
> > Hello,
> >
> > This is version two of the patches previously posted here:
> >
> >
On Mon, Jul 09, 2018 at 06:05:16PM +0200, Krzysztof Kozlowski wrote:
> Remove the usage of skeleton.dtsi because it was deprecated since commit
> 9c0da3cc61f1 ("ARM: dts: explicitly mark skeleton.dtsi as deprecated").
> It also allows later to fix DTC warnings for missing unit name in
> /memory
Forgot to add this patch is on top of
Following patches. Which are under review
https://patchwork.kernel.org/patch/10510029/
https://patchwork.kernel.org/patch/10510031/
https://patchwork.kernel.org/patch/10510037/
https://patchwork.kernel.org/patch/10510045/
On 03-07-18, 14:32, Paul Cercueil wrote:
> The register area of the JZ4780 DMA core can be split into different
> sections for different purposes:
>
> * one set of registers is used to perform actions at the DMA core level,
> that will generally affect all channels;
>
> * one set of registers
Hello,
syzbot found the following crash on:
HEAD commit:1e4b044d2251 Linux 4.18-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14dc81b240
kernel config: https://syzkaller.appspot.com/x/.config?x=25856fac4e580aa7
dashboard link:
On Fri, Jun 08, 2018 at 02:22:34PM -0500, shenwei.w...@nxp.com wrote:
> The current driver assumes that the ftm_sys clock works as
> one of the clock sources for the IP block as well as the IP
> interface clock. This assumption does not apply any more on
> the latest i.MX8x SoC family. On i.MX8x
> +#ifdef CONFIG_THP_SWAP
> +static inline int cluster_swapcount(struct swap_cluster_info *ci)
> +{
> + if (!ci || !cluster_is_huge(ci))
> + return 0;
> +
> + return cluster_count(ci) - SWAPFILE_CLUSTER;
> +}
> +#else
> +#define cluster_swapcount(ci)0
>
On 03-07-18, 14:32, Paul Cercueil wrote:
> The JZ4725B has one DMA core starring six DMA channels.
> As for the JZ4770, each DMA channel's clock can be enabled with
> a register write, the difference here being that once started, it
> is not possible to turn it off.
ok so disable for this,
On Mon, Jul 09, 2018 at 06:08:06PM +0200, Jan Kara wrote:
> On Mon 09-07-18 18:49:37, Nicholas Piggin wrote:
> > The problem with blocking in clear_page_dirty_for_io is that the fs is
> > holding the page lock (or locks) and possibly others too. If you
> > expect to have a bunch of long term
- On Jul 9, 2018, at 12:53 PM, Will Deacon will.dea...@arm.com wrote:
> On Mon, Jul 09, 2018 at 12:06:22PM -0400, Mathieu Desnoyers wrote:
>> - On Jul 9, 2018, at 10:19 AM, Will Deacon will.dea...@arm.com wrote:
>>
>> > Hello,
>> >
>> > This is version two of the patches previously
I'm seeing a pattern here.
old code:
foo()
{
do_swap_something()
}
new code:
foo(bool cluster)
{
if (cluster)
do_swap_cluster_something();
else
do_swap_something();
}
That make me fear that we have:
1. Created a new, wholly untested code
- On Jul 8, 2018, at 5:03 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> In preparation to use __u64 for the rseq_cs pointer field, 32-bit
> architectures need to read this 64-bit value located in user-space
> addresses.
>
> __get_user is used to read this value, given that
Hi Lorenzo,
On 7/9/2018 10:22 AM, Lorenzo Pieralisi wrote:
On Mon, Jun 11, 2018 at 05:21:02PM -0700, Ray Jui wrote:
This patch series improves the Broadcom PAXC support by 1) adding more
quirks for specific versions of PAXC controllers; 2) adding logic to
reject internally unconfigured
On Fri, Jun 29, 2018 at 7:53 PM, Wu Hao wrote:
> Hi All,
>
> Here is v7 patch-series adding drivers for FPGA DFL devices.
Hi Greg,
Could you please take this v7 patchset for 4.19?
Alan
>
> This patch series provides a common framework to support FPGA Device
> Feature List (DFL) and also
The SDMMC clocks have a Low Jitter (LJ) clock path which bypasses a
divider to achieve better jitter performance with high speed signaling
modes. The clock path with the divider is needed by some of the slower
signaling modes. This series automatically multiplexes the LJ and
non-LJ clock paths
From: Peter De-Schrijver
These clocks have low jitter paths to certain parents. To model these
correctly, use the sdmmc mux divider clock type.
Signed-off-by: Peter De-Schrijver
Signed-off-by: Aapo Vienamo
Acked-by: Peter De Schrijver
---
drivers/clk/tegra/clk-id.h | 2 --
Add the missing linux/delay.h include statement for udelay() used by
fence_udelay() macro.
Signed-off-by: Aapo Vienamo
---
drivers/clk/tegra/clk.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/tegra/clk.h b/drivers/clk/tegra/clk.h
index e1f8846..e3b9c22 100644
---
On Mon, Jul 09, 2018 at 09:05:39AM -0500, Gustavo A. R. Silva wrote:
> Make use of the swap macro and remove some unnecessary variables.
> This makes the code easier to read and maintain. Also, reduces the
> stack usage.
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by:
From: Peter De-Schrijver
Add a clock type to model the sdmmc switch divider clocks which have paths
to source clocks bypassing the divider (Low Jitter paths). These
are handled by selecting the lj path when the divider is 1 (ie the
rate is the parent rate), otherwise the normal path with divider
From: Peter De Schrijver
Move this to a separate file so it can be used to calculate the sdmmc
clock dividers.
Signed-off-by: Peter De-Schrijver
Signed-off-by: Aapo Vienamo
Acked-by: Peter De Schrijver
---
drivers/clk/tegra/Makefile | 1 +
drivers/clk/tegra/clk-divider.c | 30
On 09/07/18 11:20, Matthias Brugger wrote:
>
>
> On 09/07/18 08:05, Mars Cheng wrote:
>> This adds basic chip support for MT6765 SoC.
>>
>> Signed-off-by: Mars Cheng
>> ---
>> arch/arm64/boot/dts/mediatek/Makefile |1 +
>> arch/arm64/boot/dts/mediatek/mt6765-evb.dts | 33 ++
>>
Hi Darrick,
On 07/09/2018 11:39 AM, Darrick J. Wong wrote:
> On Mon, Jul 09, 2018 at 09:05:39AM -0500, Gustavo A. R. Silva wrote:
>> Make use of the swap macro and remove some unnecessary variables.
>> This makes the code easier to read and maintain. Also, reduces the
>> stack usage.
>>
>> This
Quoting Gregory CLEMENT (2018-06-19 05:34:46)
> Adopt the SPDX license identifier headers to ease license compliance
> management.
>
> Signed-off-by: Gregory CLEMENT
> ---
Applied to clk-next
The dra76x MCAN generic interconnect module has a its own
format for the bits in the control registers.
Therefore add a new module type, new regbits and new capabilities
specific to the MCAN module.
Acked-by: Rob Herring
CC: Tony Lindgren
Signed-off-by: Faiz Abbas
---
The ti-sysc driver provides support for manipulating the idle modes
and interconnect level resets.
Add the generic interconnect target module node for MCAN to support
the same.
CC: Tony Lindgren
Signed-off-by: Faiz Abbas
---
arch/arm/boot/dts/dra76x.dtsi | 18 ++
1 file
Add support for the MCAN peripheral which supports both classic
CAN messages along with the new CAN-FD message.
Add MCAN node to evm and enable it with a maximum datarate of 5 mbps
Signed-off-by: Faiz Abbas
---
arch/arm/boot/dts/dra76-evm.dts | 6 ++
arch/arm/boot/dts/dra76x.dtsi | 13
On Wed, Jun 06, 2018 at 01:42:10PM -0400, Thomas Hebb wrote:
> The Berlin PWM driver is currently broken on at least BG2CD. The
> symptoms manifest as a very non-linear and erratic mapping from the duty
> cycle configured in software to the duty cycle produced by hardware.
>
> The cause of the
On Mon, Jun 11, 2018 at 11:39:54AM +0530, Vignesh R wrote:
> EHRPWM has two PWM outputs. Currently with pwm-tiehrpwm driver, if PWMA
> is enabled and then disabled, and then PWMB is enabled, it is seen that
> PWMA turns on automatically. This series fixes the bug.
>
> Vignesh R (2):
> pwm:
On 03-07-18, 14:32, Paul Cercueil wrote:
> struct jz4780_dma_dev {
> struct dma_device dma_device;
> void __iomem *base;
> struct clk *clk;
> unsigned int irq;
> + unsigned int nb_channels;
> + enum jz_version version;
>
> uint32_t chan_reserved;
> -
On Tue, Jun 05, 2018 at 07:54:27PM +0200, Enric Balletbo i Serra wrote:
> Adopt the SPDX license identifier headers to ease license compliance
> management.
>
> Signed-off-by: Enric Balletbo i Serra
> ---
>
> Changes in v2: None
>
> drivers/pwm/pwm-cros-ec.c | 13 -
> 1 file
On Mon, Jul 9, 2018 at 5:10 PM, Manfred Spraul wrote:
> If idr_alloc within ipc_idr_alloc fails, then the return value (-ENOSPC)
> is used to calculate new->id.
> Technically, this is not a bug, because new->id is never accessed.
>
> But: Clean it up anyways: On error, just return, do not set
On 07/06/2018 08:28 PM, Xiubo Li wrote:
> On 2018/7/7 2:23, Mike Christie wrote:
>> On 07/05/2018 09:57 PM, xiu...@redhat.com wrote:
>>> static irqreturn_t uio_interrupt(int irq, void *dev_id)
>>> {
>>> struct uio_device *idev = (struct uio_device *)dev_id;
>>> -irqreturn_t ret =
On Tue, 2018-06-05 at 21:22 +0200, Thomas Gleixner wrote:
> On Tue, 5 Jun 2018, Joe Perches wrote:
>
> > Depending on how old your -next tree is, it may
> > not have a master that has the LICENSES directory.
> >
> > Change the lookup to HEAD and find whatever
> > LICENSE directory files are used
On 03-07-18, 14:32, Paul Cercueil wrote:
> +static inline void jz4780_dma_chan_disable(struct jz4780_dma_dev *jzdma,
> + unsigned int chn)
> +{
> + if (jzdma->version == ID_JZ4770)
> + jz4780_dma_ctrl_writel(jzdma, JZ_DMA_REG_DCKEC, BIT(chn));
> +}
this sounds as hardware
On 03-07-18, 14:32, Paul Cercueil wrote:
> enum jz_version {
> + ID_JZ4740,
> ID_JZ4770,
> ID_JZ4780,
> };
> @@ -247,6 +248,7 @@ static void jz4780_dma_desc_free(struct virt_dma_desc
> *vdesc)
> }
>
> static const unsigned int jz4780_dma_ord_max[] = {
> + [ID_JZ4740] =
On Mon, Jun 11, 2018 at 05:21:02PM -0700, Ray Jui wrote:
> This patch series improves the Broadcom PAXC support by 1) adding more
> quirks for specific versions of PAXC controllers; 2) adding logic to
> reject internally unconfigured physical functions from the embedded
> network processor acting
On Fri, Jun 22, 2018 at 11:51:44AM +0800, Huang, Ying wrote:
> Because there is no way to prevent a huge swap cluster from being
> split except when it has SWAP_HAS_CACHE flag set.
What about making get_mctgt_type_thp take the cluster lock? That function
would be the first lock_cluster user
On Mon, Jul 9, 2018 at 5:25 PM, Kirill A. Shutemov wrote:
> On Mon, Jul 09, 2018 at 05:21:55PM +0300, Kirill A. Shutemov wrote:
>> > This also happened only once so far:
>> > https://syzkaller.appspot.com/bug?extid=3f84280d52be9b7083cc
>> > and I can't reproduce it rerunning this program. So it's
Am Sonntag, 8. Juli 2018, 22:44:00 CEST schrieb Christoph Hellwig:
Hi Christoph,
>
> diff --git a/include/uapi/linux/aio_abi.h b/include/uapi/linux/aio_abi.h
> index 75846164290e..b7705ad66d78 100644
> --- a/include/uapi/linux/aio_abi.h
> +++ b/include/uapi/linux/aio_abi.h
> @@ -29,7 +29,11 @@
>
On 06-07-18, 15:02, Benjamin Gaignard wrote:
> The format specifier "%p" can leak kernel addresses.
> Use "%pK" instead.
The subsystem name is 'dmaengine' and not dma.
The git log on the subsystem should have told you this
Applied after fixing the tag, thanks.
--
~Vinod
On Tue 19 Jun 16:43 PDT 2018, Evan Green wrote:
> The MSM pinctrl driver quietly swallows errors that occur
> when trying to call .irq_set_wake. It should instead pass
> those failures up the chain so the caller can react to them.
> Swallowing the error for instance causes gpio_keys to think that
On 7/9/2018 9:52 AM, Will Deacon wrote:
> On Fri, Jul 06, 2018 at 02:10:55PM -0700, Paul E. McKenney wrote:
>> On Fri, Jul 06, 2018 at 04:37:21PM -0400, Alan Stern wrote:
>>> On Thu, 5 Jul 2018, Andrea Parri wrote:
>>>
> At any rate, it looks like instead of strengthening the relation, I
>
Quoting Taniya Das (2018-07-09 02:34:07)
>
>
> On 7/9/2018 1:07 PM, Stephen Boyd wrote:
> > Quoting Taniya Das (2018-07-09 00:07:21)
> >>
> >>
> >> On 7/9/2018 11:46 AM, Stephen Boyd wrote:
>
> > Why is the nocache flag needed? Applies to all clks in this file.
> >
>
>
2018-07-09 16:08 GMT+02:00 Linus Walleij :
> On Wed, Jun 6, 2018 at 7:44 PM Rafael David Tinoco
> wrote:
>
>> Following logic from commit: 22f6592b23, GPIOHANDLE_REQUEST_OUTPUT
>> should handle errors same way as GPIOHANDLE_REQUEST_INPUT does, or else
>> the following error occurs:
>>
>>
On Fri, Jul 06, 2018 at 12:18:27PM +0200, Vincent Guittot wrote:
> Hi Morten,
>
> On Wed, 4 Jul 2018 at 12:18, Morten Rasmussen
> wrote:
> >
> > On asymmetric cpu capacity systems (e.g. Arm big.LITTLE) it is crucial
> > for performance that cpu intensive tasks are aggressively migrated to
> >
On Tue, Jul 03, 2018 at 05:03:39PM +0200, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> CAN2 currently fails on probe as follows:
>
> mcp251x spi1.1: Probe failed, err=19
>
> Fix this by enabling input on pin mux of resp. SPI4 pins.
>
> Signed-off-by: Marcel Ziswiler
>
> Signed-off-by:
ipc_addid() is impossible to use:
- for certain failures, the caller must not use ipc_rcu_putref(),
because the reference counter is not yet initialized.
- for other failures, the caller must use ipc_rcu_putref(),
because parallel operations could be ongoing already.
The patch cleans that up,
Hi,
I have merged the patches from Dmitry, Davidlohr and myself:
- patch #1-#6: Fix syzcall findings & further race cleanups
- patch #7: Cleanup from Dmitry for ipc_idr_alloc.
- patch #8-#11: rhashtable improvement from Davidlohr
- patch #12: Another cleanup for ipc_idr_alloc.
@Davidlohr:
ipc_addid() initializes kern_ipc_perm.seq after having called
ipc_idr_alloc().
Thus a parallel semop() or msgrcv() that uses ipc_obtain_object_check()
may see an uninitialized value.
The patch moves the initialization of kern_ipc_perm.seq before the
calls of ipc_idr_alloc().
Notes:
1) This
The comment that explains ipc_obtain_object_check is wrong:
The function checks the sequence number, not the reference
counter.
Note that checking the reference counter would be meaningless:
The reference counter is decreased without holding any locks,
thus an object with
ipc/util.c contains multiple functions to get the ipc object
pointer given an id number.
There are two sets of function: One set verifies the sequence
counter part of the id number, other functions do not check
the sequence counter.
The standard for function names in ipc/util.c is
- ..._check()
On 08/07/18 21:59, Martin Blumenstingl wrote:
> Hi Thomas,
>
> On Tue, Jul 3, 2018 at 6:48 PM Sudeep Holla wrote:
>>
>> Hi Thomas,
>>
>> On Tue, Jul 03, 2018 at 06:08:19PM +0200, Thomas Gleixner wrote:
>>
>> [...]
>>
> / # cat /sys/devices/system/clockevents/broadcast/current_device
>
From: Davidlohr Bueso
As of commit ce91f6ee5b3b ("mm: kvmalloc does not fallback to vmalloc for
incompatible gfp flags") we can simplify the caller and trust kvzalloc() to
just do the right thing. For the case of the GFP_ATOMIC context, we can
drop the __GFP_NORETRY flag for obvious reasons, and
From: Dmitry Vyukov
ipc_idr_alloc refactoring
Signed-off-by: Dmitry Vyukov
Signed-off-by: Manfred Spraul
---
ipc/util.c | 51 +--
1 file changed, 13 insertions(+), 38 deletions(-)
diff --git a/ipc/util.c b/ipc/util.c
index
From: Davidlohr Bueso
rhashtable_init() may fail due to -ENOMEM, thus making the
entire api unusable. This patch removes this scenario,
however unlikely. In order to guarantee memory allocation,
this patch always ends up doing GFP_KERNEL|__GFP_NOFAIL
for both the tbl as well as
GCC_MSS_AXIS2 clock is used for disabling boot IMEM (a part of
AP boot up). With Boot IMEM disable now a part TZ/ATF, AXIS2
clock is no longer required post AP boot up and expected to
remain untouched. However if the clock is turned ON after Q6
is brought out of reset and later turned off, it
ipc_addid() initializes kern_ipc_perm.id after having called
ipc_idr_alloc().
Thus a parallel semop() or msgrcv() that uses ipc_obtain_object_idr()
may see an uninitialized value.
The patch moves all accesses to kern_ipc_perm.id under the spin_lock().
The issues is related to the finding of
On Mon, Jul 09, 2018 at 05:21:55PM +0300, Kirill A. Shutemov wrote:
> > This also happened only once so far:
> > https://syzkaller.appspot.com/bug?extid=3f84280d52be9b7083cc
> > and I can't reproduce it rerunning this program. So it's either a very
> > subtle race, or fd in the middle of netlink
On Fri, 6 Jul 2018 08:22:01 +0200
Claudio wrote:
> Hello all,
>
> I have been experimenting with the idea of leaving ftrace enabled, with sched
> events,
> on production systems.
>
> The main concern that I am having at the moment is about the impact on the
> system.
> Enabling the sched
Quoting Linus Walleij (2018-07-09 06:54:01)
> On Mon, Jul 2, 2018 at 7:56 PM Stephen Boyd wrote:
>
> > I could do with some more clarity from Linus in the "Drivers needing
> > both pin control and GPIOs" section of
> > Documentation/driver-api/pinctl.rst but I read that section as stating
> >
Building with KASAN and SLUB but without sysfs now results in a build-time
error:
WARNING: unmet direct dependencies detected for SLUB_DEBUG
Depends on [n]: SLUB [=y] && SYSFS [=n]
Selected by [y]:
- KASAN [=y] && HAVE_ARCH_KASAN [=y] && (SLUB [=y] || SLAB [=n] &&
!DEBUG_SLAB [=n]) &&
On Fri, 6 Jul 2018 17:42:56 +0800
piaojun wrote:
> From my test, the second mount will fail after umounting successfully.
> The reason is that we put refcount of trans_mod in the correct case rather
> than the error case in parse_opts() at last. That will cause the refcount
> decrease to -1, and
On Tue, Jun 19, 2018 at 3:41 PM Rob Herring wrote:
>
> The DT core will call of_platform_default_populate, so it is not
> necessary for arch specific code to call it unless there are custom
> match entries, auxdata or parent device. Neither of those apply here, so
> remove the call.
>
> Cc:
On Tue, Jun 19, 2018 at 3:40 PM Rob Herring wrote:
>
> The DT core will call of_platform_populate, so it is not necessary for
> arch specific code to call it unless there are custom match entries,
> auxdata or parent device. Neither of those apply here, so remove the call.
>
> Cc: Yoshinori Sato
601 - 700 of 1608 matches
Mail list logo
