netdev - Re: [PATCH net-next v2] bonding: check slave set command firstly

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20190214.083651.1886161133830865121.davem@davemloft.net>
Date:   Thu, 14 Feb 2019 08:36:51 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     xiangxia.m.yue@...il.com
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2] bonding: check slave set command firstly

From: xiangxia.m.yue@...il.com
Date: Mon, 11 Feb 2019 10:49:48 -0800

> From: Tonghao Zhang <xiangxia.m.yue@...il.com>
> 
> This patch is a little improvement. If user use the
> command shown as below, we should print the info [1]
> instead of [2]. The eth0 exists actually, and it may
> confuse user.
> 
> $ echo "eth0" > /sys/class/net/bond4/bonding/slaves
> 
> [1] "bond4: no command found in slaves file - use +ifname or -ifname"
> [2] "write error: No such device"
> 
> Signed-off-by: Tonghao Zhang <xiangxia.m.yue@...il.com>

Applied, but would you please fix the dates on your submissions?

Because the dates in your patch postings are in the past, patchwork
puts your work at the tail of my patch queue instead of the front.

Thank you.