When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc:
Signed-off-by: Greg
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc:
Signed-off-by: Greg
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Dave Hansen
Cc: Andy Lutomirski
Cc: Peter Zijlstra
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Paolo Bonzini
Cc: "Radim Krčmář"
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter
When calling debugfs functions, there is no need to ever check the
return value. The function can work or not, but the code logic should
never do something different based on this.
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: "H. Peter Anvin"
Cc:
Cc: Tony Luck
Cc: Vishal
When calling debugfs code, there is no need to ever check the return
value of the call, as no logic should ever change if a call works
properly or not. Fix up a bunch of x86-specific code to not care about
the results of debugfs.
Greg Kroah-Hartman (6):
x86: mce: no need to check return value
Kees Cook writes:
> On Tue, Jan 22, 2019 at 8:15 AM Greg KH wrote:
>>
>> On Mon, Jan 21, 2019 at 10:36:18AM -0800, Andi Kleen wrote:
>> > > + /* Check the start address: needs to be page-aligned.. */
>> > > +- if (start & ~PAGE_MASK)
>> > > ++ if (start & ~PAGE_MASK) {
>> > > ++
>> > > ++
Hi Min,
On Tue, Jan 22, 2019 at 05:36:13PM +0800, Min Guo wrote:
> Hi Bin,
>
> Sorry to bother you again, I encounter a problem about the extcon
> property.
>
> I don't find a common driver describing the usb-connector. Is
> there any driver that I can refer to, specially the way to switch MUSB
Hello Dan,
Am 22.01.19 um 14:37 schrieb Dan Murphy:
> Wolfgang
>
> On 1/22/19 3:35 AM, Wolfgang Grandegger wrote:
>> Hello,
>>
>> Am 17.01.19 um 21:05 schrieb Dan Murphy:
>>> Migrate the m_can code to use the m_can_platform framework
>>> code.
>>>
>>> Signed-off-by: Dan Murphy
>>> ---
>>>
I have a mission worth $ 11,000,000.00 from you
There's no need to export fcoe_ctlr_destroy_store as a symbol, so remove
the EXPORT_SYMBOL() line for it.
Cc: Johannes Thumshirn
Cc: "James E.J. Bottomley"
Cc: "Martin K. Petersen"
Signed-off-by: Greg Kroah-Hartman
---
drivers/scsi/fcoe/fcoe_transport.c | 1 -
1 file changed, 1 deletion(-)
We are trying to get rid of BUS_ATTR() and the usage of that in the fcoe
driver can be trivially converted to use BUS_ATTR_WO(), so use that
instead.
Cc: Johannes Thumshirn
Cc: "James E.J. Bottomley"
Cc: "Martin K. Petersen"
Signed-off-by: Greg Kroah-Hartman
---
v2: Made simpler with wrapper
On Tue, 22 Jan 2019 at 15:24, Vincent Guittot
wrote:
>
> From: Thara Gopinath
>
> This patch replaces jiffies based accounting for runtime_active_time
> and runtime_suspended_time with ktime-based accounting. This makes the
> runtime debug counters inline with genpd and other PM subsytems which
From: Colin Ian King
There are a bunch of various indentation issues, clean these up.
Signed-off-by: Colin Ian King
---
drivers/usb/gadget/function/f_uac1.c | 8 ++---
drivers/usb/gadget/legacy/inode.c| 40
drivers/usb/gadget/udc/aspeed-vhub/hub.c | 2 +-
On 22-Jan 13:29, Quentin Perret wrote:
> On Tuesday 22 Jan 2019 at 12:45:46 (+), Patrick Bellasi wrote:
> > On 22-Jan 12:13, Quentin Perret wrote:
> > > On Tuesday 15 Jan 2019 at 10:15:08 (+), Patrick Bellasi wrote:
> > > > The Energy Aware Scheduler (AES) estimates the energy impact of
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger
crash:
Reported-and-tested-by:
syzbot+148c2885d71194f18...@syzkaller.appspotmail.com
Tested on:
commit: 48b161983ae5 Merge tag 'xarray-5.0-rc3' of git://git.infra..
git tree: upstream
kernel
Move pm_runtime accounted time to raw nsec. The subject of the patchset
has changed as the 1st patch of the previous versions has been queued by
Rafael.
Patch 1 set accounting_timestamp to 0 in pm_runtime_init and update it when
enable. So
we remove ordering constraint between timekeeping_init
From: Thara Gopinath
This patch replaces jiffies based accounting for runtime_active_time
and runtime_suspended_time with ktime-based accounting. This makes the
runtime debug counters inline with genpd and other PM subsytems which
use ktime-based accounting.
Timekeeping is initialized before
Initializing accounting_timestamp to something different from 0 during
pm_runtime_init() doesn't make sense and put useless ordering constraint between
timekeeping_init() and pm_runtime_init().
PM runtime should start accounting time only when it is enable and discard
the period when disabled.
Set
On Tue, 22 Jan 2019 at 14:52, Geert Uytterhoeven wrote:
>
> Hi Heiner,
>
> On Fri, Jan 18, 2019 at 9:58 PM Heiner Kallweit wrote:
> > On 18.01.2019 09:48, Krzysztof Kozlowski wrote:
> > > On Fri, 18 Jan 2019 at 09:39, Krzysztof Kozlowski wrote:
> > >> On today's next (next-20190118) my Colibri
On Fri, Dec 28, 2018 at 01:50:53PM +0100, Hannes Reinecke wrote:
> On 12/21/18 4:29 PM, James Bottomley wrote:
> > [scsi list cc added]
> > On Fri, 2018-12-21 at 08:54 +0100, Greg Kroah-Hartman wrote:
> > > We are trying to get rid of BUS_ATTR() and the usage of that in the
> > > fcoe driver can
commit d6abe6df706c66d803e6dd4fe98c1b6b7f125a56 (drm/bridge:
sil_sii8620: do not have a dependency of RC_CORE) added a dependency on
INPUT. However, this causes problems with other drivers, in particular
an input driver that depends on MFD_INTEL_LPSS_PCI (to be added in a
future commit):
From: Colin Ian King
A return statement is indented incorrectly, fix this.
Signed-off-by: Colin Ian King
---
drivers/staging/rtl8723bs/core/rtw_xmit.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_xmit.c
On Tue, Jan 08, 2019 at 10:21:25AM -0800, Florian Fainelli wrote:
On 1/7/19 9:01 PM, Florian Fainelli wrote:
Le 12/4/18 à 4:04 PM, Ivan Khoronzhuk a écrit :
On Tue, Dec 04, 2018 at 11:49:27AM -0800, Florian Fainelli wrote:
...
I was thinking also about pinned list of vlans to the address,
On 22/01/2019 15:02, Marc Gonzalez wrote:
> On 21/01/2019 18:42, Mike Rapoport wrote:
>
>> If I understood correctly, the trouble comes from no-map range allocated in
>> early_init_dt_alloc_reserved_memory_arch().
>>
>> There's indeed imbalance, because memblock_alloc() does kmemleak_alloc(),
Em Fri, Jan 18, 2019 at 11:46:55AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Jan 17, 2019 at 08:15:19AM -0800, Song Liu escreveu:
> > This patch synthesize PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT for
> > BPF programs loaded before perf-record. This is achieved by gathering
> >
Looks like book3s/32 doesn't set RI on machine check, so
checking RI before calling die() will always be fatal
allthought this is not an issue in most cases.
Fixes: b96672dd840f ("powerpc: Machine check interrupt is a non-maskable
interrupt")
Fixes: daf00ae71dad ("powerpc/traps: restore
Hello,
syzbot has tested the proposed patch but the reproducer still triggered
crash:
possible deadlock in __do_page_fault
8021q: adding VLAN 0 to HW filter on device team0
8021q: adding VLAN 0 to HW filter on device team0
8021q: adding VLAN 0 to HW filter on device team0
8021q: adding VLAN
The EVM consists of a system on module (SOM) and baseboard, and LCD.
This patch adds a DTSI file for the SOM and baseboard separately,
then a wrapper to combine them and specify processor type and a
LCD information.
Signed-off-by: Adam Ford
diff --git
Exit latency is the time from exiting the idle state to execute
the first instruction. This place may be a typo , so fix it.
Signed-off-by: Yangtao Li
---
Documentation/admin-guide/pm/cpuidle.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On 21/01/2019 18:42, Mike Rapoport wrote:
> If I understood correctly, the trouble comes from no-map range allocated in
> early_init_dt_alloc_reserved_memory_arch().
>
> There's indeed imbalance, because memblock_alloc() does kmemleak_alloc(), but
> memblock_remove() does not do
This seems to have slipped in by accident when sorting the entries.
Fixes: ffbdd9172ee2f53020f763574b4cdad8d9760a4f
Signed-off-by: Alexander Dahl
---
Notes:
v1 -> v2:
* rebase onto v5.0-rc3 (was v4.20-rc6)
drivers/net/can/usb/Kconfig | 6 --
1 file changed, 6 deletions(-)
diff
CC: sta...@vger.kernel.org
On Fri, 2018-12-21 at 18:17 +0800, Linus Walleij wrote:
> On Thu, Dec 13, 2018 at 3:28 AM Ryder Lee wrote:
>
> > Remove prompts to make all pinctrl cores to non-visible symbols and
> > make sure the target SoCs would be coupled with the corresponding
> > cores.
> >
>
On 22-Jan 14:28, Peter Zijlstra wrote:
> On Tue, Jan 22, 2019 at 10:43:05AM +, Patrick Bellasi wrote:
> > On 22-Jan 10:37, Peter Zijlstra wrote:
>
> > > Sure, I get that. What I don't get is why you're adding that (2) here.
> > > Like said, __sched_setscheduler() already does a
On 1/22/19 2:55 PM, Alexander Dahl wrote:
> This seems to have slipped in by accident when sorting the entries.
>
> Fixes: ffbdd9172ee2f53020f763574b4cdad8d9760a4f
> Signed-off-by: Alexander Dahl
Added to linux-can.
Tnx,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde
Hi Sai,
On 01/22/2019 01:37 PM, Sai Prakash Ranjan wrote:
Add coresight components found on Qualcomm SDM845 SoC.
Signed-off-by: Sai Prakash Ranjan
Sorry, but I hadn't noticed the PID override strings below. Please
find the question.
---
Depends on AOSS QMP side channel patches and AMBA
On Wed, May 9, 2018 at 6:57 PM 'Todd Kjos' via syzkaller-bugs
wrote:
>
> +Joel Fernandes
>
> On Wed, May 9, 2018 at 12:55 AM Eric Biggers wrote:
>>
>> [+ashmem maintainers]
>>
>> On Sun, Apr 29, 2018 at 10:00:03AM -0700, syzbot wrote:
>> > Hello,
>> >
>> > syzbot hit the following crash on
Em Thu, Dec 06, 2018 at 11:18:18AM -0800, Davidlohr Bueso escreveu:
> At the cost of an extra pointer, we can avoid the O(logN) cost
> of finding the first element in the tree (smallest node), which
> is something heavily required for histograms. Specifically, the
> following are converted to
On Fri, Aug 10, 2018 at 6:18 PM Matthew Wilcox wrote:
>
>
> This is another ashmem lockdep splat. Forwarding to the appropriate ashmem
> people.
Let's test Tetsuo's patch
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
> On Fri, Aug 10, 2018 at 04:59:02AM
On Tue, Jan 15, 2019 at 10:15:04AM +, Patrick Bellasi wrote:
> diff --git a/include/linux/sched.h b/include/linux/sched.h
> index 84294925d006..c8f391d1cdc5 100644
> --- a/include/linux/sched.h
> +++ b/include/linux/sched.h
> @@ -625,6 +625,11 @@ struct uclamp_se {
> unsigned int
On Tue, 22 Jan 2019 at 14:28, Torsten Duwe wrote:
>
> On Tue, Jan 22, 2019 at 10:18:17AM +, Julien Thierry wrote:
> > Hi Torsten,
> >
> > A few suggestions below.
> >
> > > +#ifdef CONFIG_DYNAMIC_FTRACE_WITH_REGS
> > > +#define ARCH_SUPPORTS_FTRACE_OPS 1
> > > +#define REC_IP_BRANCH_OFFSET
All callers of mftb() expect 'unsigned long', and the function itself
only returns lower part of the TB so it really is 'unsigned long'
not 'unsigned long long'
Signed-off-by: Christophe Leroy
---
tools/testing/selftests/powerpc/benchmarks/null_syscall.c | 2 +-
1 file changed, 1 insertion(+),
On Tue, Jan 22, 2019 at 2:52 PM Dmitry Vyukov wrote:
>
> On Tue, Jan 22, 2019 at 11:32 AM Tetsuo Handa
> wrote:
> >
> > On 2019/01/22 19:12, Dmitry Vyukov wrote:
> > > On Tue, Jan 22, 2019 at 11:02 AM Tetsuo Handa
> > > wrote:
> > >>
> > >> On 2018/09/22 8:21, Andrew Morton wrote:
> > >>> On
Web de correo electrónico de administración de notificaciones
Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros
propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a
todos nuestros clientes de correo web. Su cuenta de correo electrónico se
Thanks a lot for the testing!
I'll play with it today hopefully.
On Tue, Jan 22, 2019 at 05:31:10AM +, xuyandong wrote:
> Hi Bjorn and Michael
>
> After trying to reproduce the problem for a whole day, the bug did not show up
> any more. So I think the new patch does solve this problem.
>
>
On Tue, Jan 22, 2019 at 11:32 AM Tetsuo Handa
wrote:
>
> On 2019/01/22 19:12, Dmitry Vyukov wrote:
> > On Tue, Jan 22, 2019 at 11:02 AM Tetsuo Handa
> > wrote:
> >>
> >> On 2018/09/22 8:21, Andrew Morton wrote:
> >>> On Thu, 20 Sep 2018 19:33:15 -0400 Joel Fernandes
> >>> wrote:
> >>>
>
On 22.01.19 14:18, Boris Brezillon wrote:
> On Tue, 22 Jan 2019 11:23:29 +
> Schrempf Frieder wrote:
>
>> From: Frieder Schrempf
>>
>> The information about where the manufacturer puts the bad block
>> markers inside the bad block and in the OOB data is stored in
>> different places. Let's
40x/booke have another path to reach 3f from transfer_to_handler,
so ACCOUNT_CPU_USER_ENTRY() have to be moved there.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/entry_32.S | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git
MSR[RI] has already been cleared a few lines above.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/entry_32.S | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/powerpc/kernel/entry_32.S b/arch/powerpc/kernel/entry_32.S
index 0768dfd8a64e..c2b66fbbf7f0 100644
---
Hi Heiner,
On Fri, Jan 18, 2019 at 9:58 PM Heiner Kallweit wrote:
> On 18.01.2019 09:48, Krzysztof Kozlowski wrote:
> > On Fri, 18 Jan 2019 at 09:39, Krzysztof Kozlowski wrote:
> >> On today's next (next-20190118) my Colibri VF50 board fails to boot up
> >> from network (DHCP, NFSv4 root).
On 22/01/2019 13:28, Torsten Duwe wrote:
> On Tue, Jan 22, 2019 at 10:18:17AM +, Julien Thierry wrote:
>> Hi Torsten,
>>
>> A few suggestions below.
>>
>>> +#ifdef CONFIG_DYNAMIC_FTRACE_WITH_REGS
>>> +#define ARCH_SUPPORTS_FTRACE_OPS 1
>>> +#define REC_IP_BRANCH_OFFSET AARCH64_INSN_SIZE
>>>
https://slashdot.org/submission/9129664/author-rescinds-gpl
Quote:
"
Then you should have used them.
Not necessary, the language used in the press release identifies them
easily.
should
As if I somehow can't just rescind using their names either.
License to use/modify/etc the GPC Slots 2 code is hereby terminated for.
Alex "Skud" Bayley, and
On Mon, Jan 21, 2019 at 8:38 PM Ran Wang wrote:
>
> Hi Rob,
>
> On January 22, 2019 09:03, Rob Herring wrote:
> >
> > On Wed, Jan 16, 2019 at 06:48:06AM +, Ran Wang wrote:
> > > When DWC3 is set to host mode by programming register DWC3_GCTL,
> > VUBS
> >
> > s/VUBS/VBUS/
>
> Yes, will fix it
From: Naveen Kumar Parna
Without ".owner = THIS_MODULE" it is possible to crash the kernel
by unloading the mbcs module while someone works with the file.
Fix this by initializing the ‘struct file_operations' ->owner with
THIS_MODULE.
Signed-off-by: Naveen Kumar Parna
---
drivers/char/mbcs.c
On Tue, Jan 22, 2019 at 1:24 PM Christian Brauner wrote:
> On Tue, Jan 22, 2019 at 12:46:56PM +0100, Christian Brauner wrote:
> > On Tue, Jan 22, 2019 at 12:42:44PM +0100, Arnd Bergmann wrote:
> > >
> > > You need to change __NR_syscalls to 425 as well. This will
> > > clearly create a conflict,
On 1/22/2019 3:07 AM, Mathieu Poirier wrote:
On Mon, 21 Jan 2019 at 11:48, Mathieu Poirier
wrote:
On Mon, Jan 21, 2019 at 04:18:36PM +0530, Vivek Gautam wrote:
On 1/18/2019 5:52 PM, Sai Prakash Ranjan wrote:
SDM845 has ETMv4.2 and can use the existing etm4x driver.
But the current etm
Hi Andrew,
Andrew Lunn wrote on Tue, 22 Jan 2019 14:20:05 +0100:
> > I am not sure to understand what is lost. On my setup ethtool shows
> > that everything is fine after resume but maybe I fall into a "default"
> > working case.
>
> Hi Miquèl
>
> Is the power removed from the switch? If
Hi Mathieu,
On 1/22/2019 12:07 AM, Mathieu Poirier wrote:
Hi Sai,
On Fri, Jan 18, 2019 at 05:52:53PM +0530, Sai Prakash Ranjan wrote:
Add coresight components found on Qualcomm SDM845 SoC.
Signed-off-by: Sai Prakash Ranjan
---
This depends on AMBA bus pclk change by Bjorn Andersson [1].
On Mon, 21 Jan 2019 at 19:28, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.152 release.
> There are 51 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Tue, Jan 22, 2019 at 3:09 AM wrote:
>
> Hi Rob,
>
> On 22/01/2019 at 02:10, Rob Herring wrote:
> > On Wed, Jan 16, 2019 at 10:57:40AM +0100, Nicolas Ferre wrote:
> >> This removes a line left while adding the correct compatibility string for
> >> sama5d3 10/100 interface. Now use the
On Mon, Jan 21, 2019 at 12:21:17PM +0100, Oleg Nesterov wrote:
> And in any case I do not understand the idea to use the second
> in-kernel struct fpu. A signal handler can be interrupted by another
> signal, this will need to save/restore the FPU state again.
Well, we were just speculating
On Tue, Jan 22, 2019 at 3:00 AM wrote:
>
> Hi Rob,
>
> On 22/01/2019 at 02:07, Rob Herring wrote:
> > On Wed, Jan 16, 2019 at 10:57:38AM +0100, Nicolas Ferre wrote:
> >> Update the Reset Controller's binding to add new SoC compatibility string.
> >>
> >> Signed-off-by: Nicolas Ferre
> >> ---
>
Remove the duplicate inclusion of qcom,gcc-sdm845.h
mistakenly introduced by commit 6e17f8140521 ("arm64:
dts: sdm845: add prng-ee node").
Signed-off-by: Sai Prakash Ranjan
Reviewed-by: Douglas Anderson
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 1 -
1 file changed, 1 deletion(-)
diff --git
SDM845 has ETMv4.2 and can use the existing etm4x driver.
But the current etm driver checks only for ETMv4.0 and
errors out for other etm4x versions. This patch adds this
missing support to enable SoC's with ETMv4x to use same
driver by checking only the ETM architecture major version
number.
From: Vivek Gautam
Enable coresight support by adding device nodes for the
available source, sinks and channel blocks on msm8996.
This also adds coresight cpu debug nodes.
Signed-off-by: Vivek Gautam
Signed-off-by: Sai Prakash Ranjan
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 448
Hi Hans,
Thanks for the discussion and sorry for my late reply due to the holidays.
I replied inline below:
On Sun, Jan 20, 2019 at 06:49:56PM -0800, h...@zytor.com wrote:
> On January 20, 2019 5:45:53 PM PST, Joel Fernandes
> wrote:
> >On Sun, Jan 20, 2019 at 01:58:15PM -0800, h...@zytor.com
Add coresight components found on Qualcomm SDM845 SoC.
Signed-off-by: Sai Prakash Ranjan
---
Depends on AOSS QMP side channel patches and AMBA bus pclk change
by Bjorn Andersson [1][2].
Also depends on patch ("arm64: dts: qcom: sdm845: Increase address
and size cells for soc") [3].
[1]
This patch series adds support for coresight on SDM845 and MSM8996.
* Patch 1 adds device tree nodes for SDM845 coresight components.
* Patch 2 adds device tree nodes for MSM8996 coresight components.
* Patch 3 enables support for ETMv4.2 and enables SDM845 to make
use of same driver(etm4x).
On Mon, Jan 21, 2019 at 8:16 PM Chen-Yu Tsai wrote:
>
> On Tue, Jan 22, 2019 at 8:19 AM Rob Herring wrote:
> >
> > On Mon, Jan 21, 2019 at 05:57:57PM +0800, Chen-Yu Tsai wrote:
> > > On Mon, Jan 21, 2019 at 5:50 PM Maxime Ripard
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I'm a bit late
Wolfgang
On 1/22/19 3:35 AM, Wolfgang Grandegger wrote:
> Hello,
>
> Am 17.01.19 um 21:05 schrieb Dan Murphy:
>> Migrate the m_can code to use the m_can_platform framework
>> code.
>>
>> Signed-off-by: Dan Murphy
>> ---
>> drivers/net/can/m_can/Kconfig | 12 +
>>
On 14.12.18 22:16, Thomas Schöbel-Theuer wrote:
Hi,
> Currently, we have a few thousands of servers relying on 32bit ABIs in> some
> thousands of VMs and/or containers of various types (LXC,
OpenVZ,> etc).
Similar w/ my clients, but in Industrie/Embedded/i4.0 world. We have
thousands of devices
On Mon, 21 Jan 2019 at 20:58, Bhupesh Sharma wrote:
>
> Hi Sumit,
>
> On Mon, Jan 21, 2019 at 3:00 PM Sumit Garg wrote:
> >
> > Introduce a generic TEE bus driver concept for TEE based kernel drivers
> > which would like to communicate with TEE based devices/services.
> >
> > In this TEE bus
On Mon, 21 Jan 2019 at 19:16, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.20.4 release.
> There are 111 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
Commit-ID: ee35b9b9f6d52ba134b4e75442531935f295be7a
Gitweb: https://git.kernel.org/tip/ee35b9b9f6d52ba134b4e75442531935f295be7a
Author: Borislav Petkov
AuthorDate: Thu, 17 Jan 2019 13:02:05 +0100
Committer: Borislav Petkov
CommitDate: Tue, 22 Jan 2019 14:13:35 +0100
x86/traps: Have
Commit-ID: bae54dc4f353653bbd3e3081754adad05da1d4dd
Gitweb: https://git.kernel.org/tip/bae54dc4f353653bbd3e3081754adad05da1d4dd
Author: Borislav Petkov
AuthorDate: Fri, 18 Jan 2019 00:05:40 +0100
Committer: Borislav Petkov
CommitDate: Tue, 22 Jan 2019 14:16:39 +0100
x86/fpu: Get rid
On Tuesday 22 Jan 2019 at 12:45:46 (+), Patrick Bellasi wrote:
> On 22-Jan 12:13, Quentin Perret wrote:
> > On Tuesday 15 Jan 2019 at 10:15:08 (+), Patrick Bellasi wrote:
> > > The Energy Aware Scheduler (AES) estimates the energy impact of waking
>
> [...]
>
> > > +
On an arm64 ThunderX2 server, the first kmemleak scan would crash [1]
with CONFIG_DEBUG_VM_PGFLAGS=y due to page_to_nid() found a pfn that is
not directly mapped (MEMBLOCK_NOMAP). Hence, the page->flags is
uninitialized.
This is due to the commit 9f1eb38e0e11 ("mm, kmemleak: little
optimization
On Mon, Jan 21, 2019 at 07:58:36PM -0700, Jason Gunthorpe wrote:
> On Tue, Jan 22, 2019 at 03:02:18AM +0200, Jarkko Sakkinen wrote:
> > On Sun, Jan 20, 2019 at 06:04:13PM +0200, Jarkko Sakkinen wrote:
> > > On Fri, Jan 18, 2019 at 02:09:18PM -0800, James Bottomley wrote:
> > > > On Fri, 2019-01-18
On Tue, Jan 22, 2019 at 10:43:05AM +, Patrick Bellasi wrote:
> On 22-Jan 10:37, Peter Zijlstra wrote:
> > Sure, I get that. What I don't get is why you're adding that (2) here.
> > Like said, __sched_setscheduler() already does a dequeue/enqueue under
> > rq->lock, which should already take
On Tue, Jan 22, 2019 at 10:18:17AM +, Julien Thierry wrote:
> Hi Torsten,
>
> A few suggestions below.
>
> > +#ifdef CONFIG_DYNAMIC_FTRACE_WITH_REGS
> > +#define ARCH_SUPPORTS_FTRACE_OPS 1
> > +#define REC_IP_BRANCH_OFFSET AARCH64_INSN_SIZE
> > +/* All we need is some magic value. Simply use
On Fri, Jan 18, 2019 at 12:35:43PM +0100, Christoph Hellwig wrote:
> On Wed, Jan 16, 2019 at 06:10:13PM +, Robin Murphy wrote:
> > It's a shame that this is pretty much a duplication of
> > debug_dma_dump_mappings(), but there seems no straightforward way to define
> > one in terms of the
Hi, recently I came across some code and it seems to be able to leak
kernel address?
Is the following code cause info leak in the Linux kernel?
The callback function address is printed to debugfs.
The local user could know the kernel object address, and is able to
bypass kASLR.
linux-4.14.90
On Tue, Jan 22, 2019 at 01:40:02PM +0800, Jun Li wrote:
> Hi Heikki,
> Heikki Krogerus 于2018年10月24日周三 下午11:06写道：
> >
> > When the connections are defined in firmware, struct
> > device_connection will have the fwnode member pointing to
> > the device node (struct fwnode_handle) of the requested
>
Hello,
On Mon 14-01-19 11:30:11, Jan Kara wrote:
> On Mon 14-01-19 01:33:30, Kevin Weidemann wrote:
> > this is RE the patch 8515b9edf7a0c9dcf1ad218ccc783700db217336 (Upstream
> > commit a9ad01bc759df79b0012f43ee52164391e31cd96) in 4.18.20.
> >
> > I have an issue with UDF. I used to be able to
From: Philippe Schenker
Add the stmpe-adc DT node as found on Toradex iMX6 modules
Signed-off-by: Philippe Schenker
---
arch/arm/boot/dts/imx6qdl-apalis.dtsi | 22 ++
arch/arm/boot/dts/imx6qdl-colibri.dtsi | 22 ++
2 files changed, 28 insertions(+),
From: Philippe Schenker
Hello,
Recently the STMPE811 driver got pulled by MFD (for 5.1).
This patches I'm sending are now adding support for STMPE811 ADC in
devicetree. These patches have been in the STMPE811 ADC driver patchset
but were not pulled by Lee, as they had no reviews and I also
From: Philippe Schenker
Add the stmpe-adc DT node as found on Toradex T30 modules
Signed-off-by: Philippe Schenker
---
arch/arm/boot/dts/tegra30-apalis-v1.1.dtsi | 22 ++
arch/arm/boot/dts/tegra30-apalis.dtsi | 22 ++
From: Priit Laes
Even though HDMI connector features hotplug detect pin (HPD), there
are older devices which do not support it. For these devices fall
back to additional check on I2C bus to probe for EDID data.
One known example is HDMI/DVI display with following edid:
$ xxd -p display.edid
The DMA engine clients can trigger DMA engine automatically by setting
the corresponding hardware slave id for the DMA engine. Thus add one
cell to present the hardware slave id for DMA clients.
Signed-off-by: Baolin Wang
---
Documentation/devicetree/bindings/dma/sprd-dma.txt | 12
Change to use 2 cells to provide the channel id and slave id for client.
Signed-off-by: Baolin Wang
---
arch/arm64/boot/dts/sprd/whale2.dtsi |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm64/boot/dts/sprd/whale2.dtsi
b/arch/arm64/boot/dts/sprd/whale2.dtsi
Add new DMA engine translation function to get the hardware slave id
of the corresponding DMA engine channel. Meanwhile we do not need
to set default slave id in sprd_dma_alloc_chan_resources(), remove it.
Signed-off-by: Baolin Wang
---
drivers/dma/sprd-dma.c | 49
> I am not sure to understand what is lost. On my setup ethtool shows
> that everything is fine after resume but maybe I fall into a "default"
> working case.
Hi Miquèl
Is the power removed from the switch? If so, you need to restore the
full switch configuration. The current code might be
On Tue, 22 Jan 2019 11:23:29 +
Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The information about where the manufacturer puts the bad block
> markers inside the bad block and in the OOB data is stored in
> different places. Let's move this information to nand_chip.options
> and
> From: Lucas Stach [mailto:l.st...@pengutronix.de]
> Sent: Tuesday, January 22, 2019 8:52 PM
> To: Aisheng Dong ; linux-kernel@vger.kernel.org
> Cc: linux-arm-ker...@lists.infradead.org; shawn...@kernel.org; dl-linux-imx
> ; robh...@kernel.org; devicet...@vger.kernel.org;
> t...@linutronix.de;
On Tue, 22 Jan 2019 13:48:48 +0100
Andreas Ziegler wrote:
> Commit 9178412ddf5a ("tracing: probeevent: Return consumed
> bytes of dynamic area") improved the string fetching
> mechanism by returning the number of required bytes after
> copying the argument to the dynamic area. However, this
>
On 22.01.19 12:22, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> The information about where the manufacturer puts the bad block
> markers inside the bad block and in the OOB data is stored in
> different places. Let's move this information to nand_chip.options
> and
On Mon, Jan 21, 2019 at 03:37:41PM -0800, Florian Fainelli wrote:
On 12/4/18 3:42 PM, Ivan Khoronzhuk wrote:
On Tue, Dec 04, 2018 at 11:49:27AM -0800, Florian Fainelli wrote:
[...]
Ivan, based on the recent submission I copied you on [1], it sounds like
we want to move ahead with your
Hi Balbir!
On Tue, Jan 22, 2019 at 02:39:32PM +1300, Singh, Balbir wrote:
>
> On 1/19/19 5:39 AM, Torsten Duwe wrote:
> > + */
> > +ftrace_common_return:
> > + /* restore function args */
> > + ldp x0, x1, [sp]
> > + ldp x2, x3, [sp, #S_X2]
> > + ldp x4, x5, [sp, #S_X4]
> > +
On 22.01.19 12:22, Schrempf Frieder wrote:
> From: Frieder Schrempf
>
> Currently supported bad block marker positions within the block are:
> * in first page only
> * in last page only
> * in first or second page
>
> Some ESMT NANDs are known to have been shipped by the manufacturer
> with bad
801 - 900 of 1233 matches
Mail list logo
