From: Ingo Molnar <mingo@kernel.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [v4.6-rc7-183-g1410b74e4061]
Date: Mon, 16 May 2016 12:50:45 +0200 [thread overview]
Message-ID: <20160516105045.GA19189@gmail.com> (raw)
In-Reply-To: <CA+icZUXF9DkymNNGwP8zzmKY9PRAPGFZ+7p9En1xy80FcX_RRw@mail.gmail.com>
* Sedat Dilek <sedat.dilek@gmail.com> wrote:
> Hi,
>
> as Linux v4.6 is very near, I decided to write this bug report (only
> drunk one coffee).
>
> First, I am not absolutely sure if this is a real issue as...
> #1: This is only a (lockdep) warning.
> #2: I have not a "vanilla" Linux v4.6-rc7+ here (see P.S. and attached patch)
Having such a kernel base is certainly not helpful to the quality of your report,
please try to reproduce under the vanilla kernel.
> For a more helpful feedback I should test a...
> #1: vanilla v4.6-rc7-183-g1410b74e4061
I'd suggest v4.6 plus this debug patch from Peter:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1142352.html
... to see whether something fishy is going on.
Thanks,
Ingo
next prev parent reply other threads:[~2016-05-16 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-14 9:22 [v4.6-rc7-183-g1410b74e4061] Sedat Dilek
2016-05-14 16:46 ` [v4.6-rc7-183-g1410b74e4061] Eric Dumazet
2016-05-16 10:50 ` Ingo Molnar [this message]
2016-05-16 17:42 ` [v4.6-rc7-183-g1410b74e4061] Sedat Dilek
2016-05-16 17:57 ` [v4.6-rc7-183-g1410b74e4061] Peter Zijlstra
2016-05-16 18:11 ` [v4.6-rc7-183-g1410b74e4061] Sedat Dilek
2016-05-22 9:16 ` [v4.6-rc7-183-g1410b74e4061] Sedat Dilek
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=20160516105045.GA19189@gmail.com \
--to=mingo@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=sedat.dilek@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).