netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ivecera@redhat.com
Cc: poros@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net] be2net: Fix NULL pointer dereference in be_tx_timeout()
Date: Wed, 28 Nov 2018 11:00:20 -0800 (PST)	[thread overview]
Message-ID: <20181128.110020.1466319069502491864.davem@davemloft.net> (raw)
In-Reply-To: <932ae382-a1fe-c7ad-a9b3-e728ed6c1176@redhat.com>

From: Ivan Vecera <ivecera@redhat.com>
Date: Wed, 28 Nov 2018 11:12:22 +0100

> On 27. 11. 18 23:51, David Miller wrote:
>> From: Petr Oros <poros@redhat.com>
>> Date: Thu, 22 Nov 2018 15:24:07 +0100
>> 
>>> @@ -4700,8 +4700,11 @@ int be_update_queues(struct be_adapter
>>> *adapter)
>>>   	struct net_device *netdev = adapter->netdev;
>>>   	int status;
>>>   -	if (netif_running(netdev))
>>> +	if (netif_running(netdev)) {
>>> +		/* prevent netdev watchdog during tx queue destroy */
>>> +		netif_carrier_off(netdev);
>>>   		be_close(netdev);
>>> +	}
>> This will make userspace networking daemons will think that the link
>> went down.
>> This absolutely should not be a side effect of making a simple
>> TX queue configuration change via ethtool.
>> 
> 
> Yes, you're right Dave. But the same thing (netif_carrier_off()) is
> done by number of other drivers (igb, tg3, ixgbe...) during
> .set_channels() callback. The patch that Petr sent does the
> practically the same thing like this one:

Bug exist in other drivers, thanks for reporting that.

It doesn't mean you should add the same bug here as well.

  reply	other threads:[~2018-11-29  6:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-22 14:24 [PATCH net] be2net: Fix NULL pointer dereference in be_tx_timeout() Petr Oros
2018-11-27 22:51 ` David Miller
2018-11-28 10:12   ` Ivan Vecera
2018-11-28 19:00     ` David Miller [this message]
2018-11-28 19:29       ` Ivan Vecera
2018-11-28 19: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=20181128.110020.1466319069502491864.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ivecera@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=poros@redhat.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).