All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: xiangxia.m.yue@gmail.com
Cc: syzbot+7ef50afd3a211f879112@syzkaller.appspotmail.com,
	dev@openvswitch.org, kuba@kernel.org,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	pshelar@ovn.org, syzkaller-bugs@googlegroups.com,
	yihung.wei@gmail.com
Subject: Re: [PATCH] net: openvswitch: ovs_ct_exit to be done under ovs_lock
Date: Mon, 20 Apr 2020 11:00:00 -0700 (PDT)	[thread overview]
Message-ID: <20200420.110000.944435201264166335.davem@davemloft.net> (raw)
In-Reply-To: <1587063451-54027-1-git-send-email-xiangxia.m.yue@gmail.com>

From: xiangxia.m.yue@gmail.com
Date: Fri, 17 Apr 2020 02:57:31 +0800

> From: Tonghao Zhang <xiangxia.m.yue@gmail.com>
> 
> syzbot wrote:
 ...
> To avoid that warning, invoke the ovs_ct_exit under ovs_lock and add
> lockdep_ovsl_is_held as optional lockdep expression.
> 
> Link: https://lore.kernel.org/lkml/000000000000e642a905a0cbee6e@google.com
> Fixes: 11efd5cb04a1 ("openvswitch: Support conntrack zone limit")
> Cc: Pravin B Shelar <pshelar@ovn.org> 
> Cc: Yi-Hung Wei <yihung.wei@gmail.com>
> Reported-by: syzbot+7ef50afd3a211f879112@syzkaller.appspotmail.com
> Signed-off-by: Tonghao Zhang <xiangxia.m.yue@gmail.com>

Applied and queued up for -stable, thanks.

  parent reply	other threads:[~2020-04-20 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14  7:57 linux-next test error: WARNING: suspicious RCU usage in ovs_ct_exit syzbot
2020-04-16 18:57 ` [PATCH] net: openvswitch: ovs_ct_exit to be done under ovs_lock xiangxia.m.yue
2020-04-19 17:32   ` Pravin Shelar
2020-04-20 18:00   ` David Miller [this message]
2020-04-18  7:02 ` linux-next test error: WARNING: suspicious RCU usage in ovs_ct_exit Dmitry Vyukov
2020-04-20  1:59   ` Qian Cai

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=20200420.110000.944435201264166335.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=dev@openvswitch.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@ovn.org \
    --cc=syzbot+7ef50afd3a211f879112@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=xiangxia.m.yue@gmail.com \
    --cc=yihung.wei@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 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.