From: Michal Hocko <mhocko@kernel.org>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Hugh Dickins <hughd@google.com>, Minchan Kim <minchan@kernel.org>,
"wencongyang (A)" <wencongyang2@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Dmitry Vyukov <dvyukov@google.com>,
zhong jiang <zhongjiang@huawei.com>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm, we use rcu access task_struct in mm_match_cgroup(), but not use rcu free in free_task_struct()
Date: Wed, 24 May 2017 10:29:49 +0200 [thread overview]
Message-ID: <20170524082949.GB14733@dhcp22.suse.cz> (raw)
In-Reply-To: <59253E84.6010506@huawei.com>
On Wed 24-05-17 16:04:20, Xishi Qiu wrote:
> On 2017/5/24 15:49, Vlastimil Babka wrote:
>
> > On 05/24/2017 06:40 AM, Xishi Qiu wrote:
> >> On 2017/5/24 9:40, Xishi Qiu wrote:
> >>
> >>> Hi, I find we use rcu access task_struct in mm_match_cgroup(), but not use
> >>> rcu free in free_task_struct(), is it right?
> >>>
> >>> Here is the backtrace.
> >
> > Can you post the whole oops, including kernel version etc? Is it the
> > same 3.10 RH kernel as in the other report?
> >
>
> Hi Vlastimil,
>
> Yes, it's RHEL 7.2
Please contact Redhat for the support of this kernel. Feel free to
report the issue if it persists with the current vanilla kernel. It is
really hard for us to help you with a custom patched and an old kernel.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-05-24 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 1:40 Xishi Qiu
2017-05-24 4:40 ` Xishi Qiu
2017-05-24 7:49 ` Vlastimil Babka
2017-05-24 8:04 ` Xishi Qiu
2017-05-24 8:29 ` Michal Hocko [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=20170524082949.GB14733@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=dvyukov@google.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=minchan@kernel.org \
--cc=qiuxishi@huawei.com \
--cc=vbabka@suse.cz \
--cc=wencongyang2@huawei.com \
--cc=zhongjiang@huawei.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