From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux- stable <stable@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
open list <linux-kernel@vger.kernel.org>,
John Stultz <john.stultz@linaro.org>,
Todd Kjos <tkjos@google.com>, Shuah Khan <shuah@kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
tkjos@android.com, ardb@kernel.org,
Kees Cook <keescook@chromium.org>,
lkft-triage@lists.linaro.org, Basil Eljuse <Basil.Eljuse@arm.com>,
YongQin Liu <yongqin.liu@linaro.org>
Subject: Re: [stable-rc-5.4 and 5.5 ] WARNING: CPU: 3 PID: 2548 at /usr/src/kernel/lib/refcount.c:28 refcount_warn_saturate
Date: Tue, 17 Mar 2020 09:29:10 +0100 [thread overview]
Message-ID: <20200317082910.GB1063543@kroah.com> (raw)
In-Reply-To: <CA+G9fYu06RPexAK-4huCSwYC4=FkuH2QduVpxOgG43ojX2jyBA@mail.gmail.com>
On Tue, Mar 17, 2020 at 01:15:40PM +0530, Naresh Kamboju wrote:
> While running selftests binderfs_test on stable rc 5.4 and 5.5
> branches the following
> warning on arm64, arm, x86_64 and i386.
>
> This warning was noticed on Linus's tree and reported [1] and then
> Christian Brauner investigated this problem.
>
> FYI, We are running selftests source from stable rc 5.5 branch.
There is a fix in my tree that will go to Linus for this this week.
thanks,
greg k-h
prev parent reply other threads:[~2020-03-17 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 7:45 Naresh Kamboju
2020-03-17 8:26 ` Christian Brauner
2020-03-17 8:29 ` Greg Kroah-Hartman [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=20200317082910.GB1063543@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Basil.Eljuse@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ardb@kernel.org \
--cc=christian.brauner@ubuntu.com \
--cc=john.stultz@linaro.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tkjos@android.com \
--cc=tkjos@google.com \
--cc=yongqin.liu@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®