From: Christoph Hellwig <hch@lst.de>
To: lkp@lists.01.org
Subject: Re: [lkp-developer] [xfs] acdda3aae1: WARNING:at_fs/iomap.c:#iomap_dio_rw
Date: Thu, 22 Dec 2016 07:20:19 +0100 [thread overview]
Message-ID: <20161222062019.GB31630@lst.de> (raw)
In-Reply-To: <20161221185658.GB21332@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 373 bytes --]
On Thu, Dec 22, 2016 at 02:56:58AM +0800, kernel test robot wrote:
> [ 700.619048] XFS (sdf1): Ending clean mount
> [ 701.352337] ------------[ cut here ]------------
> [ 701.357125] WARNING: CPU: 0 PID: 16179 at fs/iomap.c:950 iomap_dio_rw+0x3b7/0x3d0
This is the racy direct vs buffered I/O warning we had for a long time in
XFS, it just moved to a new place.
prev parent reply other threads:[~2016-12-22 6:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 18:56 [lkp-developer] [xfs] acdda3aae1: WARNING:at_fs/iomap.c:#iomap_dio_rw kernel test robot
2016-12-22 6:20 ` Christoph Hellwig [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=20161222062019.GB31630@lst.de \
--to=hch@lst.de \
--cc=lkp@lists.01.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.