Shaun Crampton | 4 Aug 15:42 2015

veths often slow to come up

Please CC me on any responses, thanks.

Setting both ends of a veth to be oper UP completes very quickly but I
find that pings only start flowing over the veth after about a second.
This seems to correlate with the NO-CARRIER flag being set or the
interface being in "state UNKNOWN" or "state DOWN² for about a second
(demo script below).

If I run the script repeatedly then sometimes it completes very quickly on
subsequent runs as if there¹s a hot cache somewhere.

Could this be a bug or is there a configuration to speed this up?  Seems
odd that it¹s almost exactly 1s on the first run.

Seen on these kernels:
* 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
* 4.0.9-coreos #2 SMP Thu Jul 30 01:07:55 UTC 2015 x86_64 Intel(R) Xeon(R)
CPU  <at>  2.50GHz GenuineIntel GNU/Linux



Running my test script below (Assumes veth0/1 do not already exist):

$ sudo ./
Time to create veth:

real	0m0.019s
(Continue reading)

Chris Metcalf | 4 Aug 15:46 2015

Re: [tip:sched/core] sched, tile: Remove finish_arch_switch


I already have the appended commit in a modified form in the linux-tile
tree ready to be pushed to 4.3.  Can you drop it from your series?


On 8/4/2015 4:50 AM, tip-bot for Chris Metcalf wrote:
> Commit-ID:  fe363adb922583bacfbd5a30a4c773ccff9bb393
> Gitweb:
> Author:     Chris Metcalf <cmetcalf <at>>
> AuthorDate: Wed, 29 Jul 2015 13:06:29 -0400
> Committer:  Ingo Molnar <mingo <at>>
> CommitDate: Tue, 4 Aug 2015 09:38:18 +0200
> sched, tile: Remove finish_arch_switch
> Move the simulator bits into switch_to() and use
> finish_arch_post_lock_switch() for the homecache migration bits.
> Signed-off-by: Chris Metcalf <cmetcalf <at>>
> Signed-off-by: Peter Zijlstra (Intel) <peterz <at>>
> Cc: Linus Torvalds <torvalds <at>>
> Cc: Mike Galbraith <efault <at>>
> Cc: Peter Zijlstra <peterz <at>>
> Cc: Thomas Gleixner <tglx <at>>
> Cc: linux-kernel <at>
> Signed-off-by: Ingo Molnar <mingo <at>>
> ---
>   arch/tile/include/asm/switch_to.h | 10 +++-------
(Continue reading)

Geert Uytterhoeven | 4 Aug 15:22 2015

[PATCH 0/2] drm/fb-helper: Silence defined but not used warning

From: Geert Uytterhoeven <geert+renesas <at>>



    drivers/gpu/drm/drm_fb_helper.c:390:13: warning: 'drm_fb_helper_force_kernel_mode' defined but
not used [-Wunused-function]
     static bool drm_fb_helper_force_kernel_mode(void)

As just silencing this warning would require moving two functions (one
of them having obsolete documentation) inside the #ifdef, I fixed the
documentation first.

This patch series is against next-20150803.

Geert Uytterhoeven (2):
  drm/fb-helper: Clarify drm_fb_helper_restore_fbdev_mode*()
  drm/fb-helper: Move drm_fb_helper_force_kernel_mode() inside #ifdef

 drivers/gpu/drm/drm_fb_helper.c | 71 ++++++++++++++++-------------------------
 1 file changed, 28 insertions(+), 43 deletions(-)




(Continue reading)

Nicolas Schichan | 4 Aug 15:19 2015

[PATCH V2 net-next 0/6] test_bpf improvements


Please find below the patch series with my latest changes to test_bpf.

The first patch checks for unexpected NULL generated skbs before
running the filter.

The second patch adds the possibility for tests to generate fragmented

The third patch tests LD_ABS and LD_IND on fragmented skbs.

The fourth patch adds the possibility to restrict the tests being run
by specifying the name/id/range of the test(s) to run via module

The fifth patch tests LD_ABS and LD_IND on non fragmented skbs with
various sizes and alignments.

The sixth and final patch checks that the interpreter or JIT correctly
resets A and X to 0.

This serie is against today's net-next tree.

Changes in V2:

* move declaration of 'ptr' in if() block in patch 2/6.

* fix various typos in patch 4/6

(Continue reading)

Shraddha Barke | 4 Aug 15:06 2015

[PATCH v2 1/3] Staging: lustre: Replace comma with a semicolon

Replace comma between expression statements by a semicolon.
The semantic patch used is as follows:

 <at>  <at> 
expression e1,e2;
 <at>  <at> 
- ,
+ ;
Changes in v2:
  -No changes made.

 drivers/staging/lustre/lustre/libcfs/libcfs_string.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/staging/lustre/lustre/libcfs/libcfs_string.c b/drivers/staging/lustre/lustre/libcfs/libcfs_string.c
