netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: Vlad Buslov <vladbu@mellanox.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
	David Miller <davem@davemloft.net>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH net-next] net: sched: act_ife: disable bh when taking ife_mod_lock
Date: Mon, 13 Aug 2018 16:18:29 -0700	[thread overview]
Message-ID: <CAM_iQpUk6vo_9StceKQ+RLgB6FN_+yxPGC6BSeKsKwpWjGdw7Q@mail.gmail.com> (raw)
In-Reply-To: <1534180811-10416-1-git-send-email-vladbu@mellanox.com>

Hi, Vlad,

Could you help to test my fixes?

I just pushed them into my own git repo:
https://github.com/congwang/linux/commits/net-sched-fixes

Particularly, this is the revert:
https://github.com/congwang/linux/commit/b3f51c4ab8272cc8d3244848e528fce1426c4659
and this is my fix for the lockdep warning you reported:
https://github.com/congwang/linux/commit/ecadcde94919183e9f0d5bc376f05e731baf2661

I don't have environment to test ife modules.

BTW, this is the fix for the deadlock I spotted:
https://github.com/congwang/linux/commit/44f3d7f5b6ed2d4a46177e6c658fa23b76141afa

Thanks!

  parent reply	other threads:[~2018-08-14  2:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13 17:20 [PATCH net-next] net: sched: act_ife: disable bh when taking ife_mod_lock Vlad Buslov
2018-08-13 17:23 ` Jamal Hadi Salim
2018-08-13 18:33   ` Vlad Buslov
2018-08-13 17:26 ` Vlad Buslov
2018-08-13 18:27   ` David Miller
2018-08-13 18:45 ` David Miller
2018-08-13 19:16 ` Cong Wang
2018-08-13 19:21   ` Cong Wang
2018-08-13 22:53   ` David Miller
2018-08-13 23:01     ` Cong Wang
2018-08-13 23:18 ` Cong Wang [this message]
2018-08-14 17:34   ` Vlad Buslov
2018-08-14 22:52     ` Cong Wang

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=CAM_iQpUk6vo_9StceKQ+RLgB6FN_+yxPGC6BSeKsKwpWjGdw7Q@mail.gmail.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=vladbu@mellanox.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).