From: Oleg Nesterov <oleg@redhat.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Song Liu <songliubraving@fb.com>,
Kan Liang <kan.liang@linux.intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
syzkaller-bugs@googlegroups.com
Subject: Re: Reminder: 22 open syzbot bugs in perf subsystem
Date: Wed, 3 Jul 2019 13:34:37 +0200 [thread overview]
Message-ID: <20190703113436.GA21672@redhat.com> (raw)
In-Reply-To: <20190703041918.GB633@sol.localdomain>
On 07/02, Eric Biggers wrote:
>
> Even if it's a lockdep false positive you can't ignore it. People rely on
> lockdep to find bugs, and they will keep sending you bug reports. So someone
> has to fix something. Did you see Oleg's suggestion to change mmput() to
> mmput_async() in binder_alloc_free_page()?
> https://marc.info/?l=linux-kernel&m=155119805728815&w=2
> If you believe that is the right fix, I can reassign this report to binder
> subsystem and nag the binder maintainers instead...
Yes, please. To me s/mmput/mmput_async/ looks like the "obviously correct fix",
but of course I don't understand this code and can't test it.
Oleg.
prev parent reply other threads:[~2019-07-03 11:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 5:43 Reminder: 22 open syzbot bugs in perf subsystem Eric Biggers
2019-07-03 3:39 ` Ravi Bangoria
2019-07-03 3:55 ` Eric Biggers
2019-07-03 3:59 ` Ravi Bangoria
2019-07-03 4:19 ` Eric Biggers
2019-07-03 4:36 ` Ravi Bangoria
2019-07-03 11:34 ` Oleg Nesterov [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=20190703113436.GA21672@redhat.com \
--to=oleg@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ebiggers@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox