From: Ingo Molnar <mingo@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Kirill Smelkov <kirr@nexedi.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [GIT PULL] liblockdep fixes for v3.19
Date: Tue, 23 Dec 2014 10:29:11 +0100 [thread overview]
Message-ID: <20141223092911.GA9246@gmail.com> (raw)
In-Reply-To: <549781C3.50407@oracle.com>
* Sasha Levin <sasha.levin@oracle.com> wrote:
> Hi Ingo,
>
> A small (but important) fix to the way we detect freeing live locks. We would
> pass a wrong memory region when testing for locks inside freed memory spaces,
> which would trigger false positives.
>
>
> Thanks,
> Sasha
>
> The following changes since commit b2776bf7149bddd1f4161f14f79520f17fc1d71d:
>
> Linux 3.18 (2014-12-07 14:21:05 -0800)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux.git liblockdep-fixes-3.19
>
> for you to fetch changes up to 95bfdf23e4d59099340c01064f39e7f6875c02bc:
>
> tools/liblockdep: Fix debug_check thinko in mutex destroy (2014-12-19 15:50:55 -0500)
>
> ----------------------------------------------------------------
> Kirill Smelkov (1):
> tools/liblockdep: Fix debug_check thinko in mutex destroy
>
> tools/lib/lockdep/preload.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Pulled, thanks Sasha!
Ingo
next prev parent reply other threads:[~2014-12-23 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 2:28 [GIT PULL] liblockdep fixes for v3.19 Sasha Levin
2014-12-23 9:29 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-01 12:46 Sasha Levin
2015-02-03 11:26 ` Ingo Molnar
2015-02-03 12:59 ` Sasha Levin
2015-02-04 5:59 ` Ingo Molnar
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=20141223092911.GA9246@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=kirr@nexedi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.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.