index 4dde8e0..efe5e66 100644
--- a/drivers/staging/lustre/lustre/libcfs/libcfs_string.c
+++ b/drivers/staging/lustre/lustre/libcfs/libcfs_string.c
 <at>  <at>  -400,7 +400,7  <at>  <at>  cfs_expr_list_free(struct cfs_expr_list *expr_list)
 		struct cfs_range_expr *expr;

 		expr = list_entry(expr_list->,
-				      struct cfs_range_expr, re_link),
+				      struct cfs_range_expr, re_link);
 		LIBCFS_FREE(expr, sizeof(*expr));
(Continue reading)

Oleg Nesterov | 4 Aug 15:00 2015

qrwlock && read-after-read

I am working on the (off-topic) bug report which motivated me to
look at locking/qrwlock.c and it seems to me there is a problem
with the queued rwlocks.

Unless I am totally confused read-after-read is no longer valid,
write_lock() stops the new readers. And lockdep doesn't know this,
read_lock()->rwlock_acquire_read() doesn't match the reality. The
code doing


can deadlock if another CPU does write_lock(X) in between. This
was fine before rwlock_t was changed to use qrwlock.

A nested read_lock() in interrupt should be fine though, and this
is because queue_read_lock_slowpath() "ignores" _QW_WAITING if

This means that rwlock_t has the really strange semantics imho,
and again, it is not lockdep-friendly.

What do you think we can/should do? Or did I misread this code?


Scot Doyle | 4 Aug 14:33 2015

[PATCH] fbcon: unconditionally initialize cursor blink interval

A sun7i-a20-olinuxino-micro fails to boot when kernel parameter
vt.global_cursor_default=0. The value is copied to vc->vc_deccm
causing the initialization of ops->cur_blink_jiffies to be skipped.
Unconditionally initialize it.

Reported-and-tested-by: Jonathan Liu <net147 <at>>
Signed-off-by: Scot Doyle <lkml14 <at>>
 drivers/video/console/fbcon.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/drivers/video/console/fbcon.c b/drivers/video/console/fbcon.c
index 658c34b..1aaf893 100644
--- a/drivers/video/console/fbcon.c
+++ b/drivers/video/console/fbcon.c
 <at>  <at>  -1306,10 +1306,11  <at>  <at>  static void fbcon_cursor(struct vc_data *vc, int mode)
 	int y;
  	int c = scr_readw((u16 *) vc->vc_pos);

+	ops->cur_blink_jiffies = msecs_to_jiffies(vc->vc_cur_blink_ms);
 	if (fbcon_is_inactive(vc, info) || vc->vc_deccm != 1)

-	ops->cur_blink_jiffies = msecs_to_jiffies(vc->vc_cur_blink_ms);
 	if (vc->vc_cursor_type & 0x10)

(Continue reading)

Wang Xiaoqiang | 4 Aug 14:20 2015

[PATCH] memory-failure/hwpoison_user_mappings: move the comment about swap cache pages' check to proper location

Hi Naoya,

This patch just move the comment about swap cache pages' check to the
proper location in 'hwpoison_user_mappings' function.

Signed-off-by: Wang Xiaoqiang <wangxq10 <at>>
 mm/memory-failure.c |    8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index 1cf7f29..3253abb 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
 <at>  <at>  -945,10 +945,6  <at>  <at>  static int hwpoison_user_mappings(struct page *p, unsigned long pfn,
 	if (!(PageLRU(hpage) || PageHuge(p)))
 		return SWAP_SUCCESS;

-	/*
-	 * This check implies we don't kill processes if their pages
-	 * are in the swap cache early. Those are always late kills.
-	 */
 	if (!page_mapped(hpage))
 		return SWAP_SUCCESS;

 <at>  <at>  -957,6 +953,10  <at>  <at>  static int hwpoison_user_mappings(struct page *p, unsigned long pfn,
 		return SWAP_FAIL;

+	/*
(Continue reading)

Julia Lawall | 4 Aug 14:00 2015

Re: [PATCH 1/3] Staging: lustre: Replace comma with a semicolon

On Tue, 4 Aug 2015, Shraddha Barke wrote:

> Should I resend the entire patch series as v2 ? Or only the first two
> patches?

The entire series.  You can say under the --- that there is no change in
the cases where there is no change.

Eddie Huang | 4 Aug 13:44 2015

[PATCH 0/2] Mediatek I2C fixup

This series provide two patches to optimize mediatek i2c driver.
The first patch will reset dma hardware in init function to make sure
hardware work in good state. The second patch fix i2c interrupt handling
for ACK error. All these patches base on v4.2-rc1.

Eddie Huang (2):
  i2c: mediatek: Reset DMA engine in hardware init function
  i2c: mediatek: Fixup i2c ack error interrupt handling

 drivers/i2c/busses/i2c-mt65xx.c |   28 ++++++++++++++++++++--------
 1 file changed, 20 insertions(+), 8 deletions(-)



Admin Portal | 4 Aug 12:33 2015

Update Account

This is to inform you that your password will expire in 3 days, please update your account or your new mails
will remain pending.

Note: Open

Open to update now