Hi,
On 2/3/19 13:23, Chanwoo Choi wrote:
> 2019년 2월 2일 (토) 오전 2:42, Lukasz Luba 님이 작성:
>> +/**
>> + * exynos5_dmc_pause_on_switching() - Controls a pause feature in DMC
>> + * @dmc: device which is used for changing this feature
>> + * @set: a boolean state passing enable/disable
On Tue, Mar 5, 2019 at 8:12 PM Guenter Roeck wrote:
>
> On Tue, Feb 12, 2019 at 04:12:24PM -0600, Rob Herring wrote:
> > On Tue, Feb 12, 2019 at 3:50 PM Stephen Rothwell
> > wrote:
> > >
> > > Hi all,
> > >
> > > On Tue, 12 Feb 2019 10:03:09 -0600 Rob Herring wrote:
> > > >
> > > > On Mon, Feb
On Wed, Mar 6, 2019 at 2:13 PM Peter Zijlstra wrote:
>
> On Fri, Mar 01, 2019 at 04:23:05PM +0100, Peter Zijlstra wrote:
>
> > But yes, I'll try some annotation, see what that looks like.
>
> OK; that took a lot of time.. and a number of objtool bugs fixed but I
> think I have something that I
On Wed, Mar 6, 2019 at 1:29 PM Thomas Gleixner wrote:
> On Wed, 6 Mar 2019, Miroslav Lichvar wrote:
> > On Tue, Mar 05, 2019 at 05:42:25PM -0800, John Stultz wrote:
> So once Arnd is done with y2038, we'll ask him to look into y2262 :)
There is also y2070 (many RTCs), y2100 (some other RTCs,
[...]
> > > Btw, I saw that imx7d-sdb.dts (and probably other i.MX 7 boards too)
> > > use three different settings for usdhc pinctrl: 0x59, 0x5a and 0x5b
> > > (for default, 100MHz and 200MHz respectively). One would expect that
> > > higher frequency use higher driver strength (and this is the
On Mon, 4 Mar 2019 at 11:17, Ludovic Barre wrote:
>
> From: Ludovic Barre
>
> This patch defines get_dctrl_cfg callback for qcom variant.
> qcom variant has a specific block size definition.
>
> Signed-off-by: Ludovic Barre
> ---
> drivers/mmc/host/mmci_qcom_dml.c | 8
> 1 file
Commit-ID: 1e9b238bb4c1f22b5db77e9e17af0abd5578fa10
Gitweb: https://git.kernel.org/tip/1e9b238bb4c1f22b5db77e9e17af0abd5578fa10
Author: Kees Cook
AuthorDate: Wed, 27 Feb 2019 12:01:32 -0800
Committer: Thomas Gleixner
CommitDate: Wed, 6 Mar 2019 13:25:55 +0100
lkdtm: Check for SMEP
Commit-ID: d884bc119c4ebe7ac53b61fc0750bbc89b4d63db
Gitweb: https://git.kernel.org/tip/d884bc119c4ebe7ac53b61fc0750bbc89b4d63db
Author: Kees Cook
AuthorDate: Wed, 27 Feb 2019 12:01:30 -0800
Committer: Thomas Gleixner
CommitDate: Wed, 6 Mar 2019 13:25:55 +0100
x86/asm: Pin sensitive
On Mon, 4 Mar 2019 at 11:17, Ludovic Barre wrote:
>
> From: Ludovic Barre
>
> This patch defines get_dctrl_cfg callback for sdmmc variant.
> sdmmc variant has specific stm32 transfer modes.
> sdmmc data transfer mode selection could be:
> -Block data transfer ending on block count.
> -SDIO
Commit-ID: 3c8dbef26202a83207611b3d6f4d2db5e5cbbc0f
Gitweb: https://git.kernel.org/tip/3c8dbef26202a83207611b3d6f4d2db5e5cbbc0f
Author: Kees Cook
AuthorDate: Wed, 27 Feb 2019 12:01:31 -0800
Committer: Thomas Gleixner
CommitDate: Wed, 6 Mar 2019 13:25:55 +0100
x86/asm: Avoid taking an
Hello,
I wonder if it is "normal" to get panic() when the system is rebooted
using "reboot -f". I looks a bit weird to me.
In our case, the panic() was triggered from ext4 filesystem code
that was mounted with "errors=panic"
crash> bt
PID: 3984 TASK: 887db1f6c180 CPU: 32 COMMAND:
On 06/03/2019 12:00, Jon Hunter wrote:
>
> On 06/03/2019 11:31, Marc Zyngier wrote:
>> Hi Sameer,
>>
>> [unrelated to this email: anything that comes from NVIDIA reaches me
>> encrypted with my public key. Not a big deal, but it'd be good if
>> someone could fix that.]
>>
>> On 06/03/2019
Christian Kujau wrote:
> FS-Cache: Duplicate cookie detected
> FS-Cache: O-cookie c=9da9dbf0 [p=1593f904 fl=222 nc=0 na=1]
> FS-Cache: O-cookie d=287febd9 n=980c9e8a
> FS-Cache: O-key=[8] '020001bdc0a80064'
> FS-Cache: N-cookie c=bfe3f869
On Fri, Mar 01, 2019 at 04:23:05PM +0100, Peter Zijlstra wrote:
> But yes, I'll try some annotation, see what that looks like.
OK; that took a lot of time.. and a number of objtool bugs fixed but I
think I have something that I don't hate -- although it is not as solid
as I'd like it to be.
On 19-03-05 10:38:29, Stephen Boyd wrote:
> Quoting Abel Vesa (2019-03-05 01:49:16)
> > IMX8MQ_CLK_USB_PHY_REF changes from 163 to 153, this way removing the gap.
> > All the following clock ids are now decreased by 10 to keep the numbering
> > right. Doing this, the IMX8MQ_CLK_CSI2_CORE is not
On 2019/3/6 16:12, Peter Xu wrote:
> On Wed, Mar 06, 2019 at 03:41:06PM +0800, zhong jiang wrote:
>> On 2019/3/6 14:26, Mike Rapoport wrote:
>>> Hi,
>>>
>>> On Wed, Mar 06, 2019 at 01:53:12PM +0800, zhong jiang wrote:
On 2019/3/6 10:05, Andrea Arcangeli wrote:
> Hello everyone,
>
On Wed, Mar 06, 2019 at 06:15:25PM +0530, Aneesh Kumar K.V wrote:
> On 3/6/19 5:14 PM, Michal Suchánek wrote:
> > On Wed, 06 Mar 2019 14:47:33 +0530
> > "Aneesh Kumar K.V" wrote:
> >
> > > Dan Williams writes:
> > >
> > > > On Thu, Feb 28, 2019 at 1:40 AM Oliver wrote:
> > > > >
> > > > > On
On 2/03/19 7:20 AM, Sowjanya Komatineni wrote:
> This patch adds a quirk for setting CMD_TIMING to 1 in descriptor
> for DCMD with R1B response type to allow the command to be sent to
> device during data activity or busy time.
>
> Tegra186 CQHCI host has bug where it selects DATA_PRESENT_SELECT
When I ran Syzkaller testsuite, I got some UBSAN warnings with
ktime_sub().
Instead of putting overflow checks into each place, add a function
which does the sanity checking and convert all affected callers to use
it.
Hongbo Yao (2):
ktime: add ktime_sub_safe() to avoid undefined behaviour
I ran Syzkaller testsuite, and got the following call trace.
===
UBSAN: Undefined behaviour in ../kernel/time/hrtimer.c:514:11
signed integer overflow:
9223372036854775807 - -240652746 cannot be represented in type 'long
long int'
CPU: 1
This patch add a new ktime_sub_unsafe() helper which won't throw a
UBSAN warning when it does overflows, and then it add ktime_sub_safe()
which will check if the result of ktime_sub_unsafe overflows.This patch
modify the above functions to use ktime_sub_safe instead of ktime_sub();
Signed-off-by:
On Wed, Feb 27, 2019 at 10:14:56PM +0900, Masahiro Yamada wrote:
> On Fri, Feb 22, 2019 at 8:37 PM Sakari Ailus
> wrote:
> >
> > Hi Yamada-san,
> >
> > On Fri, Feb 22, 2019 at 01:36:03PM +0900, Masahiro Yamada wrote:
> > > On Thu, Feb 21, 2019 at 10:29 PM Sakari Ailus
> > > wrote:
> > > >
> > >
On Wed, Mar 6, 2019 at 8:38 PM Peter Zijlstra wrote:
>
> On Wed, Mar 06, 2019 at 07:49:36PM +0800, Yafang Shao wrote:
>
>
> $ grep SCHEDSTAT defconfig-build/.config
> # CONFIG_SCHEDSTATS is not set
> $ obbjdump -dr defconfig-build/kernel/sched/fair.o | awk '/>:$/ { F=$2 }
> /sched_stat/ { print
Em Mon, Mar 04, 2019 at 10:36:14PM +0800, Yang Wei escreveu:
> From: Yang Wei
>
> Delete a superfluous semicolon in getBPFObjectFromModule().
>
> Signed-off-by: Yang Wei
> ---
> tools/perf/util/c++/clang.cpp | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
Hi Mark,
On Wed, Mar 06, 2019 at 09:35:21AM +, Mark Rutland wrote:
> On Tue, Mar 05, 2019 at 05:31:12PM +, Russell King - ARM Linux admin
> wrote:
> > Guys,
>
> Hi Russell,
>
> > We need to be smarter when writing Kconfig help. I'm just going
> > through updating my build trees with
On 3/6/19 5:14 PM, Michal Suchánek wrote:
On Wed, 06 Mar 2019 14:47:33 +0530
"Aneesh Kumar K.V" wrote:
Dan Williams writes:
On Thu, Feb 28, 2019 at 1:40 AM Oliver wrote:
On Thu, Feb 28, 2019 at 7:35 PM Aneesh Kumar K.V
wrote:
Also even if the user decided to not use THP, by
echo
From: YueHaibing
Syzkaller report this:
BUG: KASAN: use-after-free in sysfs_remove_file_ns+0x5f/0x70 fs/sysfs/file.c:468
Read of size 8 at addr 8881f59a6b70 by task syz-executor.0/8363
CPU: 0 PID: 8363 Comm: syz-executor.0 Not tainted 5.0.0-rc8+ #3
Hardware name: QEMU Standard PC (i440FX +
On Wed, Mar 06, 2019 at 11:34:36AM +, Russell King - ARM Linux admin wrote:
> On Wed, Mar 06, 2019 at 12:49:40PM +0200, Andy Shevchenko wrote:
> > On Wed, Mar 6, 2019 at 11:52 AM Russell King - ARM Linux admin
> > wrote:
> > > On Wed, Mar 06, 2019 at 10:45:52AM +0100, Lucas Stach wrote:
> > >
On Wed, Mar 06, 2019 at 07:49:36PM +0800, Yafang Shao wrote:
$ grep SCHEDSTAT defconfig-build/.config
# CONFIG_SCHEDSTATS is not set
$ obbjdump -dr defconfig-build/kernel/sched/fair.o | awk '/>:$/ { F=$2 }
/sched_stat/ { print F " " $0 }'
: 24cd: R_X86_64_32S
On 01. 03. 19 10:37, Rajan Vaja wrote:
> Existing driver checks for alternate clock if devm_clk_get() fails
> and returns error code for last clock failure. If xilinx_uartps is
> called before clock driver, devm_clk_get() returns -EPROBE_DEFER.
> In this case, probe should not check for alternate
On Wed, 6 Mar 2019, Miroslav Lichvar wrote:
> On Tue, Mar 05, 2019 at 05:42:25PM -0800, John Stultz wrote:
> > > --- a/kernel/time/ntp.c
> > > +++ b/kernel/time/ntp.c
> > > @@ -677,6 +677,8 @@ static inline void process_adjtimex_modes(const
> > > struct timex *txc, s32 *time_tai
> > >
> > >
On Mon, Mar 4, 2019 at 1:15 AM Joel Fernandes wrote:
>
> This report is for an older version of the patch so ignore it. The
> issue is already resolved.
>
> On Sat, Mar 2, 2019 at 2:00 PM kbuild test robot wrote:
> >
> > Hi Joel,
> >
> > Thank you for the patch! Yet something to improve:
> >
> >
On Tue, 5 Mar 2019, Matthew Wilcox wrote:
> On Tue, Mar 05, 2019 at 10:19:04AM +0100, Borislav Petkov wrote:
> > On Sat, Mar 02, 2019 at 12:57:30AM +0100, Jann Horn wrote:
> > > In theory, Linux can dump cores for a.out binaries. In practice, that
> > > code is pretty bitrotten and buggy. Does
Le 3/6/19 à 12:08 AM, Joe Perches a écrit :
On Tue, 2019-03-05 at 13:02 -0500, Alexandre Ghiti wrote:
This patch ensures that apart from net code, block comments start with an
empty /* line.
I'm not sure it's useful to try to eliminate these types
of lines as there are ~20K of them in the
On Wed, 30 Jan 2019, Vlastimil Babka wrote:
> I've collected the patches from the discussion for formal posting. The first
> two should be settled already, third one is the possible improvement I've
> mentioned earlier, where only in restricted case we resort to existence of
> page
> table
On 1/03/19 10:38 AM, Faiz Abbas wrote:
> commit 5b0d62108b46 ("mmc: sdhci-omap: Add platform specific reset
> callback") skips data resets during tuning operation. Because of this,
> a data error or data finish interrupt might still arrive after a command
> error has been handled and the mrq
On Wed, Mar 06, 2019 at 03:25:11PM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit 2264f5132fe45571139727ebdeb78696b35d1506
>
(VFIO) is untrusted, ok. But a malicious driver loaded into the kernel
address space would have much easier ways to corrupt the system than to
exploit lazy mode...
Yes, so that we have no need to consider untrusted drivers.
For (3), I agree that we should at least disallow lazy mode if
On 06/03/2019 09:38, Auger Eric wrote:
>>> +struct iommu_fault_unrecoverable {
>>> + __u32 reason; /* enum iommu_fault_reason */
>>> +#define IOMMU_FAULT_UNRECOV_PASID_VALID (1 << 0)
>>> +#define IOMMU_FAULT_UNRECOV_PERM_VALID (1 << 1)
>>
>> Not needed, since @perm
On Wed, Mar 06, 2019 at 06:43:48PM +0800, Xin Long wrote:
> On Wed, Mar 6, 2019 at 9:42 AM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:63bdf4284c38 Merge branch 'linus' of git://git.kernel.org/..
> > git tree: upstream
> > console
On Tue, Mar 5, 2019 at 1:33 PM Wen Yang wrote:
>
> The call to of_get_next_child returns a node pointer with refcount
> incremented thus it must be explicitly decremented after the last
> usage.
>
> Detected by coccinelle with the following warnings:
> ./arch/arm/mach-npcm/platsmp.c:52:1-7:
Currently, common/platform.c registers the Loongson 2F cpufreq driver
during boot time for all boards. To support platform drivers for Lemote
Yeeloong laptops, we need to register more drivers.
First, we add support for per-board platform drivers. Just like how IRQ,
DMA, or reset logic is
The hardware design of Yeeloong laptops is similar to OLPC: low-level
hardware events are processed by the ENE KB3310B Embedded Controller,
which is connected to the AMD CS5536 southbridge through a GPIO port.
When a hardware event occurs, such as a short-circuit on the USB port,
removing the
I've introduced platform code for Lemote Yeeloong computers and modified
power management-related files. Add myself as a maintainer of these code.
Signed-off-by: Yifeng Li
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index
To ease the support of platform drivers on Lemote Yeeloong laptop,
code for accessing the embedded controller has been separated from
arch/mips, as a MFD driver. Since the board files here still need
to access the EC directly to handle reboot/shutdown and interrupts,
we make MFD_YEELOONG_KB3310B
There is some complicated logic in lemote-2f/pm.c. During wakeup, it
creates a delayed_work to execute a callback to the function
yeeloong_report_lid_status(). It's only purpose is to report the current
status of the laptop lid switch, and this callback function was not
implemented in the mainline
We have already converted the supporting code for ENE KB3310B
embedded controller as a separate MFD driver, and select it
as a dependency of LEMOTE_MACH2F.
This commit removes the original implementation of ec_kb3310b.c,
and converts all EC operations to use the utility function provided
by the
v3:
- Style fixes: remove asterisks banners from code comments, use
pr_fmt() to format driver messages, remove newlines in mfd_cells
retries, fix copyright years.
- Define DEFINE_SPINLOCK(kb3310b_command_lock) as a static variable
within kb3310b_query_seq().
- Reword misleading notes
Lemote Yeeloong is a laptop powered by Loongson 2F MIPS processor,
primarily a demo platform for hobbyists and developers. It uses an
ENE KB3310B Embedded Controller with customized firmware to implement
hardware and power management.
A monolithic platform driver code for those functionality has
On 06/03/2019 11:31, Marc Zyngier wrote:
> Hi Sameer,
>
> [unrelated to this email: anything that comes from NVIDIA reaches me
> encrypted with my public key. Not a big deal, but it'd be good if
> someone could fix that.]
>
> On 06/03/2019 10:41, Sameer Pujar wrote:
>> With pm_clk_*() usage,
From: YueHaibing
Syzkaller report this:
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1] SMP KASAN PTI
CPU: 0 PID: 4492 Comm: syz-executor.0 Not tainted 5.0.0-rc7+ #45
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
Assalamu Alaikum Wa Rahmatullahi Wa Barakatuh,
hello dear
I came across your contact during my private search. Mrs Aisha Al-
Qaddafi is my name, the only daughter of late Libyan president, am a
single Mother and a Widow with three Children.I have funds the sum of
$27.5 million USD for,
On Wed, Mar 6, 2019 at 7:27 PM Peter Zijlstra wrote:
>
> On Wed, Mar 06, 2019 at 06:15:39PM +0800, Yafang Shao wrote:
> > On Wed, Mar 6, 2019 at 6:09 PM Peter Zijlstra wrote:
> > >
> > > On Wed, Mar 06, 2019 at 04:43:46PM +0800, Yafang Shao wrote:
> > > > When I'm using trace_sched_stat_{iowait,
To support USB3 Gen2 ISOC, the registers of TXCSR1 and RXCSR1
are adjusted to support greater maxpkt and mult value, this
patch fix this issue
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3.h | 11 ++
drivers/usb/mtu3/mtu3_core.c| 14 +++--
In order to help debug, this series add more debugfs consumers,
introduce a few initial tracepoints;
And support new features introduced by USB3 Gen2 ISOC:
1. TXCSR/RXCSR registers are adjusted to support greater MULT
and MAX_PKT
2. QMU format is also improved
last, some small problems are
Print useful information not only dual-role mode but also
device mode and host mode.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_plat.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/mtu3/mtu3_plat.c b/drivers/usb/mtu3/mtu3_plat.c
index
From: YueHaibing
Use remove_proc_subtree to remove the whole subtree
Signed-off-by: YueHaibing
---
drivers/net/wireless/ray_cs.c | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/drivers/net/wireless/ray_cs.c b/drivers/net/wireless/ray_cs.c
index d561659..ee4d810 100644
In order to support U3gen2 ISOC transfer upto 96DPs, extend
the data buffer length.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3.h | 11 +++---
drivers/usb/mtu3/mtu3_core.c| 5 +++
drivers/usb/mtu3/mtu3_gadget.c | 6 ++--
drivers/usb/mtu3/mtu3_hw_regs.h | 1 +
This patch implements a few initial tracepoints for the
mtu3 driver. More traces can be added as necessary in order
to ease the task of debugging.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/Makefile | 7 +
drivers/usb/mtu3/mtu3_core.c | 5 +
By introducing mailbox_state_string(), allow to make debug
log more readable
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_dr.c | 20 ++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/mtu3/mtu3_dr.c b/drivers/usb/mtu3/mtu3_dr.c
index
Check the return value of devm_extcon_register_notifier() and
add error handling.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_dr.c | 13 +
drivers/usb/mtu3/mtu3_plat.c | 8 +++-
2 files changed, 16 insertions(+), 5 deletions(-)
diff --git
Remove local variable @vbus and use @dev instead of @pdev->dev
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_plat.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/mtu3/mtu3_plat.c b/drivers/usb/mtu3/mtu3_plat.c
index 3a4a80f15957..a326b1d6006a
The local variable @req is unnecessary in qmu_tx_zlp_error_handler,
so remove it.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_qmu.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/mtu3/mtu3_qmu.c b/drivers/usb/mtu3/mtu3_qmu.c
index
Due to the separated debugfs files are added, move vbus and mode
debugfs interfaces related with dual-role switch from mtu3_dr.c
into mtu3_debugfs.c
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_debug.h | 2 +
drivers/usb/mtu3/mtu3_debugfs.c | 101
To support USB3 Gen2 ISOC, the data buffer length need be extended,
it's hard to make the current qmu_gpd struct compatible, so here
rebuild qmu_gpd struct and make easy to support new QMU format
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3.h | 45 +++--
This adds more debugfs consumers. The debugfs entries read some
important registers, fifo status, QMU ring, endpoint status, and
IPPC probe interface to get internal status.
With these entries, users can check the registers, endpoint and
GPD used during run time.
Signed-off-by: Chunfeng Yun
---
From: YueHaibing
init_ray_cs does not check value of pcmcia_register_driver,
if it fails, there maybe cause a NULL pointer dereference in
exit_ray_cs.
Signed-off-by: YueHaibing
---
drivers/net/wireless/ray_cs.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Wed, 06 Mar 2019 14:47:33 +0530
"Aneesh Kumar K.V" wrote:
> Dan Williams writes:
>
> > On Thu, Feb 28, 2019 at 1:40 AM Oliver wrote:
> >>
> >> On Thu, Feb 28, 2019 at 7:35 PM Aneesh Kumar K.V
> >> wrote:
> Also even if the user decided to not use THP, by
> echo "never" >
On Fri 01-03-19 17:08:14, Qian Cai wrote:
> When onlining a memory block with DEBUG_PAGEALLOC, it unmaps the pages
> in the block from kernel, However, it does not map those pages while
> offlining at the beginning. As the result, it triggers a panic below
> while onlining on ppc64le as it checks
On machines where the GART aperture is mapped over physical RAM,
/proc/kcore contains the GART aperture range and reading it may lead
to kernel panic.
Vmcore used to have the same issue, until we fixed it in
commit 2a3e83c6f96c ("x86/gart: Exclude GART aperture from vmcore")',
leveraging existing
>
> Without CONFIG_OF, the of_match_node() helper does not evaluate
> its argument, and the compiler warns about the unused variable:
>
> drivers/scsi/ufs/ufs-hisi.c: In function 'ufs_hisi_probe':
> drivers/scsi/ufs/ufs-hisi.c:673:17: error: unused variable 'dev' [-
> Werror=unused-variable]
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/asm
head: a0bf7fc24303a538396aa8d32450d05c1929b9f0
commit: d309ba034fac1a149d00cac79318973e9ba81848 [2/4] x86/asm: Pin sensitive
CR0 bits
config: um-x86_64_defconfig (attached as .config)
compiler: gcc-8 (Debian 8.3.0-2)
On Tue, 5 Mar 2019, Andy Shevchenko wrote:
CC+ PeterZ
> I have an Intel Merrifield platform where from time to time (don't
> know how to reproduce reliably) I have got a warning on reboot.
>
> Requesting system reboot
> [ 64.945973] reboot: Restarting system
> [ 64.950770] reboot: machine
On Wed, Mar 06, 2019 at 04:33:08PM +0900, Myungho Jung wrote:
> In esp4_gro_receive() and esp6_gro_receive(), secpath can be allocated
> without adding xfrm state to xvec. Then, sp->xvec[sp->len - 1] would
> fail and result in dereferencing invalid pointer in esp4_gso_segment()
> and
On Wed, Mar 06, 2019 at 12:49:40PM +0200, Andy Shevchenko wrote:
> On Wed, Mar 6, 2019 at 11:52 AM Russell King - ARM Linux admin
> wrote:
> > On Wed, Mar 06, 2019 at 10:45:52AM +0100, Lucas Stach wrote:
> > > Am Dienstag, den 05.03.2019, 17:31 + schrieb Russell King - ARM Linux
> > > admin:
On Mon, Mar 04, 2019 at 08:19:14PM -0500, Su Yanjun wrote:
> For rcu protected pointers, we'd better add '__rcu' for them.
>
> Once added '__rcu' tag for rcu protected pointer, the sparse tool reports
> warnings.
>
> net/xfrm/xfrm_user.c:1198:39: sparse:expected struct sock *sk
>
Hi Sameer,
[unrelated to this email: anything that comes from NVIDIA reaches me
encrypted with my public key. Not a big deal, but it'd be good if
someone could fix that.]
On 06/03/2019 10:41, Sameer Pujar wrote:
> With pm_clk_*() usage, it is seen that clocks always remain ON. This
> happens
On Wed, Mar 06, 2019 at 06:15:39PM +0800, Yafang Shao wrote:
> On Wed, Mar 6, 2019 at 6:09 PM Peter Zijlstra wrote:
> >
> > On Wed, Mar 06, 2019 at 04:43:46PM +0800, Yafang Shao wrote:
> > > When I'm using trace_sched_stat_{iowait, blocked, wait, sleep} to
> > > measure how long the processes are
After commit 68bb7bfb7985 ("X86/Hyper-V: Enable IPI enlightenments"),
kexec will fail with a kernel panic like this:
kexec_core: Starting new kernel
BUG: unable to handle kernel NULL pointer dereference at
PGD 800057995067 P4D 800057995067 PUD 57990067 PMD 0
Oops: 0002
> Do you have any other questions?
I would like to point another aspect out for further development considerations.
The initial assignment targets are (id)expressions in the discussed analysis
approach so far.
Would you like to care also for value (or pointer) initialisations by resource
Hi Jonathan,
On 3/3/19 17:47, Jonathan Cameron wrote:
> On Fri, 22 Feb 2019 11:24:24 +0100
> Enric Balletbo i Serra wrote:
>
>> Hi Jonathan,
>>
>> On 20/2/19 17:01, Jonathan Cameron wrote:
>>> On Wed, 20 Feb 2019 16:03:00 +0100
>>> Enric Balletbo i Serra wrote:
>>>
From: Gwendal
This adds documentation for the specific prescaler entry.
Signed-off-by: Patrick Havelange
---
Changes v2
- Add doc for prescaler entry
---
.../ABI/testing/sysfs-bus-counter-ftm-quaddec| 16
1 file changed, 16 insertions(+)
create mode 100644
This also fixes the wrong value for the previously defined
FTM_MODE_INIT macro (it was not used).
Signed-off-by: Patrick Havelange
Reviewed-by: Esben Haabendal
---
Changes v2
- None
---
drivers/pwm/pwm-fsl-ftm.c | 44 +--
1 file changed, 1 insertion(+),
Several files are/will be using the same #defines to use the Flextimer
module. Regroup them in a common file.
Signed-off-by: Patrick Havelange
Reviewed-by: Esben Haabendal
---
Changes v2
- Commit message
---
include/linux/fsl/ftm.h | 88 +
1 file
Common #defines have been moved to "linux/fsl/ftm.h". Thus making use of
this file.
Also FTM_SC_CLK_SHIFT has been renamed to FTM_SC_CLK_MASK_SHIFT.
Signed-off-by: Patrick Havelange
Reviewed-by: Esben Haabendal
---
Changes v2
- None
---
drivers/clocksource/timer-fsl-ftm.c | 15
This patch serie is to be applied on top of
https://patchwork.kernel.org/project/linux-iio/list/?series=147
(a more recent version of the serie is available here :
https://gitlab.com/vilhelmgray/iio/tree/generic_counter_v10 )
Main changes in v2:
The code is a bit simpler, thanks to more use of
This driver exposes the counter for the quadrature decoder of the
FlexTimer Module, present in the LS1021A soc.
Signed-off-by: Patrick Havelange
---
Changes v2
- Rebased on new counter subsystem
- Cleaned up included headers
- Use devm_ioremap()
- Correct order of devm_ and unmanaged
Add the 4 Quadrature counters for this board.
Signed-off-by: Patrick Havelange
Reviewed-by: Esben Haabendal
---
Changes v2
- None
---
arch/arm/boot/dts/ls1021a.dtsi | 28
1 file changed, 28 insertions(+)
diff --git a/arch/arm/boot/dts/ls1021a.dtsi
FlexTimer quadrature decoder driver.
Signed-off-by: Patrick Havelange
Reviewed-by: Esben Haabendal
---
Changes v2
- None
---
.../bindings/counter/ftm-quaddec.txt | 18 ++
1 file changed, 18 insertions(+)
create mode 100644
The PTN5150 dependencies look like they were meant to do the
right thing, but they actually should not allow building without
I2C for compile testing, as that results in a Kconfig warning
and subsequent build failure:
WARNING: unmet direct dependencies detected for REGMAP_I2C
Depends on [m]:
Hi Steve,
On 04/03/2019 23:15, Steven Rostedt wrote:
On Mon, 4 Mar 2019 22:25:41 +
Julien Grall wrote:
On 04/03/2019 22:01, Sebastian Andrzej Siewior wrote:
On 2019-03-04 17:21:57 [+], Julien Grall wrote:
(CC correctly linux-rt-users)
On 04/03/2019 17:20, Julien Grall wrote:
At
Trying to log in on the serial console causes the system to freeze. The
last message is:
[ 115.597858] sifive-serial 1001.serial: BRKINT/PARMRK flag not supported
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA
On 2019/3/4 23:52, Robin Murphy wrote:
> On 02/03/2019 06:12, Leizhen (ThunderTown) wrote:
>>
>>
>> On 2019/3/1 19:07, Jean-Philippe Brucker wrote:
>>> Hi Leizhen,
>>>
>>> On 01/03/2019 04:44, Leizhen (ThunderTown) wrote:
On 2019/2/26 20:36, Hanjun Guo wrote:
> Hi Jean,
>
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses
On some architectures, the MMU can be disabled, leading to access_ok()
becoming an empty macro that does not evaluate its size argument,
which in turn produces an unused-variable warning:
drivers/vhost/vhost.c:1191:9: error: unused variable 's'
[-Werror,-Wunused-variable]
size_t s =
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses
atomic_t variables are currently used to implement reference
counters with the following properties:
- counter is initialized to 1 using atomic_set()
- a resource is freed upon counter reaching zero
- once counter reaches zero, its further
increments aren't allowed
- counter schema uses
I would like to reopen ages-old discussion on these conversions now.
Eric had objections against them in past, namely on not providing enough
security for reference counters (but we still argue it is better
than overflowing atomic_t and resulting use-after-free).
However now, refcount_t has been
Hi Jean,
On 3/5/19 3:56 PM, Jean-Philippe Brucker wrote:
> On 18/02/2019 13:54, Eric Auger wrote:
>> From: Jacob Pan
>>
>> Device faults detected by IOMMU can be reported outside the IOMMU
>> subsystem for further processing. This patch introduces
>> a generic device fault data structure.
>>
>>
On 05-03-19, 11:23, Rafael J. Wysocki wrote:
> Hi All,
>
> This is a follow-up to the RFT patch set posted previously:
> https://lore.kernel.org/lkml/9956076.f4luudm...@aspire.rjw.lan/
>
> Patch [1/3] causes intel_pstate to update all policies if it gets a _PPC
> change
> notification and sees
701 - 800 of 943 matches
Mail list logo
