On Mon, Nov 06, 2017 at 09:41:09AM +0200, Gilad Ben-Yossef wrote:
> On Mon, Nov 6, 2017 at 9:38 AM, Greg Kroah-Hartman
> wrote:
> > On Mon, Nov 06, 2017 at 06:55:49AM +, Gilad Ben-Yossef wrote:
> >> Additional code readability and simplification patches.
> >> These goes on top the previous pat
On 2017-11-04 at 12:24:15 +0100, Rafael J. Wysocki wrote:
> On Sat, Nov 4, 2017 at 3:34 AM, Ramesh Thomas wrote:
> > On 2017-11-03 at 12:47:20 +0100, Rafael J. Wysocki wrote:
> >> From: Rafael J. Wysocki
> >>
> >> The genpd governor currently uses negative PM QoS values to indicate
> >> the "no s
According to the datasheet, in Meson-GXBB/GXL series,
The clock gate bit for SARADC is HHI_GCLK_MPEG2 bit[22],
while clock gate bit for SANA is HHI_GCLK_MPEG0 bit[10].
Test passed at gxl_skt dev board.
Tested-by: Xingyu Chen
Signed-off-by: Yixun Lan
---
I think this error was introduced by a c
On 11/05/2017 10:56 PM, Stefan Wahren wrote:
> Hi Michal,
>
> the dwc2 USB driver on BCM2835 in linux-next is affected by the CMA
> allocation issue. A quick web search guide me to your patch, which avoid the
> issue.
>
> Since the patch wasn't accepted, i want to know is there another solution
On Mon, Nov 6, 2017 at 9:38 AM, Greg Kroah-Hartman
wrote:
> On Mon, Nov 06, 2017 at 06:55:49AM +, Gilad Ben-Yossef wrote:
>> Additional code readability and simplification patches.
>> These goes on top the previous patch set sent to the list.
>
> Please label your 0/X patches the same way your
On 11/06/2017 02:31 AM, Yisheng Xie wrote:
> Hi Vlastimil,
>
> On 2017/10/31 17:46, Vlastimil Babka wrote:
>> +CC Andi and Christoph
>>
>> On 10/27/2017 12:14 PM, Yisheng Xie wrote:
>>> As manpage of migrate_pages, the errno should be set to EINVAL when none
>>> of the specified nodes contain memo
On Mon, Nov 06, 2017 at 06:55:49AM +, Gilad Ben-Yossef wrote:
> Additional code readability and simplification patches.
> These goes on top the previous patch set sent to the list.
Please label your 0/X patches the same way your patches are, with the
prefix of the subsystem, otherwise they get
Hi all,
Changes since 20171103:
New tree: cpupower
The powerpc tree still had its build failure for which I applied a patch.
The crypto tree gained a build failure so I used the version from
next-20171103.
The regmap tree lost its build failure.
The tip tree gained a conflict against the pm t
On Sat, Nov 4, 2017 at 4:53 PM, Serge E. Hallyn wrote:
>
> Quoting Mahesh Bandewar (mah...@bandewar.net):
> > Init-user-ns is always uncontrolled and a process that has SYS_ADMIN
> > that belongs to uncontrolled user-ns can create another (child) user-
> > namespace that is uncontrolled. Any other
This adds the power_mode sysfs interface to the device as documented in
sysfs-bus-iio.
---
Note that I explicitely don't sign off on this.
This is a starting point for anybody who can test it and check for correct
API usage, and ABI correctness, as documented in
Documentation/ABI/testing/sys-bu
Hi Greg
>How is things crashing on startup when you are messing with data being sent on
>shutdown?
>Are you still sending data at startup time?
Yes, I always sending data at startup. Actually I keep sending "reboot" to
serial port, all the time, no break, regardless of any response from system.
On 3 November 2017 at 16:31, Tom Lendacky wrote:
> On 11/3/2017 10:12 AM, Tomeu Vizoso wrote:
>>
>> On 17 July 2017 at 23:10, Tom Lendacky wrote:
>>>
>>> The SMP MP-table is built by UEFI and placed in memory in a decrypted
>>> state. These tables are accessed using a mix of early_memremap(),
>>>
On Fri, Nov 03, 2017 at 11:58:23AM -0500, Gustavo A. R. Silva wrote:
> Make use of the swap macro and remove unnecessary variable temp.
> This makes the code easier to read and maintain.
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by: Gustavo A. R. Silva
Patch applied
> -Original Message-
> From: Chao Yu [mailto:c...@kernel.org]
> Sent: Friday, November 03, 2017 9:16 PM
> To: Fan Li; 'Chao Yu'; 'Jaegeuk Kim'
> Cc: linux-kernel@vger.kernel.org; linux-f2fs-de...@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH RESEND] f2fs: modify the procedure of
Blink the LED on a kernel panic.
Signed-off-by: Amit Kucheria
Acked-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi
b/arch/arm64/boot/dts/qcom/apq8016-sbc.dtsi
index 1d63e6b..e
Blink the LED on a kernel panic.
Signed-off-by: Amit Kucheria
Acked-by: Guodong Xu
Acked-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi6220-hikey.dts
b/arch/arm64/boot/dts/hisili
Most development boards and devices have one or more LEDs. It is useful
during debugging if they can be wired to show different behaviours such as
disk or cpu activity or a load-average dependent heartbeat. Enable panic
and disk activity triggers so they can be tied to LED activity during
debugging
Blink the LED on a kernel panic.
Signed-off-by: Amit Kucheria
Acked-by: Guodong Xu
Tested-by: Manivannan Sadhasivam
---
arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts
b/arch/arm64/boot/dts
This patchset enables the kernel panic and disk-activity trigger for LEDs
and then enables the panic trigger for three 96Boards - DB410c, Hikey and
Hikey960.
DB410c and Hikey panic behaviour has been tested by triggering a panic
through /proc/sysrq-trigger, while Hikey960 is only compile-tested.
On Mon, Nov 6, 2017 at 11:36 AM, Wang Nan wrote:
> tlb_gather_mmu(&tlb, mm, 0, -1) means gathering all virtual memory space.
> In this case, tlb->fullmm is true. Some archs like arm64 doesn't flush
> TLB when tlb->fullmm is true:
>
> commit 5a7862e83000 ("arm64: tlbflush: avoid flushing when ful
On Monday 06 November 2017 12:29 PM, Keerthy wrote:
>
>
> On Monday 06 November 2017 12:25 PM, Sekhar Nori wrote:
>> + linux omap list
>>
>> On Tuesday 31 October 2017 09:57 PM, Alexandre Belloni wrote:
>>> Register an nvmem device to expose the 3 scratch registers (total of 12
>>> bytes) to both
On Monday 06 November 2017 12:25 PM, Sekhar Nori wrote:
> + linux omap list
>
> On Tuesday 31 October 2017 09:57 PM, Alexandre Belloni wrote:
>> Register an nvmem device to expose the 3 scratch registers (total of 12
>> bytes) to both userspace and kernel space.
>>
>> Signed-off-by: Alexandre Be
> -Original Message-
> From: intel-gvt-dev [mailto:intel-gvt-dev-boun...@lists.freedesktop.org] On
> Behalf Of Alex Williamson
> Sent: Monday, November 6, 2017 10:39 AM
> To: Zhang, Tina
> Cc: Tian, Kevin ; Daniel Vetter
> ;
> intel-...@lists.freedesktop.org; joonas.lahti...@linux.intel
Am 05.11.2017 um 04:39 schrieb Ard Biesheuvel:
> On 4 November 2017 at 20:06, Andreas Färber wrote:
>> Am 04.11.2017 um 23:39 schrieb Ard Biesheuvel:
>>> On 4 November 2017 at 15:30, Andreas Färber wrote:
Am 04.11.2017 um 22:57 schrieb Ard Biesheuvel:
> On 4 November 2017 at 13:44, Andre
Turn the code sites that don't require any special handling
on error return to a simple return.
Signed-off-by: Gilad Ben-Yossef
---
drivers/staging/ccree/ssi_driver.c | 28
1 file changed, 12 insertions(+), 16 deletions(-)
diff --git a/drivers/staging/ccree/ssi_driv
Additional code readability and simplification patches.
These goes on top the previous patch set sent to the list.
Gilad Ben-Yossef (3):
staging: ccree: simplify error handling logic
staging: ccree: simplify registers access
staging: ccree: simplify ioread/iowrite
drivers/staging/ccree/cc_
Registers ioread/iowrite operations were done via macros,
sometime using a "magical" implicit parameter.
Replace all register access with simple inline macros.
Signed-off-by: Gilad Ben-Yossef
---
drivers/staging/ccree/cc_hal.h | 33 --
drivers/staging/ccree/cc_regs.h
The register offset calculation macro was taking a HW block base
parameter that was not actually used. Simplify the whole thing
by dropping it and rename the macro for better readability.
Signed-off-by: Gilad Ben-Yossef
---
drivers/staging/ccree/cc_regs.h | 15
drivers/stagi
+ linux omap list
On Tuesday 31 October 2017 09:57 PM, Alexandre Belloni wrote:
> Register an nvmem device to expose the 3 scratch registers (total of 12
> bytes) to both userspace and kernel space.
>
> Signed-off-by: Alexandre Belloni
Looks good to me.
Reviewed-by: Sekhar Nori
Curious on wh
Hi Andrew,
After merging the akpm tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:
lib/cpumask.c: In function 'cpumask_next_and':
lib/cpumask.c:39:9: error: implicit declaration of function 'find_next_and_bit'
[-Werror=implicit-function-declaration]
return find_ne
Hi Linus:
This push fixes an unaligned panic in x86/sha-mb and a bug in ccm
that triggers with certain underlying implementations.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus
Andrey Ryabinin (2):
crypto: x86/sha256-mb - fix panic due to u
Dear Hari,
I did not found where your patch decreases mnt counter,
it seems for me you have lost path_put in perf_fill_ns_link_info().
Thank you,
Vasily Averin
On 2017-11-06 09:22, Vasily Averin wrote:
> Fixes: commit e422267322cd ("perf: Add PERF_RECORD_NAMESPACES to include
> namespace
On Mon, Nov 6, 2017 at 6:29 AM, Al Viro wrote:
> On Sun, Nov 05, 2017 at 02:25:00AM -0800, syzbot wrote:
>
>> loop0/2986 is trying to acquire lock:
>> (&sb->s_type->i_mutex_key#9){}, at: [] inode_lock
>> include/linux/fs.h:712 [inline]
>> (&sb->s_type->i_mutex_key#9){}, at: []
>> generic
Fixes: commit e422267322cd ("perf: Add PERF_RECORD_NAMESPACES to include
namespaces related info")
Signed-off-by: Vasily Averin
---
kernel/events/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 10cdb9c..ab5ac84 100644
--- a/kernel/even
Hi Guenter,
Thanks a lot for the detailed review.
I will try to fix all the comments and send v2 patch.
On Sun, Nov 5, 2017 at 3:30 AM, Guenter Roeck wrote:
> On 11/01/2017 11:33 PM, Lei YU wrote:
>>
>> Nuvoton W83773G is a hardware monitor IC providing one local
>> temperature and two remote t
move the driver from drivers/soc/fsl/qe to drivers/irqchip,
merge qe_ic.h and qe_ic.c into irq-qeic.c.
Signed-off-by: Zhao Qiang
---
MAINTAINERS| 6 ++
drivers/irqchip/Makefile | 1 +
drivers/{soc/fsl/qe/qe_ic.c => irqchip/irq
The codes of qe_ic init from a variety of platforms are redundant,
merge them to a common function and put it to irqchip/irq-qeic.c
For non-p1021_mds mpc85xx_mds boards, use "qe_ic_init(np, 0,
qe_ic_cascade_low_mpic, qe_ic_cascade_high_mpic);" instead of
"qe_ic_init(np, 0, qe_ic_cascade_muxed_mpic
QEIC was supported on PowerPC, and dependent on PPC,
Now it is supported on other platforms, so remove PPCisms.
Signed-off-by: Zhao Qiang
---
arch/powerpc/platforms/83xx/km83xx.c | 1 -
arch/powerpc/platforms/83xx/misc.c| 1 -
arch/powerpc/platforms/83xx/mpc832x_mds.c
QEIC is an interrupt controller for QE, was put under drivers/soc/fsl/qe,
and now move to driver/irqchip.
And QEIC is supported more than just powerpc boards, so remove PPCisms.
changelog:
Changes for v8:
- use IRQCHIP_DECLARE() instead of subsys_initcall in qeic driver
- r
qeic_of_init just get device_node of qeic from dtb and call qe_ic_init,
pass the device_node to qe_ic_init.
So merge qeic_of_init into qe_ic_init to get the qeic node in
qe_ic_init.
Signed-off-by: Zhao Qiang
---
drivers/irqchip/irq-qeic.c | 109 -
incl
Ping! Anyone care to take this trivial fix?
On Tue, Oct 31, 2017 at 8:39 PM, Rakib Mullick wrote:
> Kconfig reference for module-signing.txt file needs to
> be replaced with admin-guide/module-signing.rst.
>
> Signed-off-by: Rakib Mullick
> ---
> init/Kconfig | 2 +-
> 1 file changed, 1 inserti
On Mon, Nov 06, 2017 at 11:25:21AM +1100, Stephen Rothwell wrote:
> Hi Herbert,
>
> After merging the crypto tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/crypto/marvell/marvell-cesa: struct platform_device_id is 24 bytes.
> The last of 1 is:
> 0x6d 0x7
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
include/uapi/linux/prctl.h
between commit:
7582e22038a2 ("arm64/sve: Backend logic for setting the vector length")
2d2123bc7c7f ("arm64/sve: Add prctl controls for userspace vector length
management")
from t
Propagate the error of devfreq_add_device() in devm_devfreq_add_device()
rather than statically returning ENOMEM. This makes it slightly faster
to pinpoint the cause of a returned error.
Fixes: 8cd84092d35e ("PM / devfreq: Add resource-managed function for devfreq
device")
Cc: sta...@vger.kernel.
kaslr feature is enabled in kernel.
Remove kernel text address when dumping idle IP info
Signed-off-by: Liu Changcheng
Signed-off-by: Jerry Liu
diff --git a/lib/nmi_backtrace.c b/lib/nmi_backtrace.c
index 0bc0a35..9cc4178 100644
--- a/lib/nmi_backtrace.c
+++ b/lib/nmi_backtrace.c
@@ -92,7 +92,7
Currently we are leaking addresses from the kernel to user space. This
script is an attempt to find some of those leakages. Script parses
`dmesg` output and /proc and /sys files for hex strings that look like
kernel addresses.
Only works for 64 bit kernels, the reason being that kernel addresses
o
Hi Alexei, Naveen,
On 11/04/2017 11:01 PM, Naveen N. Rao wrote:
>
> I think the offsets described in dwarf were incorrect with
> CONFIG_GCC_PLUGIN_RANDSTRUCT, but I'll let Sandipan confirm that.
>
I think that the offsets described in dwarf are probably incorrect when
CONFIG_GCC_PLUGIN_RANDSTR
Hi Tom,
On Mon, Oct 30, 2017 at 03:51:48PM -0500, Tom Zanussi wrote:
> RINGBUF_TYPE_TIME_STAMP is defined but not used, and from what I can
> gather was reserved for something like an absolute timestamp feature
> for the ring buffer, if not a complete replacement of the current
> time_delta scheme
Hi Huacai,
On Mon, Nov 06, 2017 at 12:41:48PM +0800, Huacai Chen wrote:
> Hi, Willy,
>
> Does these two patches really needed for 3.10? They are marked for 4.4 and
> 4.6.
>
> ext4: avoid deadlock when expanding inode size
>
> ext4: in ext4_seek_{hole,data}, return -ENXIO for negative offsets
On Friday 03 November 2017 08:00 PM, Niklas Cassel wrote:
> dra7xx_pcie_shutdown should be static.
>
> This patch introduces a new sparse warning.
Thanks Niklas for reporting.
Bjorn,
Should i send a next version or just a fix patch on top of this?
Regards,
Keerthy
>
> On Wed, Oct 11, 2017
> -Original Message-
> From: Himanshu Jha [mailto:himanshujha199...@gmail.com]
> Sent: Wednesday, October 11, 2017 9:06 PM
> To: j...@linux.vnet.ibm.com
> Cc: martin.peter...@oracle.com; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; subbu.seethara...@broadcom.com;
> ketan.muk
Hi, Willy,
Does these two patches really needed for 3.10? They are marked for 4.4 and 4.6.
ext4: avoid deadlock when expanding inode size
ext4: in ext4_seek_{hole,data}, return -ENXIO for negative offsets
Huacai
Hi Mark,
On Mon, 6 Nov 2017 15:21:57 +1100 Stephen Rothwell
wrote:
>
> On Mon, 6 Nov 2017 11:52:14 +1100 Stephen Rothwell
> wrote:
> >
> > After merging the regmap tree, today's linux-next build
> > (arm_multi_v7_defconfig) produced this warning:
> >
> > drivers/gpio/Kconfig:13:error: recursi
Previous patch supports the multiple time range.
For example, select the first and second 10% time slices.
perf report --time 10%/1,10%/2
We need a function to check if a timestamp is in the ranges of
[0, 10%) and [10%, 20%].
Note that it includes the last element in [10%, 20%] but it
doesn't in
In perf record, it's walked on all samples yet. So it's very easy to get
the first/last samples and save the time to perf file header via the
function write_sample_time().
In later, perf report/script will fetch the time from perf file header.
Change log:
---
v6: Currently '--buildid-all'
perf report has a --time option to limit the time range of output.
It only supports absolute time.
Now this option is extended to support multiple time ranges and
support the percent of time.
For example:
1. Select the first and second 10% time slices
perf report --time 10%/1,10%/2
2. Select fr
perf report/script/... have a --time option to limit the time range
of output. That's very useful to slice large traces, e.g. when processing
the output of perf script for some analysis.
But right now --time only supports absolute time. Also there is no fast
way to get the start/end times of a giv
perf script has a --time option to limit the time range of output.
It only supports absolute time.
Now this option is extended to support multiple time ranges and
support the percent of time.
For example:
1. Select the first and second 10% time slices
perf script --time 10%/1,10%/2
2. Select
v6:
---
1. Create a new option "--timestamp-boundary" in perf record.
Currently '--buildid-all' is not enabled by default. So the walking
on all samples is the default operation. There is no big overhead
to calculate the timestamp boundary in process_sample_event handler
once we alr
Current perf report/script/... have a --time option to limit the time
range of output. But right now it only supports absolute time.
For easy using, now it can support a percent of time usage.
For example:
1. Select the second 10% time slice
perf report --time 10%/2
2. Select from 0% to 10%
Hi Mark,
On Mon, 6 Nov 2017 11:52:14 +1100 Stephen Rothwell
wrote:
>
> After merging the regmap tree, today's linux-next build
> (arm_multi_v7_defconfig) produced this warning:
>
> drivers/gpio/Kconfig:13:error: recursive dependency detected!
> For a resolution refer to Documentation/kbuild/kco
Hi,
When parsing drivers/staging/unisys/visorbus/visorchipset.c in Greg's
staging tree checkpatch emits
--
visorchipset.c
--
WARNING: char * array declaration might be better as static const
#1050: FILE: visorchipset.c:1050:
+ char *envp[] = { env_cmd, env_id, env_st
I run into below error when building futext
/bin/sh: -c: line 5: syntax error: unexpected end of file
the closing ";" and "\" are necessary.
My OS is "Ubuntu 14.04.5 LTS"
Signed-off-by: Lei Yang
---
tools/testing/selftests/futex/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(
On 10/30/2017 12:46 PM, Prateek Sood wrote:
> Remove circular dependency deadlock in a scenario where hotplug of CPU is
> being done while there is updation in cgroup and cpuset triggered from
> userspace.
>
> Process A => kthreadd => Process B => Process C => Process A
>
> Process A
> cpu_subsys
Hi Dmitry,
Thanks for your mention.
>Hi Anthony,
>On Tue, Oct 31, 2017 at 07:17:56PM +0900, Anthony Kim wrote:
>> Hi,
>>
>> I remake patch to base on dmitry's modified code.
>> Please refer as follow.
>> http://www.spinics.net/lists/linux-input/msg53724.html
>>
>> That code is working well alm
Hi James,
Today's linux-next merge of the scsi tree got a conflict in:
include/scsi/scsi_devinfo.h
between commit:
28a0bc4120d3 ("scsi: sd: Implement blacklist option for WRITE SAME w/ UNMAP")
from Linus' tree and commit:
f26aeada0493 ("scsi: scsi_devinfo: Reformat blacklist flags")
fr
From: Changbin Du
The build message for fdimage/isoimage are pretty unstructured. The raw
shell command blocks are printed. We can improve them as regular build
system messages. Besides, writing commands in a shell script is much more
easy than in a Makefile.
See Ingo's suggestion here https://l
From: Changbin Du
Ignore generated files fdimage,mtools.conf and image.iso.
Signed-off-by: Changbin Du
---
arch/x86/boot/.gitignore | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/x86/boot/.gitignore b/arch/x86/boot/.gitignore
index e3cf9f6..09d25dd 100644
--- a/arch/x86/boot/.giti
From: Changbin Du
It avoids the following warning triggered by newer versions of mkisofs::
I: -input-charset not specified, using utf-8 (detected in locale settings)
Signed-off-by: Changbin Du
---
arch/x86/boot/genimage.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
From: Changbin Du
This serias is a expansion of below original patch after discussion with Ingo
and Yamada.
[PATCH] x86, build: Improve the isolinux searching of isoimage generation
v2: some improvement for commit messages.
Changbin Du (4):
x86, build: Factor out fdimage/isoimage generation c
From: Changbin Du
Recently I failed to build isoimage target, because the path of isolinux.bin
changed to /usr/xxx/ISOLINUX/isolinux.bin, as well as ldlinux.c32 which
changed to /usr/xxx/syslinux/modules/bios/ldlinux.c32.
This patch improves the file search logic:
- Show a error message instea
tlb_gather_mmu(&tlb, mm, 0, -1) means gathering all virtual memory space.
In this case, tlb->fullmm is true. Some archs like arm64 doesn't flush
TLB when tlb->fullmm is true:
commit 5a7862e83000 ("arm64: tlbflush: avoid flushing when fullmm == 1").
Which makes leaking of tlb entries. For exampl
Unbound devices may race with calling this function causing the mutex
to stay locked. This failure mode should have released the mutex too.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/dell-smbios-wmi.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/driv
This failure mode should have also released the mutex.
Signed-off-by: Mario Limonciello
---
drivers/platform/x86/wmi.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/platform/x86/wmi.c b/drivers/platform/x86/wmi.c
index 8c31ed4..791449a 100644
--- a/drivers/pla
Some of the failure scenarios weren't releasing acquired mutexes.
Here are some patches that correct them.
Mario Limonciello (2):
platform/x86: wmi: release mutex on module acquistion failure
platform/x86: dell-smbios-wmi: release mutex lock on WMI call failure
drivers/platform/x86/dell-smbi
On Sat, 2017-11-04 at 22:26 +0100, Arnd Bergmann wrote:
> This interface is inefficient and deprecated because of the y2038
> overflow.
>
> ktime_get_seconds() is an appropriate replacement here, since it
> has sufficient granularity but is more efficient and uses monotonic
> time.
>
> Signed-off
On Sun, Nov 05, 2017 at 02:25:00AM -0800, syzbot wrote:
> loop0/2986 is trying to acquire lock:
> (&sb->s_type->i_mutex_key#9){}, at: [] inode_lock
> include/linux/fs.h:712 [inline]
> (&sb->s_type->i_mutex_key#9){}, at: []
> generic_file_write_iter+0xdc/0x7a0 mm/filemap.c:3151
>
> but n
On 05/11/17 08:26, Arnd Bergmann wrote:
This interface is inefficient and deprecated because of the y2038
overflow.
ktime_get_seconds() is an appropriate replacement here, since it
has sufficient granularity but is more efficient and uses monotonic
time.
Signed-off-by: Arnd Bergmann
Reviewed
From: Yu Chen
Check vdev->real_port 0 to avoid panic
[9.261347] []
xhci_free_virt_devices_depth_first+0x58/0x108
[9.261352] [] xhci_mem_cleanup+0x1bc/0x570
[9.261355] [] xhci_stop+0x140/0x1c8
[9.261365] [] usb_remove_hcd+0xfc/0x1d0
[9.261369] [] xhci_plat_remove+0x6c/0xa8
[
kaslr feature is enabled in kernel.
Remove kernel text address when dumping idle IP info
Signed-off-by: Liu Changcheng
Signed-off-by: Jerry Liu
diff --git a/lib/nmi_backtrace.c b/lib/nmi_backtrace.c
index 0bc0a35..9cc4178 100644
--- a/lib/nmi_backtrace.c
+++ b/lib/nmi_backtrace.c
@@ -92,7 +92,7
The uniform structure filter_arg sets its union based
on the difference of enum filter_arg_type, However,
some functions use implicit type conversion obviously.
warning: implicit conversion from enumeration type 'enum filter_exp_type'
to different enumeration type 'enum filter_op_type'
w
From: gatieme
There are several issues when building plugin_traceevent.
First, We can specify a directory compiled by OUTPUT,
but make clean ignores this and uses the current directory.
Second, It generate a dynamic link library
libtraceevent.so.$(EP_VERSION) with the version
number as a suffix
On 2017/11/6 8:55, Jaegeuk Kim wrote:
> On 11/05, Chao Yu wrote:
>> From: Chao Yu
>>
>> This patch slightly changes need_do_checkpoint to return the detail
>> info that indicates why we need do checkpoint, then caller could print
>> it with trace message.
>>
>> Signed-off-by: Chao Yu
>> ---
>> f
This patch slightly changes need_do_checkpoint to return the detail
info that indicates why we need do checkpoint, then caller could print
it with trace message.
Signed-off-by: Chao Yu
---
v2:
- add enum cp_reason_type for interpret detail reason in tracepoint.
fs/f2fs/f2fs.h | 12 +
Hi Ingo,
On Sun, Nov 05, 2017 at 10:33:53AM +0100, Ingo Molnar wrote:
>
> * changbin...@intel.com wrote:
>
> > From: Changbin Du
> >
> > Recently I failed to build isoimage target, because the path of isolinux.bin
> > changed to /usr/xxx/ISOLINUX/isolinux.bin, as well as ldlinux.c32 which
> >
On Sun, Nov 05, 2017 at 10:32:08AM +0100, Ingo Molnar wrote:
>
> A few spelling fixes:
>
> in the title:
>
> s/Fact out
> /Factor out
>
> * changbin...@intel.com wrote:
>
> > From: Changbin Du
> >
> > The build message for fdimage/isoimage are pretty unstructured. The raw
> > shell command
On Monday 30 October 2017 02:18 PM, Faiz Abbas wrote:
>
>
> On Thursday 26 October 2017 01:29 PM, Faiz Abbas wrote:
>> David,
>>
>> On Thursday 19 October 2017 06:56 PM, David Laight wrote:
>>> From: Faiz Abbas
Sent: 19 October 2017 14:09
On Thursday 19 October 2017 06:13 PM, Faiz Abb
Hi Neil
On 11/05/17 00:40, Neil Armstrong wrote:
> Hi Yixun,
>
> Le 04/11/2017 09:41, Yixun Lan a écrit :
>>
>>
>> On 11/04/17 02:17, Yixun Lan wrote:
>>> According to the datasheet, the clock gate bit for
>>> SARADC is bit[22] in Meson-GXBB/GXL series.
>>>
>>> Change-Id: Ic4fa58276d2a9ea273eef0a
This patch adds the watchdog driver for Spreadtrum SC9860 platform.
Signed-off-by: Eric Long
---
Changes since v5:
- Modify the "irq" type as int type.
- Delete unused api sprd_wdt_is_running().
Changes since v4:
- Remove sprd_wdt_remove().
- Add devm_add_action() for sprd_wdt_disable().
Ch
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in:
arch/arm64/kvm/inject_fault.c
between commit:
fd6c8c206fc5 ("arm/arm64: KVM: set right LR register value for 32 bit guest
when inject abort")
from Linus' tree and commit:
00586cdaf597 ("KVM: arm/arm64: Unify 32bit
This patch adds the documentation for Spreadtrum watchdog driver.
Signed-off-by: Eric Long
Acked-by: Rob Herring
---
Changes since v5:
- No updates.
Changes since v4:
- No updates.
Changes since v3:
- No updates.
Changes since v2:
- Add acked tag from Rob.
Changes since v1:
- No updates.
---
Hi all,
Today's linux-next merge of the kvm-arm tree got a conflict in:
arch/arm/kvm/emulate.c
between commit:
fd6c8c206fc5 ("arm/arm64: KVM: set right LR register value for 32 bit guest
when inject abort")
from Linus' tree and commit:
00586cdaf597 ("KVM: arm/arm64: Unify 32bit fault i
Hi Jiri,
On 11/03/17 at 06:28pm, Jiri Bohac wrote:
> On machines where the GART aperture is mapped over physical RAM
> /proc/vmcore contains the remapped range and reading it may
> cause hangs or reboots. This range needs to be excluded from /proc/vmcore.
>
> This has originally been implemented
On Mon, 6 Nov 2017 10:19:17 +0800
Tina Zhang wrote:
> Add VFIO_DEVICE_QUERY_GFX_PLANE ioctl command to let user query and get
> a plane and its related information. So far, two types of buffers are
> supported: buffers based on dma-buf and buffers based on region.
>
> This ioctl can be invoked
User-Mode Instruction Prevention is a security feature present in new
Intel processors that, when set, prevents the execution of a subset of
instructions if such instructions are executed in user mode (CPL > 0).
Attempting to execute such instructions causes a general protection
exception.
The sub
Computing a linear address involves several steps. The first step is to
compute the effective address. This requires determining the addressing
mode in use and perform arithmetic operations on the operands. Plus, each
addressing mode has special cases that must be handled.
Once the effective addre
32-bit and 64-bit address encodings are identical. Thus, the same logic
could be used to resolve the effective address. However, there are two key
differences: address size and enforcement of segment limits.
If running a 32-bit process on a 64-bit kernel, it is best to perform
the address calculat
It is possible to utilize 32-bit address encodings in virtual-8086 mode via
an address override instruction prefix. However, the range of the
effective address is still limited to [0x-0x]. In such a case, return
error.
Also, linear addresses in virtual-8086 mode are limited to 20 bits. Enforce
Tasks running in virtual-8086 mode, in protected mode with code segment
descriptors that specify 16-bit default address sizes via the D bit, or via
an address override prefix will use 16-bit addressing form encodings as
described in the Intel 64 and IA-32 Architecture Software Developer's
Manual Vo
The feature User-Mode Instruction Prevention present in recent Intel
processor prevents a group of instructions (sgdt, sidt, sldt, smsw, and
str) from being executed with CPL > 0. Otherwise, a general protection
fault is issued.
Rather than relaying to the user space the general protection fault c
1 - 100 of 337 matches
Mail list logo
