From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
To: Akinobu Mita <akinobu.mita@gmail.com>,
Nikolay Aleksandrov <razor@blackwall.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
shm@cumulusnetworks.com, gospo@cumulusnetworks.com,
roopa@cumulusnetworks.com, dsa@cumulusnetworks.com,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] net: add support for netdev notifier error injection
Date: Tue, 1 Dec 2015 00:49:55 +0100 [thread overview]
Message-ID: <565CE0A3.2010403@cumulusnetworks.com> (raw)
In-Reply-To: <CAC5umyjONtF9r=Ox1-mMS-vzxp2j-fk+VX1wWWVvWvyOxWPbiQ@mail.gmail.com>
On 12/01/2015 12:48 AM, Akinobu Mita wrote:
> 2015-11-28 21:45 GMT+09:00 Nikolay Aleksandrov <razor@blackwall.org>:
>> From: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
>>
>> This module allows to insert errors in some of netdevice's notifier
>> events. All network drivers use these notifiers to signal various events
>> and to check if they are allowed, e.g. PRECHANGEMTU and CHANGEMTU
>> afterwards. Until recently I had to run failure tests by injecting
>> a custom module, but now this infrastructure makes it trivial to test
>> these failure paths. Some of the recent bugs I fixed were found using
>> this module.
>> Here's an example:
>> $ cd /sys/kernel/debug/notifier-error-inject/netdev
>> $ echo -22 > actions/NETDEV_CHANGEMTU/error
>> $ ip link set eth0 mtu 1024
>> RTNETLINK answers: Invalid argument
>
> This patch looks good to me. It would be nice if you add tools like
> tools/testing/selftests/cpu-hotplug/cpu-on-off-test.sh for this feature.
>
Thanks for reviewing and noted. I'll take a look and make some tests.
Do you mind if I post it as a follow-up ?
Cheers,
Nik
next prev parent reply other threads:[~2015-11-30 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 12:45 [PATCH] net: add support for netdev notifier error injection Nikolay Aleksandrov
2015-11-30 23:48 ` Akinobu Mita
2015-11-30 23:49 ` Nikolay Aleksandrov [this message]
2015-12-01 20:32 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=565CE0A3.2010403@cumulusnetworks.com \
--to=nikolay@cumulusnetworks.com \
--cc=akinobu.mita@gmail.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=gospo@cumulusnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=roopa@cumulusnetworks.com \
--cc=shm@cumulusnetworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.