From: Ivan Vecera <ivecera@redhat.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
saeed@kernel.org, Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH net] team: postpone features update to avoid deadlock
Date: Thu, 21 Jan 2021 11:29:37 +0100 [thread overview]
Message-ID: <20210121112937.11b72ea6@ceranb> (raw)
In-Reply-To: <CAM_iQpUqdm-mpSUdsxEtLnq6GwhN=YL+ub--8N0aGxtM+PRfAQ@mail.gmail.com>
On Wed, 20 Jan 2021 15:18:20 -0800
Cong Wang <xiyou.wangcong@gmail.com> wrote:
> On Wed, Jan 20, 2021 at 4:56 AM Ivan Vecera <ivecera@redhat.com> wrote:
> >
> > To fix the problem __team_compute_features() needs to be postponed
> > for these cases.
>
> Is there any user-visible effect after deferring this feature change?
>
An user should not notice this change.
I.
next prev parent reply other threads:[~2021-01-21 13:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 12:23 [PATCH net] team: postpone features update to avoid deadlock Ivan Vecera
2021-01-20 13:40 ` Jiri Pirko
2021-01-20 23:18 ` Cong Wang
2021-01-21 10:29 ` Ivan Vecera [this message]
2021-01-22 2:34 ` Jakub Kicinski
2021-01-22 8:30 ` Ivan Vecera
2021-01-22 18:03 ` Jakub Kicinski
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=20210121112937.11b72ea6@ceranb \
--to=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=saeed@kernel.org \
--cc=xiyou.wangcong@gmail.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).