From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: dvyukov@google.com, syzkaller@googlegroups.com
Cc: hannes@cmpxchg.org, cgroups@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, kcc@google.com, glider@google.com,
sasha.levin@oracle.com, edumazet@google.com, gthelen@google.com,
tj@kernel.org, peterz@infradead.org
Subject: Re: WARNING in handle_mm_fault
Date: Thu, 26 Nov 2015 20:33:05 +0900 [thread overview]
Message-ID: <201511262033.EAB48965.FVJOOOMLFHStFQ@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <CACT4Y+Y0EESD_HhgGE2pWPqfJsDgvSny=ZMfP1ewaSzd6z_bLg@mail.gmail.com>
Dmitry Vyukov wrote:
> On Wed, Nov 25, 2015 at 6:37 PM, Michal Hocko <mhocko@kernel.org> wrote:
> > On Wed 25-11-15 18:21:02, Dmitry Vyukov wrote:
> > [...]
> >> I have some progress.
> >
> > Please have a look at Peter's patch posted in the original email thread
> > http://lkml.kernel.org/r/20151125150207.GM11639@twins.programming.kicks-ass.net
>
> Yes, I've posted there as well. That patch should help.
>
OK. This bug seems to exist since commit ca94c442535a "sched: Introduce
SCHED_RESET_ON_FORK scheduling policy flag". Should
Cc: <stable@vger.kernel.org> [2.6.32+]
line be added?
By the way, does use of "unsigned char" than "unsigned" save some bytes?
Simply trying not to change the size of "struct task_struct"...
According to C99, only "unsigned int", "signed int" and "_Bool" are
allowed. But many compilers accept other types such as "unsigned char",
given that we watch out for compiler bugs.
--
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>
next prev parent reply other threads:[~2015-11-26 11:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 13:50 Dmitry Vyukov
2015-11-24 22:31 ` Johannes Weiner
2015-11-25 13:05 ` Dmitry Vyukov
2015-11-25 13:12 ` Dmitry Vyukov
2015-11-25 8:44 ` Michal Hocko
2015-11-25 10:51 ` Tetsuo Handa
2015-11-25 13:08 ` Dmitry Vyukov
2015-11-25 15:27 ` Tetsuo Handa
2015-11-25 17:21 ` Dmitry Vyukov
2015-11-25 17:32 ` Dmitry Vyukov
2015-11-25 17:37 ` Michal Hocko
2015-11-25 17:44 ` Dmitry Vyukov
2015-11-26 11:33 ` Tetsuo Handa [this message]
2015-11-30 16:20 ` Peter Zijlstra
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=201511262033.EAB48965.FVJOOOMLFHStFQ@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=glider@google.com \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=kcc@google.com \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=sasha.levin@oracle.com \
--cc=syzkaller@googlegroups.com \
--cc=tj@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