From: Taehee Yoo <ap420073@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: wangxiaogang3@huawei.com, dsahern@kernel.org, shrijeet@gmail.com,
Netdev <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org, hujunwei4@huawei.com,
xuhanbing@huawei.com
Subject: Re: [PATCH] vrf: Fix possible NULL pointer oops when delete nic
Date: Sun, 17 Nov 2019 15:17:38 +0900 [thread overview]
Message-ID: <CAMArcTWUV1iZuACs0FTwC1jdFYSupPNsaV+9E_HQta1Vdyh6gg@mail.gmail.com> (raw)
In-Reply-To: <20191116.125316.1859622454319892445.davem@davemloft.net>
On Sun, 17 Nov 2019 at 05:53, David Miller <davem@davemloft.net> wrote:
>
Hi David,
Thank you for Ccing!
> From: "wangxiaogang (F)" <wangxiaogang3@huawei.com>
> Date: Fri, 15 Nov 2019 14:22:56 +0800
>
> > From: XiaoGang Wang <wangxiaogang3@huawei.com>
> >
> > Recently we get a crash when access illegal address (0xc0),
> > which will occasionally appear when deleting a physical NIC with vrf.
> >
> > [166603.826737]hinic 0000:43:00.4 eth-s3: Failed to cycle device eth-s3;
> > route tables might be wrong!
> > .....
> > [166603.828018]WARNING: CPU: 135 PID: 15382at net/core/dev.c:6875
> > __netdev_adjacent_dev_remove.constprop.40+0x1e0/0x1e8
> > ......
>
> Taehee-ssi, please take a look at this.
>
> It is believed that this may be caused by the adjacency fixes you made
> recently.
>
I will take a look at this
Thank you!
> Thank you.
prev parent reply other threads:[~2019-11-17 6:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 6:22 [PATCH] vrf: Fix possible NULL pointer oops when delete nic wangxiaogang (F)
2019-11-15 13:14 ` David Ahern
2019-11-18 3:15 ` wangxiaogang (F)
2019-11-18 3:22 ` David Ahern
2019-11-15 16:59 ` David Ahern
2019-11-18 3:16 ` wangxiaogang (F)
2019-11-18 3:21 ` David Ahern
2019-11-16 20:53 ` David Miller
2019-11-17 6:17 ` Taehee Yoo [this message]
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=CAMArcTWUV1iZuACs0FTwC1jdFYSupPNsaV+9E_HQta1Vdyh6gg@mail.gmail.com \
--to=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=hujunwei4@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shrijeet@gmail.com \
--cc=wangxiaogang3@huawei.com \
--cc=xuhanbing@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).