linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Byungchul Park <byungchul.park@lge.com>
Cc: Dmitry Vyukov <dvyukov@google.com>, Jan Kara <jack@suse.cz>,
	syzbot 
	<bot+045a1f65bdea780940bf0f795a292f4cd0b773d1@syzkaller.appspotmail.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	jlayton@redhat.com, LKML <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>,
	Mel Gorman <mgorman@techsingularity.net>,
	npiggin@gmail.com, rgoldwyn@suse.com,
	syzkaller-bugs@googlegroups.com,
	Peter Zijlstra <peterz@infradead.org>,
	kernel-team@lge.com
Subject: Re: possible deadlock in generic_file_write_iter (2)
Date: Wed, 6 Dec 2017 16:32:26 -0800	[thread overview]
Message-ID: <20171206163226.5f46132aeea6fbcc44fc8421@linux-foundation.org> (raw)
In-Reply-To: <20171206050547.GA5260@X58A-UD3R>

On Wed, 6 Dec 2017 14:05:47 +0900 Byungchul Park <byungchul.park@lge.com> wrote:

> > What is cross-release? Is it something new? Should we always enable
> > crossrelease_fullstack during testing?
> 
> Hello Dmitry,
> 
> Yes, it's new one making lockdep track wait_for_completion() as well.
> 
> And we should enable crossrelease_fullstack if you don't care system
> slowdown but testing.

We should update Documentation/process/submit-checklist.rst section 12.
But that list doesn't even mention CONFIG_LOCKDEP so a bit of
maintenance work will be needed there..

  reply	other threads:[~2017-12-07  0:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <94eb2c0d010a4e7897055f70535b@google.com>
2017-12-04  8:33 ` possible deadlock in generic_file_write_iter (2) Jan Kara
2017-12-05  4:58   ` Byungchul Park
2017-12-05  9:19     ` Dmitry Vyukov
2017-12-06  5:05       ` Byungchul Park
2017-12-07  0:32         ` Andrew Morton [this message]
2017-12-07 17:07         ` Dmitry Vyukov
2017-12-07 23:27           ` Byungchul Park
2017-12-05  9:41     ` Jan Kara
2017-12-06  5:34       ` Byungchul Park

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=20171206163226.5f46132aeea6fbcc44fc8421@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bot+045a1f65bdea780940bf0f795a292f4cd0b773d1@syzkaller.appspotmail.com \
    --cc=byungchul.park@lge.com \
    --cc=dvyukov@google.com \
    --cc=hannes@cmpxchg.org \
    --cc=jack@suse.cz \
    --cc=jlayton@redhat.com \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=npiggin@gmail.com \
    --cc=peterz@infradead.org \
    --cc=rgoldwyn@suse.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;
as well as URLs for NNTP newsgroup(s).