From: Paolo Bonzini <pbonzini@redhat.com>
To: "Roman Kagan" <rkagan@virtuozzo.com>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Matthew Wilcox" <mawilcox@microsoft.com>,
syzbot <syzbot+35666cba7f0a337e2e79@syzkaller.appspotmail.com>,
"H. Peter Anvin" <hpa@zytor.com>,
"KVM list" <kvm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Cathy Avery" <cavery@redhat.com>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] idr: fix invalid ptr dereference on item delete
Date: Fri, 11 May 2018 11:12:49 +0200 [thread overview]
Message-ID: <2516f92a-a130-1c90-ff3c-dcff14d5c577@redhat.com> (raw)
In-Reply-To: <20180511055704.GB12563@rkaganip.lan>
On 11/05/2018 07:57, Roman Kagan wrote:
>>> Should radix-tree be compilable in userspace, so that we can add unit
>>> tests for it?...
>> Good point.
>>
>> For my education, what/where are the tests that run as user-space code?
> Actually there are userspace tests for it under tools/tests/radix-tree,
> but I didn't manage to get them to build. Looks like the recent
> introduction of a spin_lock in the radix_tree structure (for XArray
> work?) broke them.
Oh cool, at least it means it was a good suggestion. :)
Paolo
next prev parent reply other threads:[~2018-05-11 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 19:16 [PATCH] idr: fix invalid ptr dereference on item delete Roman Kagan
2018-05-10 23:54 ` Paolo Bonzini
2018-05-11 5:40 ` Dmitry Vyukov
2018-05-11 5:57 ` Roman Kagan
2018-05-11 9:12 ` Paolo Bonzini [this message]
2018-05-18 20:29 ` Roman Kagan
2018-05-18 17:50 Matthew Wilcox
2018-05-18 20:23 ` Roman Kagan
2018-05-19 0:31 ` Matthew Wilcox
2018-05-18 22:31 ` Andrew Morton
2018-05-19 0:28 ` Matthew Wilcox
2018-05-19 6:26 ` Roman Kagan
2018-05-19 14:14 ` Matthew Wilcox
2018-05-21 19:13 ` Andrew Morton
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=2516f92a-a130-1c90-ff3c-dcff14d5c577@redhat.com \
--to=pbonzini@redhat.com \
--cc=cavery@redhat.com \
--cc=dvyukov@google.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=mingo@redhat.com \
--cc=rkagan@virtuozzo.com \
--cc=rkrcmar@redhat.com \
--cc=stable@vger.kernel.org \
--cc=syzbot+35666cba7f0a337e2e79@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--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).