From: Florian Westphal <fw@strlen.de>
To: lkp@lists.01.org
Subject: Re: [netfilter: nf_conntrack] b16c29191d: BUG: spinlock recursion on CPU#1, kworker/u4:2/89
Date: Thu, 28 Jan 2016 13:02:41 +0100 [thread overview]
Message-ID: <20160128120241.GA30994@breakpoint.cc> (raw)
In-Reply-To: <56a9f993.7Xz4J9Nb7thQdQrB%fengguang.wu@intel.com>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
kernel test robot <fengguang.wu@intel.com> wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
>
> commit b16c29191dc89bd877af99a7b04ce4866728a3e0
> Author: Sasha Levin <sasha.levin@oracle.com>
> AuthorDate: Mon Jan 18 19:23:51 2016 -0500
> Commit: Pablo Neira Ayuso <pablo@netfilter.org>
> CommitDate: Wed Jan 20 14:15:31 2016 +0100
>
> netfilter: nf_conntrack: use safer way to lock all buckets
Patch errounously converted a spin_unlock to a spin_lock so we have
lock()
foo()
lock()
in ctnl_untimeout().
I'll send a patch soon.
prev parent reply other threads:[~2016-01-28 12:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 11:20 [netfilter: nf_conntrack] b16c29191d: BUG: spinlock recursion on CPU#1, kworker/u4:2/89 kernel test robot
2016-01-28 12:02 ` Florian Westphal [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=20160128120241.GA30994@breakpoint.cc \
--to=fw@strlen.de \
--cc=lkp@lists.01.org \
/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.