From: Al Viro <viro@ZenIV.linux.org.uk>
To: Andrei Vagin <avagin@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: lockdep reports possible recursive locking for sb_writers from do_iter_write and do_sendfile
Date: Fri, 7 Jul 2017 16:42:08 +0100 [thread overview]
Message-ID: <20170707154208.GF10672@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CANaxB-zrn8JZ=H8y2acmViiuEvSDRorsoreA7yC+05swU+uWag@mail.gmail.com>
On Fri, Jul 07, 2017 at 08:27:47AM -0700, Andrei Vagin wrote:
> Hello,
>
> We run CRIU tests for Linus' tree and today we found this warning:
See vfs.git#work.read_write; the fix is there and it'll go to Linus
today.
prev parent reply other threads:[~2017-07-07 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-07 15:27 lockdep reports possible recursive locking for sb_writers from do_iter_write and do_sendfile Andrei Vagin
2017-07-07 15:42 ` Al Viro [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=20170707154208.GF10672@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=avagin@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.