From: Dave Chinner <david@fromorbit.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: guaneryu@gmail.com, linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH 1/3] common: filter aiodio dmesg after fs/iomap.c to fs/iomap/ move
Date: Thu, 25 Jul 2019 09:21:17 +1000 [thread overview]
Message-ID: <20190724232117.GB7777@dread.disaster.area> (raw)
In-Reply-To: <156394157450.1850719.464315342783936237.stgit@magnolia>
On Tue, Jul 23, 2019 at 09:12:54PM -0700, Darrick J. Wong wrote:
> From: Darrick J. Wong <darrick.wong@oracle.com>
>
> Since the iomap code are moving to fs/iomap/ we have to add new entries
> to the aiodio dmesg filter to reflect this.
>
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> ---
> common/filter | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
>
> diff --git a/common/filter b/common/filter
> index ed082d24..26fc2132 100644
> --- a/common/filter
> +++ b/common/filter
> @@ -555,6 +555,7 @@ _filter_aiodio_dmesg()
> local warn7="WARNING:.*fs/iomap\.c:.*iomap_dio_actor.*"
> local warn8="WARNING:.*fs/iomap\.c:.*iomap_dio_complete.*"
There's two different warnings that need capturing here.
> local warn9="WARNING:.*fs/direct-io\.c:.*dio_complete.*"
> + local warn10="WARNING:.*fs/iomap/direct-io\.c:.*iomap_dio_actor.*"
> sed -e "s#$warn1#Intentional warnings in xfs_file_dio_aio_write#" \
> -e "s#$warn2#Intentional warnings in xfs_file_dio_aio_read#" \
> -e "s#$warn3#Intentional warnings in xfs_file_read_iter#" \
> @@ -563,7 +564,8 @@ _filter_aiodio_dmesg()
> -e "s#$warn6#Intentional warnings in __xfs_get_blocks#" \
> -e "s#$warn7#Intentional warnings in iomap_dio_actor#" \
> -e "s#$warn8#Intentional warnings in iomap_dio_complete#" \
> - -e "s#$warn9#Intentional warnings in dio_complete#"
> + -e "s#$warn9#Intentional warnings in dio_complete#" \
> + -e "s#$warn10#Intentional warnings in iomap_dio_actor#"
Why not just change the regex in warn7/warn8 just to catch anything
under fs/iomap rather than explictly specifying fs/iomap.c?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2019-07-24 23:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 4:12 [PATCH 0/3] fstests: various fixes Darrick J. Wong
2019-07-24 4:12 ` [PATCH 1/3] common: filter aiodio dmesg after fs/iomap.c to fs/iomap/ move Darrick J. Wong
2019-07-24 23:21 ` Dave Chinner [this message]
2019-07-25 18:02 ` Darrick J. Wong
2019-07-25 18:03 ` [PATCH v2 " Darrick J. Wong
2019-07-28 11:30 ` Eryu Guan
2019-07-30 0:55 ` Darrick J. Wong
2019-08-07 1:44 ` Darrick J. Wong
2019-08-11 15:25 ` Eryu Guan
2019-07-24 4:13 ` [PATCH 2/3] xfs/504: fix bogus test description Darrick J. Wong
2019-07-24 4:13 ` [PATCH 3/3] generic/561: kill duperemove after sleep_time Darrick J. Wong
2019-07-24 15:55 ` [PATCH 4/3] generic/506: mount scratch fs before testing for prjquota presence Darrick J. Wong
2019-07-24 15:56 ` [PATCH 5/3] various: disable quotas before running test Darrick J. Wong
2019-07-24 15:56 ` [PATCH 6/3] xfs/033: filter out root inode nlink repair Darrick J. Wong
2019-07-24 15:56 ` [PATCH 7/3] xfs/194: unmount forced v4 fs during cleanup Darrick J. Wong
2019-07-24 23:22 ` Dave Chinner
2019-07-25 18:03 ` Darrick J. Wong
2019-07-25 18:04 ` [PATCH v2 " Darrick J. Wong
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=20190724232117.GB7777@dread.disaster.area \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@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 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).