This patch implements CONFIG_DEBUG_VIRTUAL to warn about
incorrect use of virt_to_phys() and page_to_phys()
It also warns about DMA on stack when CONFIG_HAVE_ARCH_VMAP_STACK is
selected. It will help locate them before activating CONFIG_VMAP_STACK
Below is the result of test_debug_virtual:
[
Hi Sakari,
thanks for digging this out
On Mon, Dec 10, 2018 at 01:39:17AM +0200, sakari.ai...@iki.fi wrote:
> Hi Jacopo,
>
> On Fri, Dec 29, 2017 at 01:22:26PM +0100, Jacopo Mondi wrote:
> > The following commits:
> > commit f6dd927f34d6 ("[media] media: ov7670: calculate framerate properly
>
On Mon, Dec 10, 2018 at 12:00 PM Pingfan Liu wrote:
>
> On Fri, Dec 7, 2018 at 11:56 PM Michal Hocko wrote:
> >
> > On Fri 07-12-18 22:27:13, Pingfan Liu wrote:
> > [...]
> > > diff --git a/arch/x86/mm/numa.c b/arch/x86/mm/numa.c
> > > index 1308f54..4dc497d 100644
> > > --- a/arch/x86/mm/numa.c
On 12/9/2018 9:32 PM, Mimi Zohar wrote:
On Fri, 2018-12-07 at 15:51 +0100, Roberto Sassu wrote:
On 12/6/2018 8:49 PM, Mimi Zohar wrote:
PCRs for sha1 and sha256 algorithms are being updated and the
measurement list verifies against the SHA1 PCR-10.
Roberto, have you added support in
Hello,
syzbot found the following crash on:
HEAD commit:83af01ba1c2d Merge branch 'tc-testing-next'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=15562a4340
kernel config: https://syzkaller.appspot.com/x/.config?x=28ecefa8a6e10719
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:83af01ba1c2d Merge branch 'tc-testing-next'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=119cd8b340
kernel config: https://syzkaller.appspot.com/x/.config?x=28ecefa8a6e10719
dashboard link:
Hello,
syzbot found the following crash on:
HEAD commit:a60956ed72f7 net: dsa: Make dsa_master_set_mtu() static
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17d2f3f540
kernel config: https://syzkaller.appspot.com/x/.config?x=28ecefa8a6e10719
prepare_bprm_creds is not used outside exec.c, so there's no reason for it
to have external linkage.
Signed-off-by: Chanho Min
---
fs/exec.c | 2 +-
include/linux/binfmts.h | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/fs/exec.c b/fs/exec.c
index
Hello,
syzbot found the following crash on:
HEAD commit:74c4a24df7ca Add linux-next specific files for 20181207
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17dbb3d540
kernel config: https://syzkaller.appspot.com/x/.config?x=6e9413388bf37bed
Loop RT kernel Mailing lists.
On 2018/12/10 1:04, zhang jianwei wrote:
> hi Thomas and Mike??
> i say you disabled the RT_GROUP_SCHED in RT kernel because of strange cpu
> stall was observed. currently, in my projects, I need
> enable?0?2RT_GROUP_SCHED in RT kernel. I??d like to know how to
Hello,
syzbot found the following crash on:
HEAD commit:74c4a24df7ca Add linux-next specific files for 20181207
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17bbea7d40
kernel config: https://syzkaller.appspot.com/x/.config?x=6e9413388bf37bed
Hello,
syzbot found the following crash on:
HEAD commit:74c4a24df7ca Add linux-next specific files for 20181207
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=171e912540
kernel config: https://syzkaller.appspot.com/x/.config?x=6e9413388bf37bed
On Sun, Dec 09, 2018 at 09:06:00PM +0100, Pavel Machek wrote:
...
> > > > The default permissions for the device are 600.
> > >
> > > Good. This does not belong to non-root.
> >
> > There are entirely legitimate use cases for using this as an
> > unprivileged user. However, that'll be up to
On Mon, Dec 10, 2018 at 03:27:59PM +0800, YueHaibing wrote:
> Remove duplicated include.
>
> Signed-off-by: YueHaibing
> ---
> drivers/infiniband/hw/mlx5/mlx5_ib.h | 1 -
> 1 file changed, 1 deletion(-)
>
Thanks,
Acked-by: Leon Romanovsky
signature.asc
Description: PGP signature
Hi,
> Am 09.12.2018 um 20:51 schrieb Andreas Kemnade :
>
> Devices might have a separate lna between antenna output of the gps
some nitpicking: the LNA (low noise amplifier) is between the antenna
and the GPS receiver. Therefore:
s/between antenna output of the gps/between antenna input of the
On Fri, Dec 07, 2018 at 11:24:27AM -0600, Rob Herring wrote:
> On Wed, Nov 28, 2018 at 02:59:50PM +0300, Heikki Krogerus wrote:
> > This helper returns the name of the node. The name is
> > primarily expected to be returned from a new fwnode
> > operation meant for this purpose, but when no name
From: Owen Chen
PLLs with tuner_en bit, such as APLL1, need to disable
tuner_en before apply new frequency settings, or the new frequency
settings (pcw) will not be applied.
The tuner_en bit will be disabled during changing PLL rate
and be restored after new settings applied.
Another minor
From: Owen Chen
1. pcwibits: The integer bits of pcw for plls is extend to 8 bits,
add a variable to indicate this change and
backward-compatible.
2. fmin: The pll freqency lower-bound is vary from 1GMhz to
1.5Ghz, add a variable to indicate platform-dependent.
Signed-off-by: Owen Chen
On some Mediatek platforms, there are critical clocks of
clock gate type.
To register clock gate with flags CLK_IS_CRITICAL,
we need to add the flags field in mtk_gate data and register APIs.
Signed-off-by: Weiyi Lu
---
drivers/clk/mediatek/clk-gate.c | 5 +++--
drivers/clk/mediatek/clk-gate.h
Add scpsys driver for MT8183
Signed-off-by: Weiyi Lu
---
drivers/soc/mediatek/mtk-scpsys.c | 226 ++
1 file changed, 226 insertions(+)
diff --git a/drivers/soc/mediatek/mtk-scpsys.c
b/drivers/soc/mediatek/mtk-scpsys.c
index 98ccef566ce1..58d84fe33d2a 100644
---
From: James Liao
Some modules may need to change its clock rate before turn on it.
So changing PLL's rate when it is off should be allowed.
This patch removes PLL enabled check before set rate, so that
PLLs can set new frequency even if they are off.
On MT8173 for example, ARMPLL's enable bit
Add MT8183 clock dt-bindings, include topckgen, apmixedsys,
infracfg, mcucfg and subsystem clocks.
Signed-off-by: Weiyi Lu
Reviewed-by: Rob Herring
---
include/dt-bindings/clock/mt8183-clk.h | 422 +
1 file changed, 422 insertions(+)
create mode 100644
From: Owen Chen
On both MT8183 & MT6765, there add "set/clr" register for
each clkmux setting, and one update register to trigger value change.
It is designed to prevent read-modify-write racing issue.
The sw design need to add a new API to handle this hw change with
a new mtk_clk_mux/mtk_mux
Add MT8183 clock support, include topckgen, apmixedsys,
infracfg, mcucfg and subsystem clocks.
Signed-off-by: Weiyi Lu
---
drivers/clk/mediatek/Kconfig | 75 ++
drivers/clk/mediatek/Makefile | 12 +
drivers/clk/mediatek/clk-gate.h| 14 +
This series is based on v4.20-rc1 and most of changes are extracted from series
below
(clock/scpsys common changes for both MT8183 & MT6765)
https://patchwork.kernel.org/patch/10528495/
(clock support of MT8183)
https://patchwork.kernel.org/patch/10549891/
The whole series is composed of
clock
From: Owen Chen
Both MT8183 & MT6765 add more bus protect node than previous project,
therefore we add two more register for setup bus protect, which reside
at INFRA_CFG & SMI_COMMON.
With the following change
1. bus protect need not only infracfg but smi_common registers involved
to setup.
This patch adds the binding documentation for apmixedsys, audiosys,
camsys, imgsys, infracfg, mcucfg, mfgcfg, mmsys, topckgen, vdecsys,
vencsys and ipu for Mediatek MT8183.
Signed-off-by: Weiyi Lu
Reviewed-by: Rob Herring
---
.../arm/mediatek/mediatek,apmixedsys.txt | 1 +
fix incorrect IC name that will affect the MT8183 power dt-bindings
Signed-off-by: Weiyi Lu
---
include/dt-bindings/power/mt8173-power.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/dt-bindings/power/mt8173-power.h
b/include/dt-bindings/power/mt8173-power.h
Add power dt-bindings for MT8183.
Signed-off-by: Weiyi Lu
---
.../bindings/soc/mediatek/scpsys.txt | 14 ++
include/dt-bindings/power/mt8183-power.h | 26 +++
2 files changed, 40 insertions(+)
create mode 100644 include/dt-bindings/power/mt8183-power.h
This series is based on v4.20-rc1 and most of changes are extracted from series
below
(clock/scpsys common changes for both MT8183 & MT6765)
https://patchwork.kernel.org/patch/10528495/
(clock support of MT8183)
https://patchwork.kernel.org/patch/10549891/
The whole series is composed of
clock
Remove duplicated include.
Signed-off-by: YueHaibing
---
drivers/infiniband/hw/mlx5/mlx5_ib.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/infiniband/hw/mlx5/mlx5_ib.h
b/drivers/infiniband/hw/mlx5/mlx5_ib.h
index 484a080..64fbf45 100644
--- a/drivers/infiniband/hw/mlx5/mlx5_ib.h
On Fri, Dec 07, 2018 at 04:34:32PM +0100, Christoph Hellwig wrote:
> Hi all,
>
> the ARM imx27/31 ports and various sh boards use
> dma_declare_coherent_memory on main memory taken from the memblock
> allocator.
>
> Is there any good reason these couldn't be switched to CMA areas?
> Getting rid
The accelerometer's power supply could be controlled by regulator
on some platforms, add optional property "vdd/vddio" power supply
to let device tree to pass phandles to the regulators to driver.
Signed-off-by: Anson Huang
---
Documentation/devicetree/bindings/iio/accel/mma8452.txt | 4
1
Remove duplicated include.
Signed-off-by: YueHaibing
---
drivers/bus/qcom-ebi2.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/bus/qcom-ebi2.c b/drivers/bus/qcom-ebi2.c
index a644424..56b01e4 100644
--- a/drivers/bus/qcom-ebi2.c
+++ b/drivers/bus/qcom-ebi2.c
@@ -21,7 +21,6 @@
The accelerometer's power supply could be controlled by regulator
on some platforms, such as i.MX6Q-SABRESD board, the mma8451's
power supply is controlled by a GPIO fixed regulator, need to make
sure the regulator is enabled before any communication with mma8451,
this patch adds optional
Some stack pointers used to also be thread_info pointers
and were called tp. Now that they are only stack pointers,
rename them sp.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/irq.c | 17 +++--
arch/powerpc/kernel/setup_64.c | 20 ++--
2 files
thread_info is not anymore in the stack, so the entire stack
can now be used.
There is also no risk anymore of corrupting task_cpu(p) with a
stack overflow so the patch removes the test.
When doing this, an explicit test for NULL stack pointer is
needed in validate_sp() as it is not anymore
When moving to CONFIG_THREAD_INFO_IN_TASK, the thread_info 'cpu' field
gets moved into task_struct and only defined when CONFIG_SMP is set.
This patch ensures that TI_CPU is only used when CONFIG_SMP is set and
that task_struct 'cpu' field is not used directly out of SMP code.
Signed-off-by:
Now that current_thread_info is located at the beginning of 'current'
task struct, CURRENT_THREAD_INFO macro is not really needed any more.
This patch replaces it by loads of the value at PACACURRENT(r13).
Signed-off-by: Christophe Leroy
---
arch/powerpc/include/asm/exception-64s.h | 4
This patch activates CONFIG_THREAD_INFO_IN_TASK which
moves the thread_info into task_struct.
Moving thread_info into task_struct has the following advantages:
- It protects thread_info from corruption in the case of stack
overflows.
- Its address is harder to determine if stack addresses are
This patch cleans the powerpc kernel before activating
CONFIG_THREAD_INFO_IN_TASK:
- The purpose of the pointer given to call_do_softirq() and
call_do_irq() is to point the new stack ==> change it to void* and
rename it 'sp'
- Don't use CURRENT_THREAD_INFO() to locate the stack.
- Fix a few
The table of pointers 'current_set' has been used for retrieving
the stack and current. They used to be thread_info pointers as
they were pointing to the stack and current was taken from the
'task' field of the thread_info.
Now, the pointers of 'current_set' table are now both pointers
to
The purpose of this serie is to activate CONFIG_THREAD_INFO_IN_TASK which
moves the thread_info into task_struct.
Moving thread_info into task_struct has the following advantages:
- It protects thread_info from corruption in the case of stack
overflows.
- Its address is harder to determine if
When activating CONFIG_THREAD_INFO_IN_TASK, linux/sched.h
includes asm/current.h. This generates a circular dependency.
To avoid that, asm/processor.h shall not be included in mmu-hash.h
In order to do that, this patch moves into a new header called
asm/task_size_user64.h the information from
Now that thread_info is similar to task_struct, it's address is in r2
so CURRENT_THREAD_INFO() macro is useless. This patch removes it.
At the same time, as the 'cpu' field is not anymore in thread_info,
this patch renames it to TASK_CPU.
Signed-off-by: Christophe Leroy
---
The magnetometer's power supply could be controlled by regulator
on some platforms, such as i.MX6Q-SABRESD board, the mag3110's
power supply is controlled by a GPIO fixed regulator, need to make
sure the regulator is enabled before any communication with mag3110,
this patch adds optional vdd/vddio
On 2018/12/10 14:15, Lee Jones wrote:
> On Sun, 09 Dec 2018, YueHaibing wrote:
>
>> Remove duplicated include.
>>
>> Signed-off-by: YueHaibing
>> ---
>> drivers/input/keyboard/mtk-pmic-keys.c | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/drivers/input/keyboard/mtk-pmic-keys.c
>>
The light sensor's power supply could be controlled by regulator
on some platforms, such as i.MX6Q-SABRESD board, the light sensor
isl29023's power supply is controlled by a GPIO fixed regulator,
need to make sure the regulator is enabled before any operation of
sensor, this patch adds optional
According to datasheet, the isl29018 has "vddd/vdda" power
supply, and isl29023/isl29035 ONLY has "vdd" power supply,
update the power supply name with "vdd" and "vdda" according
to datasheet to cover all devices and avoid confusion.
Signed-off-by: Anson Huang
---
Hi all,
On Mon, 10 Dec 2018 17:17:16 +1100 Stephen Rothwell
wrote:
>
> I fixed it up (see below) and can carry the fix as necessary. This
See below :-)
Also I accidentally left the declaration of "status" in
__qla2x00_abort_all_cmds().
--
Cheers,
Stephen Rothwell
diff --cc
On Mon, 10 Dec 2018, Oskari Lemmelä wrote:
> On 10.12.2018 8.36, Lee Jones wrote:
> > On Sat, 08 Dec 2018, Oskari Lemmela wrote:
> >
> >> From: Chen-Yu Tsai
> >>
> >> In the axp20x driver, the various mfd_cell lists had varying amounts
> >> of indentation, sometimes even within the same list. For
On Mon, 10 Dec 2018, Chen-Yu Tsai wrote:
> On Mon, Dec 10, 2018 at 2:35 PM Lee Jones wrote:
> >
> > On Sat, 08 Dec 2018, Oskari Lemmela wrote:
> >
> > > Parts of the AXP803 are compatible with their counterparts on the AXP813.
> > > These include the GPIO, ADC, AC and battery power supplies.
> >
Hi Linus,
After merging the gpio tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "irq_chip_retrigger_hierarchy" [drivers/gpio/gpio-lpc18xx.ko] undefined!
Caused by commit
5ddabfe8d3de ("gpio: lpc18xx: add GPIO pin interrupt controller support")
I have used the
Hi,
We have start the test with the CONFIG_PROVE_RCU=y, and also add one 2s to
detect the preempt rcu hang, hope we can get more useful logs tomorrow.
I also enclosed the config and the debug patches for you review.
-Original Message-
From: Paul E. McKenney
Sent: Monday,
Hi Lee,
On 10.12.2018 8.36, Lee Jones wrote:
> On Sat, 08 Dec 2018, Oskari Lemmela wrote:
>
>> From: Chen-Yu Tsai
>>
>> In the axp20x driver, the various mfd_cell lists had varying amounts
>> of indentation, sometimes even within the same list. For the axp288,
>> there's no alignment at all.
>>
Hi,
Anurag Kumar Vulisha writes:
> HI Felipe,
>
>>-Original Message-
>>From: Felipe Balbi [mailto:ba...@kernel.org]
>>Sent: Friday, December 07, 2018 11:42 AM
>>To: Anurag Kumar Vulisha ; Greg Kroah-Hartman
>>; Shuah Khan ; Alan Stern
>>; Johan Hovold ; Jaejoong Kim
>>; Benjamin
When the process being tracked do mremap() without
UFFD_FEATURE_EVENT_REMAP on the corresponding tracking uffd file
handle, we should not generate the remap event, and at the same
time we should clear all the uffd flags on the new VMA. Without
this patch, we can still have the
With the following piece of code, the following compilation warning
is encountered:
if (_IOC_DIR(ioc) != _IOC_NONE) {
int verify = _IOC_DIR(ioc) & _IOC_READ ? VERIFY_WRITE :
VERIFY_READ;
if (!access_ok(verify, ioarg, _IOC_SIZE(ioc))) {
1. add uart APDMA controller device node
2. add uart 0/1/2/3/4/5 DMA function
Signed-off-by: Long Cheng
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 50 +
1 file changed, 50 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
On Mon, Dec 10, 2018 at 2:35 PM Lee Jones wrote:
>
> On Sat, 08 Dec 2018, Oskari Lemmela wrote:
>
> > Parts of the AXP803 are compatible with their counterparts on the AXP813.
> > These include the GPIO, ADC, AC and battery power supplies.
> >
> > Signed-off-by: Oskari Lemmela
> > Reviewed-by:
In Mediatek SOCs, the uart can support DMA function.
Base on DMA engine formwork, we add the DMA code to support uart. And put the
code under drivers/dma.
This series contains document bindings, Kconfig to control the function enable
or not,
device tree including interrupt and dma device node,
On Fri, 07 Dec 2018, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/mfd/Kconfig:config MFD_WM8350
> drivers/mfd/Kconfig:bool
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets remove the couple traces of
On Sat, 08 Dec 2018, Oskari Lemmela wrote:
> From: Chen-Yu Tsai
>
> In the axp20x driver, the various mfd_cell lists had varying amounts
> of indentation, sometimes even within the same list. For the axp288,
> there's no alignment at all.
>
> Re-align the right hand side of the assignments
On Sat, 08 Dec 2018, Oskari Lemmela wrote:
> Parts of the AXP803 are compatible with their counterparts on the AXP813.
> These include the GPIO, ADC, AC and battery power supplies.
>
> Signed-off-by: Oskari Lemmela
> Reviewed-by: Chen-Yu Tsai
> Tested-by: Vasily Khoruzhick
> Signed-off-by:
In DMA engine framework, add 8250 mtk dma to support it.
Signed-off-by: Long Cheng
---
drivers/dma/mediatek/8250_mtk_dma.c | 830 +++
drivers/dma/mediatek/Kconfig| 11 +
drivers/dma/mediatek/Makefile |1 +
3 files changed, 842 insertions(+)
On Sat, 08 Dec 2018, Oskari Lemmela wrote:
> From: Chen-Yu Tsai
>
> In the axp20x driver, the various mfd_cell lists had varying amounts
> of indentation, sometimes even within the same list. For the axp288,
> there's no alignment at all.
>
> Re-align the right hand side of the assignments
On Sat, 08 Dec 2018, Oskari Lemmela wrote:
> Parts of the AXP803 are compatible with their counterparts on the AXP813.
> These include the GPIO, ADC, AC and battery power supplies.
>
> Signed-off-by: Oskari Lemmela
> Reviewed-by: Chen-Yu Tsai
> Tested-by: Vasily Khoruzhick
> Signed-off-by:
Hi Chen Yu and ACPI experts,
On Sat, May 05, 2018 at 07:53:22PM +0800, Chen Yu wrote:
> According to current implementation of acpi_pad driver,
> it does not make sense to spawn any power saving threads
> on the cpus which are already idle - it might bring
> unnecessary overhead on these idle
On Tue, 20 Nov 2018, Oskari Lemmela wrote:
> Parts of the AXP803 are compatible with their counterparts on the AXP813.
> These include the GPIO, ADC, AC and battery power supplies.
>
> Signed-off-by: Oskari Lemmela
> Reviewed-by: Chen-Yu Tsai
> Tested-by: Vasily Khoruzhick
> ---
>
On Sat, 08 Dec 2018, Quentin Schulz wrote:
> Hi Lee,
>
> On Fri, Dec 07, 2018 at 07:22:37PM +, Lee Jones wrote:
> > On Fri, 07 Dec 2018, Vasily Khoruzhick wrote:
> >
> > > On Fri, Dec 7, 2018 at 8:40 AM Lee Jones wrote:
> > >
> > > > My OCD-dar is going crazy.
> > > >
> > > > Why haven't
Hi Martin,
Today's linux-next merge of the scsi-mkp tree got a conflict in:
drivers/scsi/qla2xxx/qla_os.c
between commit:
f2ffd4e5bc7b ("scsi: qla2xxx: Timeouts occur on surprise removal of QLogic
adapter")
from Linus' tree and commit:
c4e521b654e1 ("scsi: qla2xxx: Split the
On Sat, 08 Dec 2018, Dmitry Torokhov wrote:
> On Wed, Nov 28, 2018 at 09:15:32AM +, Lee Jones wrote:
> > On Fri, 23 Nov 2018, Philippe Schenker wrote:
> >
> > > Move defines that are ADC related to the header of the overlying mfd,
> > > so they can be used from multiple sub-devices.
> > >
>
On Sun, 09 Dec 2018, YueHaibing wrote:
> Remove duplicated include.
>
> Signed-off-by: YueHaibing
> ---
> drivers/input/keyboard/mtk-pmic-keys.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/input/keyboard/mtk-pmic-keys.c
> b/drivers/input/keyboard/mtk-pmic-keys.c
> index
On (12/10/18 05:58), Liu, Chuansheng wrote:
> > On (12/10/18 05:40), Liu, Chuansheng wrote:
> > > @@ -130,6 +130,13 @@ static void check_hung_task(struct task_struct *t,
> > unsigned long timeout)
> > > init_utsname()->version);
> > > pr_err("\"echo 0 >
> >
On 12/9/2018 11:01 PM, Martin Blumenstingl wrote:
> Disable power_down by setting the parameter to
> DWC2_POWER_DOWN_PARAM_NONE. This fixes a problem on various Amlogic
> Meson SoCs where USB devices are only recognized when plugged in before
> booting Linux. A hot-plugged USB device was not
> -Original Message-
> From: Sergey Senozhatsky [mailto:sergey.senozhatsky.w...@gmail.com]
> Sent: Monday, December 10, 2018 1:46 PM
> To: Liu, Chuansheng
> Cc: a...@linux-foundation.org; pmla...@suse.com;
> sergey.senozhat...@gmail.com; rost...@goodmis.org; dvyu...@google.com;
>
Hi all,
Today's linux-next merge of the staging tree got a conflict in:
drivers/staging/media/tegra-vde/tegra-vde.c
between commit:
91dc5e91edf7 ("media: staging: tegra-vde: Replace debug messages with trace
points")
from the v4l-dvb tree and commit:
9483804a725a ("media: staging:
On (12/10/18 05:40), Liu, Chuansheng wrote:
> @@ -130,6 +130,13 @@ static void check_hung_task(struct task_struct *t,
> unsigned long timeout)
> init_utsname()->version);
> pr_err("\"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\""
>
Hello,
syzbot found the following crash on:
HEAD commit:83af01ba1c2d Merge branch 'tc-testing-next'
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14cea3f540
kernel config: https://syzkaller.appspot.com/x/.config?x=28ecefa8a6e10719
dashboard link:
Hi Firoz,
On Mon, Dec 10, 2018 at 11:05:38AM +0530, Firoz Khan wrote:
> Please review this patch series and queue it for linux-next.
It's been ~4 days, 2 of which were a weekend. I'll get to it, but
pinging so often won't help.
Thanks,
Paul
Hello,
syzbot found the following crash on:
HEAD commit:97ef7b4c5501 ip: silence udp zerocopy smatch false positive
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=13f4592b40
kernel config: https://syzkaller.appspot.com/x/.config?x=28ecefa8a6e10719
Hello,
syzbot found the following crash on:
HEAD commit:a60956ed72f7 net: dsa: Make dsa_master_set_mtu() static
git tree: net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=14df67eb40
kernel config: https://syzkaller.appspot.com/x/.config?x=28ecefa8a6e10719
Based on patch commit 401c636a0eeb ("kernel/hung_task.c:
show all hung tasks before panic"), we could get the
call stack of hung task.
However, if the console loglevel is not high, we still
can not get the useful information in practice, and
in most cases users don't set console loglevel to
Rob Herring writes:
> Remove directly accessing device_type property and use the
> of_node_is_type accessor instead. While not using it here, this is
> part of eventually removing the struct device_node.type pointer.
>
> Cc: Frederic Barrat
> Cc: Arnd Bergmann
> Cc: Greg Kroah-Hartman
> Cc:
Hi Paul,
On Thu, 6 Dec 2018 at 10:49, Firoz Khan wrote:
>
> The purpose of this patch series is, we can easily
> add/modify/delete system call table support by cha-
> nging entry in syscall.tbl file instead of manually
> changing many files. The other goal is to unify the
> system call table
Hi all,
Today's linux-next merge of the driver-core tree got a conflict in:
drivers/base/platform.c
u
between commit:
2d51ac9086fd ("driver core: platform: Remove duplicated
device_remove_properties() call")
from the pm tree and commit:
99fef587ff98 ("driver core: platform: Respect
On Sun, Dec 09 2018 at 10:55pm -0500,
Jens Axboe wrote:
> On 12/9/18 8:43 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > It appears that there are a series of shared patches between the block
> > and device-mapper trees that are not the same commits. I assume that the
> > block tree has been
Hi all,
On Mon, 10 Dec 2018 15:47:44 +1100 Stephen Rothwell
wrote:
>
> I fixed it up (I used the crypto tree version of the changes) and can
This turned out to be the correct thing to do since my email to Paulo
Flabiano Smorigo (when forwarded to
) bounced. ;-)
--
Cheers,
Stephen
Hello,
On Sun, Dec 9, 2018 at 8:30 PM Dmitry V. Levin wrote:
> syscall_get_* functions are required to be implemented on all
> architectures in order to extend the generic ptrace API with
> PTRACE_GET_SYSCALL_INFO request.
>
> This adds all 5 syscall_get_* functions on xtensa as documented
> in
Hello,
syzbot found the following crash on:
HEAD commit:0844895a2e51 Merge tag 'char-misc-4.20-rc6' of git://git.k..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=153c192540
kernel config: https://syzkaller.appspot.com/x/.config?x=8110fb1cd164e8f
Hello,
syzbot found the following crash on:
HEAD commit:abb8d6ecbd8f Merge tag 'trace-v4.20-rc5' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17932f4d40
kernel config: https://syzkaller.appspot.com/x/.config?x=b9cc5a440391cbfd
Hello,
On Sun, Dec 09, 2018 at 04:29:13PM -0800, David Rientjes wrote:
> [..] on this platform, at least, hugepages are
> preferred on the same socket but there isn't a significant benefit from
> getting a cross socket hugepage over small page. [..]
You didn't release the proprietary software
Hi all,
Today's linux-next merge of the rcu tree got a conflict in:
MAINTAINERS
between commit:
c97e4df573f2 ("MAINTAINERS: change NX/VMX maintainers")
from the crypto tree and commit:
1dfddcdb95c4 ("MAINTAINERS: Update from @linux.vnet.ibm.com to
@linux.ibm.com")
from the rcu tree.
Lorenzo,
You are right, I reviewed few DT files, will need some time to review
this train.
I will start doing it in a while.
Thanks for pitching in.
Thanks.
On Mon, Dec 3, 2018 at 8:58 AM Lorenzo Pieralisi
wrote:
>
> On Tue, Nov 06, 2018 at 01:19:03PM +, Z.q. Hou wrote:
> > From: Hou
>From the da7219 spec, the button A, B, C and D are remapped to
0, 1, 2 and 3 respectively where button A is KEY_PLAYPAUSE,
B is KEY_VOLUMEUP, C is KEY_VOLUMEDOWN and D is KEY_VOICECOMMAND.
Signed-off-by: Zhuohao Lee
Signed-off-by: Max Chang
---
sound/soc/intel/boards/kbl_da7219_max98927.c |
This argument is required to extend the generic ptrace API with
PTRACE_GET_SYSCALL_INFO request: syscall_get_arch() is going
to be called from ptrace_request() along with syscall_get_nr(),
syscall_get_arguments(), syscall_get_error(), and
syscall_get_return_value() functions with a tracee as their
From: Elvira Khabirova
PTRACE_GET_SYSCALL_INFO is a generic ptrace API that lets ptracer obtain
details of the syscall the tracee is blocked in.
There are two reasons for a special syscall-related ptrace request.
Firstly, with the current ptrace API there are cases when ptracer cannot
retrieve
syscall_get_* functions are required to be implemented on all
architectures in order to extend the generic ptrace API with
PTRACE_GET_SYSCALL_INFO request.
This adds all 5 syscall_get_* functions on xtensa as documented
in asm-generic/syscall.h: syscall_get_nr, syscall_get_arguments,
From: Elvira Khabirova
Arch code should use tracehook_*() helpers, as documented
in include/linux/tracehook.h,
ptrace_report_syscall() is not expected to be used outside that file.
The patch does not look very nice, but at least it is correct
and opens the way for PTRACE_GET_SYSCALL_INFO API.
This should never have been defined in the arch tree to begin with,
and now uapi/linux/audit.h header is going to use EM_UNICORE
in order to define AUDIT_ARCH_UNICORE which is needed to implement
syscall_get_arch() which in turn is required to extend
the generic ptrace API with
1 - 100 of 765 matches
Mail list logo
