On Tue, Sep 12, 2017 at 02:44:36PM +0800, Huang, Ying wrote:
> Minchan Kim writes:
>
> > On Tue, Sep 12, 2017 at 01:23:01PM +0800, Huang, Ying wrote:
> >> Minchan Kim writes:
> >>
> >> > page_cluster 0 means "we don't want readahead" so in the case,
> >> > let's skip the readahead detection log
Add QSPI node support, and this function is disabled by default
This setting could be overwritten in board-level definitions
Signed-off-by: SZ Lin
---
arch/arm/boot/dts/ls1021a.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm/boot/dts/ls1021a.dtsi b/arch/arm/boot
Hi Sergey,
On Tue, Sep 12, 2017 at 02:00:05PM +0900, Sergey Senozhatsky wrote:
> ZSTD tends to outperform deflate/inflate, thus we remove
> zlib from the list of recommended algorithms and recommend
> zstd instead.
>
> Signed-off-by: Sergey Senozhatsky
> Suggested-by: Minchan Kim
One of my c
On Mon 11-09-17 23:05:25, Ross Zwisler wrote:
> This helper, in the spirit of ext4_should_dioread_nolock() et al., replaces
> the complex conditional in ext4_set_inode_flags().
>
> Signed-off-by: Ross Zwisler
Yeah, makes sense to me. You can add:
Reviewed-by: Jan Kara
On Mon 11-09-17 23:05:24, Ross Zwisler wrote:
> We prevent DAX from being used on inodes which are using ext4's built in
> encryption via a check in ext4_set_inode_flags(). We do have what appears
> to be an unsafe transition of S_DAX in ext4_set_context(), though, where
> S_DAX can get disabled w
Minchan Kim writes:
> On Tue, Sep 12, 2017 at 01:23:01PM +0800, Huang, Ying wrote:
>> Minchan Kim writes:
>>
>> > page_cluster 0 means "we don't want readahead" so in the case,
>> > let's skip the readahead detection logic.
>> >
>> > Cc: "Huang, Ying"
>> > Signed-off-by: Minchan Kim
>> > ---
Hi all,
Hans de Goede, one of the upower maintainers, suggested I alert you all
to this bug:
https://bugs.freedesktop.org/show_bug.cgi?id=100041
and the new one I filed via the kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=196913
"keyboard backlight max_brightness value outside
On Mon 11-09-17 23:05:23, Ross Zwisler wrote:
> The current code has the potential for data corruption when changing an
> inode's journaling mode, as that can result in a subsequent unsafe change
> in S_DAX.
>
> I've captured an instance of this data corruption in the following fstest:
>
> https:
On Mon 11-09-17 23:05:22, Ross Zwisler wrote:
> If an inode has inline data it is currently prevented from using DAX by a
> check in ext4_set_inode_flags(). When the inode grows inline data via
> ext4_create_inline_data() or removes its inline data via
> ext4_destroy_inline_data_nolock(), the valu
On Tue, Sep 12, 2017 at 03:04:56PM +0900, Sergey Senozhatsky wrote:
> On (09/12/17 11:37), Minchan Kim wrote:
> > + } else {
> > + /* skip swapcache */
> > + page = alloc_page_vma(GFP_HIGHUSER_MOVABLE, vma,
> > vmf->address);
>
> what if alloc_page_vm
On Mon, Sep 11, 2017 at 8:24 PM, Chris Mason wrote:
> Hi Linus,
>
> Nick Terrell's patch series to add zstd support to the kernel has been
> floating around for a while. After talking with Dave Sterba, Herbert
> and Phillip, we decided to send the whole thing in as one pull request.
As the Squas
Fix below incorrect display when reading discard_granularity sysfs node.
$ cat /sys/fs/f2fs//discard_granularity
$ 16
$ echo 32 > /sys/fs/f2fs//discard_granularity
$ cat /sys/fs/f2fs//discard_granularity
$ 16
Signed-off-by: Chao Yu
---
fs/f2fs/sysfs.c | 2 ++
1 file changed, 2 insertions(+)
di
On Tue, Sep 12, 2017 at 01:23:01PM +0800, Huang, Ying wrote:
> Minchan Kim writes:
>
> > page_cluster 0 means "we don't want readahead" so in the case,
> > let's skip the readahead detection logic.
> >
> > Cc: "Huang, Ying"
> > Signed-off-by: Minchan Kim
> > ---
> > include/linux/swap.h | 3 ++
On Sat, Sep 09, 2017 at 03:32:48AM +, Guenter Roeck wrote:
> On 09/05/2017 10:38 PM, Eric Long wrote:
> > This patch adds the watchdog driver for Spreadtrum SC9860 platform.
> >
> > Signed-off-by: Eric Long
> > ---
> > drivers/watchdog/Kconfig| 8 +
> > drivers/watchdog/Makefile |
hi Sergey and Petr
> Hi,
> On (08/11/17 00:55), pierre kuo wrote:
> [..]
>> And people will be hard to find out some part of message is left behind.
>> (since the tail of original message is elegantly dropped by "\n")
>> That is the reason I try to add such warning in msg_print_text.
>
> have you e
Add a bugon in f2fs_evict_inode to detect inconsistent status between
inode cache and related node page cache.
Signed-off-by: Chao Yu
---
fs/f2fs/inode.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c
index c3e60fa60957..42a8594d6361 100644
--- a/fs/f2fs
On (09/12/17 11:37), Minchan Kim wrote:
> + } else {
> + /* skip swapcache */
> + page = alloc_page_vma(GFP_HIGHUSER_MOVABLE, vma,
> vmf->address);
what if alloc_page_vma() fails?
> + __SetPageLocked(page);
> +
On Mon, Sep 11, 2017 at 09:07:13PM +0100, Al Viro wrote:
> On Mon, Sep 11, 2017 at 04:44:40PM +1000, Dave Chinner wrote:
>
> > > iov_iter_get_pages() for pipe-backed destination does page allocation
> > > and inserts freshly allocated pages into pipe.
> >
> > Oh, it's hidden more layers down than
Hi,
On 09/08/17 at 12:16pm, AKASHI Takahiro wrote:
[snip]
> --- a/include/linux/kexec.h
> +++ b/include/linux/kexec.h
> @@ -162,6 +162,25 @@ int __weak arch_kexec_walk_mem(struct kexec_buf *kbuf,
> int (*func)(u64, u64, void *));
> extern int kexec_add_buffer(struct ke
If 'dmam_alloc_attrs()' fails, we must go through the error handling code,
as done elsewhere in this function. Otherwise, there is a resource leak.
Signed-off-by: Christophe JAILLET
---
I'm also puzzled by the 'framebuffer_alloc()' call a few lines above.
'ret' is known to be 0 at this point. I g
On Tue, Sep 12, 2017 at 10:10:51AM +0900, Masami Hiramatsu wrote:
> To enable jump optimized probe with CONFIG_PREEMPT, use
> synchronize_rcu_tasks() to wait for all tasks preempted
> on trampoline code back on track.
>
> Since the jump optimized kprobes can replace multiple
> instructions, there
On Tue, Sep 12, 2017 at 5:42 AM, Cameron Gutman wrote:
> On 09/11/2017 05:26 AM, Andrey Konovalov wrote:
>> Hi!
>>
>> I've got the following crashes while fuzzing the kernel with syzkaller.
>>
>> On commit 81a84ad3cb5711cec79f4dd53a4ce026b092c432 (Sep 3).
>>
>> usb 1-1: BOGUS urb xfer, pipe 1 != t
Minchan Kim writes:
> page_cluster 0 means "we don't want readahead" so in the case,
> let's skip the readahead detection logic.
>
> Cc: "Huang, Ying"
> Signed-off-by: Minchan Kim
> ---
> include/linux/swap.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/include/li
Hi Luis,
To confirm, reverting this fixes the problem I was seeing in 4.13. I've
queued it up for the next 4.13-stable release as well.
>>>
>>> Commit 81f95076281f ("firmware: add sanity check on shutdown/suspend") may
>>> seem kludgy but the reason for it was to cleanup the horrible f
This helper, in the spirit of ext4_should_dioread_nolock() et al., replaces
the complex conditional in ext4_set_inode_flags().
Signed-off-by: Ross Zwisler
---
fs/ext4/inode.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.
The following commit:
commit 9b7365fc1c82 ("ext4: add FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR
interface support")
added several defines related to extended attributes to ext4.h. They were
added within an #ifndef FS_IOC_FSGETXATTR block with the comment:
/* Until the uapi changes get merged for proj
If an inode has inline data it is currently prevented from using DAX by a
check in ext4_set_inode_flags(). When the inode grows inline data via
ext4_create_inline_data() or removes its inline data via
ext4_destroy_inline_data_nolock(), the value of S_DAX can change.
Currently these changes are un
This series prevents a pair of data corruptions with ext4 + DAX. The first
such corruption happens when combining the inline data feature with DAX,
and the second happens when combining data journaling with DAX.
Both can be reliably reproduced with the fstests that I have posted here:
https://pa
We prevent DAX from being used on inodes which are using ext4's built in
encryption via a check in ext4_set_inode_flags(). We do have what appears
to be an unsafe transition of S_DAX in ext4_set_context(), though, where
S_DAX can get disabled without us doing a proper writeback + invalidate.
Ther
The current code has the potential for data corruption when changing an
inode's journaling mode, as that can result in a subsequent unsafe change
in S_DAX.
I've captured an instance of this data corruption in the following fstest:
https://patchwork.kernel.org/patch/9948377/
Prevent this data cor
ZSTD tends to outperform deflate/inflate, thus we remove
zlib from the list of recommended algorithms and recommend
zstd instead.
Signed-off-by: Sergey Senozhatsky
Suggested-by: Minchan Kim
---
drivers/block/zram/zcomp.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/block/zram/z
Add ZSTD to the list of supported compression algorithms.
ZRAM fio perf test:
LZO DEFLATE ZSTD
#jobs1
WRITE: (2180MB/s) (77.2MB/s) (1429MB/s)
WRITE: (1617MB/s) (77.7MB/s) (1202MB/s)
READ:(426MB/s) (59
On Mon, Sep 11, 2017 at 12:56 PM, Christophe JAILLET
wrote:
> All other error handling paths in this function go through the 'error'
> label. This one should do the same.
>
> Fixes: 9cc9a5cb176c ("datapath: Avoid using stack larger than 1024.")
> Signed-off-by: Christophe JAILLET
> ---
> I think
On (09/12/17 11:37), Minchan Kim wrote:
[..]
> If rw-page based fast storage is used for swap devices, we need to
> detect it to enhance swap IO operations.
> This patch is preparation for optimizing of swap-in operation with
> next patch.
>
> Signed-off-by: Minchan Kim
> ---
> include/linux/swa
Add a regression test for the following kernel commit:
ext4: prevent data corruption with journaling + DAX
The test passes if either we successfully compare the data between the mmap
with journaling turned on and the one with journaling turned off, or if we
fail the chattr command to turn on or
Signed-off-by: Ross Zwisler
---
.gitignore | 4
1 file changed, 4 insertions(+)
diff --git a/.gitignore b/.gitignore
index 28fe84d..2accc37 100644
--- a/.gitignore
+++ b/.gitignore
@@ -238,3 +238,7 @@
/tests/xfs/033.out
/tests/xfs/071.out
/tests/xfs/096.out
+
+# cscope files
+cscope.*
+n
Add a regression test for the following kernel commit:
ext4: prevent data corruption with inline data + DAX
The test passes either if we don't encounter corruption, or if mounting
with DAX + inline data fails. The latter is the way that we prevent this
issue in the kernel.
Signed-off-by: Ross
On Mon, Sep 11, 2017 at 02:47:54PM +0800, Dave Young wrote:
> Hi,
>
> On 09/08/17 at 12:16pm, AKASHI Takahiro wrote:
> > load_other_segments() sets up and adds all the memory segments necessary
> > other than kernel, including initrd, device-tree blob and purgatory.
> > Most of the code was borrow
On Sun, Sep 10, 2017 at 11:41:47PM +0800, kbuild test robot wrote:
> Hi AKASHI,
>
> [auto build test ERROR on arm64/for-next/core]
> [also build test ERROR on v4.13 next-20170908]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
Hi Mathieu,
On Tue, Aug 29, 2017 at 11:55 AM, Mathieu Desnoyers
wrote:
> - On Aug 28, 2017, at 1:12 PM, Max Filippov jcmvb...@gmail.com wrote:
>> On Mon, Aug 28, 2017 at 12:36 AM, Mathieu Desnoyers
>> wrote:
>>> The membarrier system call now requires all architectures to implement
>>> sync_
> Yeah, that's exactly like what I made a mistake before.
> I should have mentioned that earlier. :)
Or I think the previous code which used "iter++" might be right.
You might just want to check the fixed number of small discards,
DISCARD_ISSUE_RATE,
when issue_cond is "true".
Anyways, I have an
On 09/12, Chao Yu wrote:
> On 2017/9/12 9:53, Chao Yu wrote:
> > On 2017/9/11 11:38, Jaegeuk Kim wrote:
> >> If issue_cond is true, it does double count for # of issued commands.
> >>
> >> Signed-off-by: Jaegeuk Kim
> >
> > Reviewed-by: Chao Yu
>
> As Daeho Jeong mentioned, the change makes 'it
Hi all,
Please do not add any v4.15 related material to your linux-next
included branches until after v4.14-rc1 has been released.
Changes since 20170911:
Non-merge commits (relative to Linus' tree): 1124
1423 files changed, 55946 insertions(+), 14234 dele
On 2017/9/12 9:53, Chao Yu wrote:
> On 2017/9/11 11:38, Jaegeuk Kim wrote:
>> If issue_cond is true, it does double count for # of issued commands.
>>
>> Signed-off-by: Jaegeuk Kim
>
> Reviewed-by: Chao Yu
As Daeho Jeong mentioned, the change makes 'iter > DISCARD_ISSUE_RATE' dead
code, I just
This commit allows OMAP3530 variants to use common data that is
available in 'omap3-evm-processor-common.dtsi'. It adds proper pinmux
macros for 'omap3_pmx_core2' on OMAP3430. The Micron NAND chip is also
added for the TMDSEVM3530 processor module.
Signed-off-by: Derald D. Woods
---
arch/arm/bo
This commit moves common OMAP3-EVM processor module device tree data
to a separate include file. This will allow for 'omap3-evm.dts' to use
device tree data that is unique to the OMAP3530 version of the
processor module, while making use of the work already done for the
'omap3-evm-37xx.dts'.
Signe
The Sharp panel driver and regulator are now selected properly. This
commit eliminates a dummy regulator assignment.
Signed-off-by: Derald D. Woods
---
arch/arm/boot/dts/omap3-panel-sharp-ls037v7dw01.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/om
This patch set allows TMDSEVM3530(omap3-evm.dts) to boot using common
processor module data that is shared with 'omap3-evm-37xx.dts'. A new
common file for processor module data is introduced to help facilitate
the updated OMAP3530 support.
Changes in v2
-
- Pull in change from linux-n
This commit eliminates two dummy regulator assignments.
Signed-off-by: Derald D. Woods
---
arch/arm/boot/dts/omap3-evm-processor-common.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-evm-processor-common.dtsi
b/arch/arm/boot/dts/omap3-evm-processor-common.dt
On 09/11/2017 09:53 AM, Petr Mladek wrote:
> On Wed 2017-08-30 17:38:44, Jason Baron wrote:
>> When doing cumulative patches, if patch A introduces a change to function 1,
>> and patch B reverts the change to function 1 and introduces changes to say
>> function 2 and 3 as well, the change that pa
Mainline crashes as follows when running nios2 images.
On node 0 totalpages: 65536
free_area_init_node: node 0, pgdat c8408fa0, node_mem_map c8726000
Normal zone: 512 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 65536 pages, LIFO batch:15
Unable to handle kernel NULL poin
On 09/11/2017 05:26 AM, Andrey Konovalov wrote:
> Hi!
>
> I've got the following crashes while fuzzing the kernel with syzkaller.
>
> On commit 81a84ad3cb5711cec79f4dd53a4ce026b092c432 (Sep 3).
>
> usb 1-1: BOGUS urb xfer, pipe 1 != type 3
> WARNING: CPU: 1 PID: 2574 at drivers/usb/core/urb.c:44
Document struct tcpc_config and struct tcpc_dev.
Drop unused TCPC_USB_SWITCH_RESTORE.
Signed-off-by: Guenter Roeck
---
v2, v3: No change
drivers/staging/typec/tcpm.h | 57 ++--
1 file changed, 50 insertions(+), 7 deletions(-)
diff --git a/drivers/staging
The driver is in good enough shape to be moved out of staging.
Do it.
Signed-off-by: Guenter Roeck
---
v2: Use format-patch -M
v3: No change
drivers/staging/typec/Kconfig| 2 --
drivers/staging/typec/Makefile | 1 -
drivers/staging/typec/fusb302/T
Move tcpm (USB Type-C Port Manager) out of staging.
Signed-off-by: Guenter Roeck
---
v2: Use format-patch -M
v3: No change
drivers/staging/typec/Kconfig | 8
drivers/staging/typec/Makefile| 1 -
drivers/staging/typec/TODO
Commented out code can be added as needed. Drop it.
Also drop TODO and an obsolete XXX comment.
Signed-off-by: Guenter Roeck
---
v2, v3: No change
drivers/staging/typec/tcpm.c | 37 +
1 file changed, 1 insertion(+), 36 deletions(-)
diff --git a/drivers/stagi
struct pd_message is the format of a PD message as seen on the wire.
Signed-off-by: Guenter Roeck
---
v2: No change
v3: Fix document tag
drivers/staging/typec/pd.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/staging/typec/pd.h b/drivers/staging/typec/pd.h
index 30b32ad72acd
On Sun, Sep 10, 2017 at 6:58 PM, Max Filippov wrote:
> On Sun, Sep 10, 2017 at 11:31 AM, Guenter Roeck wrote:
>> xtensa:allmodconfig fails to build in mainline with compiler errors
>> as follows.
>>
>> drivers/staging/rtl8723bs/core/rtw_ap.c: In function ‘expire_timeout_chk’:
>> drivers/staging/r
From: Masaki Ota
-To support Alps T4 device, separate U1 device code
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 120 +++--
1 file changed, 67 insertions(+), 53 deletions(-)
diff --git a/drivers/hid/hid-alps.c b/drivers/hid/hid-alps.c
inde
From: Masaki Ota
-To support Alps T4 device, clean up the source code
-Delete unnecessary structure
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 69 +-
1 file changed, 34 insertions(+), 35 deletions(-)
diff --git a/drivers/hid/hid-alps.
From: Masaki Ota
-Add T4 USB device code and Product ID
-This device is used on HP Elite x2 series
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 35 +--
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h | 1 +
3 files changed, 27 insertions(+), 10 d
From: Masaki Ota
-To support Alps T4 device, replace some variables
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 67 --
1 file changed, 27 insertions(+), 40 deletions(-)
diff --git a/drivers/hid/hid-alps.c b/drivers/hid/hid-alps.c
index
From: Masaki Ota
-To support Alps T4 device, add x_min, y_min, max_fingers variables
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 38 --
1 file changed, 24 insertions(+), 14 deletions(-)
diff --git a/drivers/hid/hid-alps.c b/drivers/hid/hid-alps.c
From: Masaki Ota
-Add new U1 device Product ID
-This device is used on HP Elite book x360 series
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 3 +++
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h | 1 +
3 files changed, 5 insertions(+)
diff --git a/drivers/hid/hid-alps.c b/driv
From: Masaki Ota
-Add T4 device code and Product ID
-This device is used on HP EliteBook 1000 series and Zbook Stduio
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 343 ++---
drivers/hid/hid-core.c | 3 +-
drivers/hid/hid-ids.h | 1 +
3
Hi, Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next
to receive the latest Thermal Management updates for v4.14-rc1 with
top-most commit b32b5e14b4e0d40e06f094d2593b447e00acdf37:
Merge branches 'thermal-core', 'thermal-soc', 'thermal-intel' and
'con
Hi, Jiri, Benjamin,
This is the patch for support new Alps HID Touchpad device.
I submitted these patch before, but it was not completed.
So I separate the patch to some parts and release it again.
Best Regards,
Masaki Ota
Currently, Denali NAND driver always expects 3 row address cycle
devices because the driver init code hard-code the register setting.
I will fix it in 2/2.
Many drivers check chip->chipsize if the third row address cycle
is needed or not. This is not nice because 32MB, 128MB are
magic numbers. n
Several drivers check ->chipsize to see if the third row address cycle
is needed. Instead of embedding magic sizes such as 32MB, 128MB in
drivers, introduce a new flag NAND_ROW_ADDR_3 for clean-up. Since
nand_scan_ident() knows well about the device, it can handle this
properly. The flag is set
The register TWO_ROW_ADDR_CYCLES specifies the number of row address
cycles of the device, but it is fixed to 0 in the driver init code
(i.e. always 3 row address cycles).
Reflect the result of nand_scan_ident() to the register setting
in order to support 2 row address cycle devices.
Signed-off-b
[1] fixed weird thing(i.e., reset BDI_CAP_STABLE_WRITES flag
unconditionally whenever revalidat_disk is called) so zram doesn't
need to reset the flag any more whenever revalidating the bdev.
Instead, set the flag just once when the zram device is created.
It shouldn't change any behavior.
[1] 19
If rw-page based fast storage is used for swap devices, we need to
detect it to enhance swap IO operations.
This patch is preparation for optimizing of swap-in operation with
next patch.
Signed-off-by: Minchan Kim
---
include/linux/swap.h | 3 ++-
mm/swapfile.c| 3 +++
2 files changed, 5
By discussion[1], someday we will remove rw_page function. If so, we need
something to detect such super-fast storage which synchronous IO operation
like current rw_page is always win.
This patch introduces BDI_CAP_SYNCHRONOUS_IO to indicate such devices.
With it, we could use various optimization
With fast swap storage, platform want to use swap more aggressively
and swap-in is crucial to application latency.
The rw_page based synchronous devices like zram, pmem and btt are such
fast storage. When I profile swapin performance with zram lz4 decompress
test, S/W overhead is more than 70%. Ma
page_cluster 0 means "we don't want readahead" so in the case,
let's skip the readahead detection logic.
Cc: "Huang, Ying"
Signed-off-by: Minchan Kim
---
include/linux/swap.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/include/linux/swap.h b/include/linux/swap.h
index
This improvement is good. But I have a concern that
the parameters of idr_alloc and idr_alloc_ul are different.
I mean in idr_alloc, we have start and end.
In our new API, we keep them. So our design goal is to
make them consistent. Your new API has its advantage surely.
If you want to change it,
On Tue, 5 Sep 2017 16:57:50 -0500
Tom Zanussi wrote:
> Allow tracing code outside of trace.c to access tracing_set_clock().
>
> Some applications may require a particular clock in order to function
> properly, such as latency calculations.
>
> Also, add an accessor returning the current clock
Hi Tom,
On Tue, 5 Sep 2017 16:57:48 -0500
Tom Zanussi wrote:
> Lookups inflate the hitcount, making it essentially useless. Only
> inserts and updates should really affect the hitcount anyway, so
> explicitly filter lookups out.
>
> Signed-off-by: Tom Zanussi
> ---
> kernel/trace/tracing_ma
From: Shu Wang
The trampoline allocated by function tracer was
overwrite by function_graph tracer, and cause
memory leak. The save_global_trampoline should
save previous trampoline in register_ftrace_graph
and restore it in unregister_ftrace_graph. But
as it implemented, save_global_trampoline wa
polite ping and +cc, thanks!
On 2017/9/11 14:51, Zhou Chengming wrote:
push_rt_task() pick the first pushable task and find an eligible
lowest_rq, then double_lock_balance(rq, lowest_rq). So if
double_lock_balance() unlock the rq (when double_lock_balance() return 1),
we have to check if this ta
Hi,
On 12 September 2017 at 04:11, Franklin S Cooper Jr wrote:
> 66AK2G has I2C instances that are not apart of the ALWAYS_ON power domain
> unlike other Keystone 2 SoCs and OMAPL138. Therefore, pm_runtime
> is required to insure the power domain used by the specific I2C instance is
> properly tu
On 2017/9/11 11:38, Jaegeuk Kim wrote:
> If issue_cond is true, it does double count for # of issued commands.
>
> Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
> ---
> fs/f2fs/segment.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/se
On Tue, 5 Sep 2017 16:57:12 -0500
Tom Zanussi wrote:
> Hi,
>
> This is V2 of the inter-event tracing patchset.
>
> There are too many changes to list in detail, most of them directly
> addressing input from V1, but here are the major changes from V1
> (thanks to everyone who reviewed V1 and th
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Kardonik Michael
> Sent: Tuesday, September 5, 2017 1:27 PM
> To: leoyang...@nxp.com; michael.kardo...@nxp.com; Kirsher, Jeffrey T
> ; Brandeburg, Jesse
> ; Shannon Nelson
> ; Wyborny, Carolyn
> ; Skidmore, D
Hi Martin,
[auto build test WARNING on iio/togreg]
[also build test WARNING on next-20170911]
[cannot apply to v4.13]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Martin-Kepplinger/iio-adc
Hi Baoquan,
At 09/07/2017 01:22 PM, Baoquan He wrote:
On 09/07/17 at 12:19pm, Dou Liyang wrote:
Hi Baoquan
I am wordy one ah:
our target is checking if BIOS supports APIC, no matter what
type(separated/integrated) it is. if not, go to PIC mode.
Let‘s discuss the original logic and the smp_fou
On 2017/9/11 0:20, Yunlong Song wrote:
> Current design will lose recovery process when check_curseg_offset is OK.
>
> Signed-off-by: Yunlong Song
Reviewed-by: Chao Yu
> ---
> fsck/fsck.c | 8 +---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/fsck/fsck.c b/fsck/fsck
On 2017/9/12 7:36, Jerome Glisse wrote:
> On Sun, Sep 10, 2017 at 07:22:58AM +0800, Bob Liu wrote:
>> On Wed, Sep 6, 2017 at 3:36 AM, Jerome Glisse wrote:
>>> On Thu, Jul 20, 2017 at 08:48:20PM -0700, Dan Williams wrote:
On Thu, Jul 20, 2017 at 6:41 PM, Jerome Glisse wrote:
> On Fri, Jul
On 2017/9/10 19:15, Yunlong Song wrote:
> If flag bit to check is in 0xFF00, then the return value will be false,
> this is not correct, so fix it.
>
> Signed-off-by: Yunlong Song
Reviewed-by: Chao Yu
> ---
> fsck/f2fs.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --
To enable jump optimized probe with CONFIG_PREEMPT, use
synchronize_rcu_tasks() to wait for all tasks preempted
on trampoline code back on track.
Since the jump optimized kprobes can replace multiple
instructions, there can be tasks which are interrupted
on the 2nd (or 3rd) instructions. If the kp
This patch enables optprobe even with CONFIG_PREEMPT. The
previous patch is https://lkml.org/lkml/2017/5/24/464 .
With Paul's hack (https://lkml.org/lkml/2017/5/25/435),
now synchronize_rcu_tasks() is translated to synchronize_sched()
when TASKS_RCU=n. So this patch just replace the
synchronize_sc
On Fri, Aug 25, 2017 at 03:40:51PM +0900, Byungchul Park wrote:
> It would be better to try to check other siblings first if
> SD_PREFER_SIBLING is flaged when pushing tasks - migration.
Any opinions?
> Suggested-by: Peter Zijlstra
> Signed-off-by: Byungchul Park
> Reviewed-by: Steven Rostedt (
On Mon, Sep 11, 2017 at 10:06:51PM +0200, Luis R. Rodriguez wrote:
> On Mon, Sep 11, 2017 at 12:29:55PM -0700, Greg Kroah-Hartman wrote:
> > On Mon, Sep 11, 2017 at 07:11:38PM +0200, Luis R. Rodriguez wrote:
> > > On Mon, Sep 11, 2017 at 06:46:47AM -0700, Greg Kroah-Hartman wrote:
> > > > To confir
On (09/11/17 13:45), Petr Mladek wrote:
[..]
> > Except for the second printk line: If you boot with rdinit=/bin/hush
> > then the first time you mount -t devtmpfs /dev /dev after boot (with
> > CONFIG_DEVTMPFS_MOUNT already having mounted it), you get the 0 return
> > value but the last printk() d
On Tue, Sep 05, 2017 at 09:22:39AM +0200, Peter Zijlstra wrote:
> On Tue, Sep 05, 2017 at 11:29:13AM +0900, Byungchul Park wrote:
> > From the point of view of crossrelease, we can never be aware of the
> > release context in advance, until we get to the lock_release().
> > However, this way we can
On Mon, Sep 11, 2017 at 5:13 PM, Gabriel C wrote:
> On 11.09.2017 22:06, Luis R. Rodriguez wrote:
>>
>> On Mon, Sep 11, 2017 at 12:29:55PM -0700, Greg Kroah-Hartman wrote:
>>>
>>> On Mon, Sep 11, 2017 at 07:11:38PM +0200, Luis R. Rodriguez wrote:
On Mon, Sep 11, 2017 at 06:46:47AM -0700,
From: Fenglin Wu
GPIO is expected to be disabled iff PIN_CONFIG_BIAS_HIGH_IMPEDANCE is
configured. Update is_enabled flag in config_set() so that it can
reflect GPIO status correctly. Also modify EN_CTL register based on
is_enabled flag in config_set() to configure the GPIO properly.
Signed-off-
Hi Harsha,
[auto build test WARNING on v4.13]
[also build test WARNING on next-20170911]
[cannot apply to staging/staging-testing]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Harsha-Sharma
From: Andi Kleen
When a PMU is missing print a better error message mentioning
the missing PMU.
% mkdir empty
% mount --bind empty /sys/devices/msr
% perf stat -M Summary true
event syntax error:
'{inst_retired.any,cycles}:W,{cpu_clk_unhalted.thread}:W,{inst_retired.any}:W,{cpu_clk_unhalted.ref
On 11.09.2017 22:06, Luis R. Rodriguez wrote:
On Mon, Sep 11, 2017 at 12:29:55PM -0700, Greg Kroah-Hartman wrote:
On Mon, Sep 11, 2017 at 07:11:38PM +0200, Luis R. Rodriguez wrote:
On Mon, Sep 11, 2017 at 06:46:47AM -0700, Greg Kroah-Hartman wrote:
To confirm, reverting this fixes the problem
1 - 100 of 537 matches
Mail list logo
