From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Petr Mladek <pmladek@suse.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.ibm.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Liu Chuansheng <chuansheng.liu@intel.com>,
Valdis Kletnieks <valdis.kletnieks@vt.edu>,
linux-kernel@vger.kernel.org, Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH] kernel/hung_task.c: Monitor killed tasks.
Date: Thu, 23 May 2019 08:46:29 +0900 [thread overview]
Message-ID: <201905222346.x4MNkTqj073305@www262.sakura.ne.jp> (raw)
In-Reply-To: <20190522144300.5ea06345efd9a831803105b7@linux-foundation.org>
Andrew Morton wrote:
> On Thu, 23 May 2019 07:39:25 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > > I put an example patch into my subversion repository:
> > >
> > > svn checkout https://svn.osdn.net/svnroot/tomoyo/branches/syzbot-patches/
> > >
> > > To fetch up-to-date debug printk() patches:
> > >
> > > cd syzbot-patches
> > > svn update
> > >
> > > Does this work for you?
> >
> > Neither will fit into my normal workflow.
> >
> > So, tell me, what are you trying to do? What does you work depend on?
> > Just Linus' tree, or something already in linux-next? Why would you
> > want to keep moving your patch(es) on top of linux-next?
"[PATCH] printk: Monitor change of console loglevel." is targeted for
linux-next only, and I estimate that this patch will be removed in a
week or so, for syzbot can reproduce this problem using linux-next and
syzbot will blacklist testcases causing this problem.
"[PATCH] kernel/hung_task.c: Monitor killed tasks." is targeted for upstream, for
syzbot is hitting this problem in any tree and this will be a kernel's problem.
But for feasibility check, for now I want to try this patch on only linux-next.
I guess we need to tune (e.g. add sysctl) before sending to linux.git tree.
I am seeking for an approach which is less burden for both of you. But it
seems that using Andrew's route seems to fit better for Stephen's workflow.
>
> um, I can carry developer-only linux-next debug patches.
>
OK. Then, will you carry these patches?
Regards.
next prev parent reply other threads:[~2019-05-22 23:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 11:02 [PATCH] kernel/hung_task.c: Monitor killed tasks Tetsuo Handa
2019-05-13 11:11 ` Dmitry Vyukov
2019-05-14 22:28 ` Paul E. McKenney
2019-05-15 10:55 ` Petr Mladek
2019-05-16 8:19 ` Tetsuo Handa
2019-05-16 11:57 ` Petr Mladek
2019-05-16 12:38 ` Tetsuo Handa
2019-05-22 12:38 ` Tetsuo Handa
2019-05-22 13:41 ` Stephen Rothwell
2019-05-22 14:58 ` Tetsuo Handa
2019-05-22 21:09 ` Tetsuo Handa
2019-05-22 21:39 ` Stephen Rothwell
2019-05-22 21:43 ` Andrew Morton
2019-05-22 23:46 ` Tetsuo Handa [this message]
2019-05-27 14:12 ` Tetsuo Handa
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=201905222346.x4MNkTqj073305@www262.sakura.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=chuansheng.liu@intel.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=sfr@canb.auug.org.au \
--cc=valdis.kletnieks@vt.edu \
--cc=vkuznets@redhat.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;
as well as URLs for NNTP newsgroup(s).