From: Toshi Kani <toshi.kani@hpe.com>
To: Ross Zwisler <ross.zwisler@linux.intel.com>
Cc: dan.j.williams@intel.com, jack@suse.cz, david@fromorbit.com,
hch@infradead.org, boaz@plexistor.com, tytso@mit.edu,
adilger.kernel@dilger.ca, micah.parrish@hpe.com,
linux-nvdimm@ml01.01.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] xfs: Add alignment check for DAX mount
Date: Mon, 02 May 2016 13:54:25 -0600 [thread overview]
Message-ID: <1462218865.27137.18.camel@hpe.com> (raw)
In-Reply-To: <20160502195027.GC14421@linux.intel.com>
On Mon, 2016-05-02 at 13:50 -0600, Ross Zwisler wrote:
> On Mon, May 02, 2016 at 12:42:58PM -0600, Toshi Kani wrote:
:
> > xfs_warn(mp,
> > - "DAX enabled. Warning: EXPERIMENTAL, use at your own risk");
> > + "DAX enabled. Warning: EXPERIMENTAL, use at your own
> > risk");
> > if (sb->s_blocksize != PAGE_SIZE) {
> > xfs_alert(mp,
> > "Filesystem block size invalid for DAX Turning DAX
> > off.");
> > mp->m_flags &= ~XFS_MOUNT_DAX;
> > - } else if (!sb->s_bdev->bd_disk->fops->direct_access)
> > {
> > - xfs_alert(mp,
> > - "Block device does not support DAX Turning DAX off.");
> > + } else if ((error = bdev_direct_access(sb->s_bdev,
> > &dax)) < 0) {
> > + switch (error) {
> > + case -EOPNOTSUPP:
> > + xfs_alert(mp,
> > + "Block device does not support DAX Turning DAX
> > off.");
>
> Since you're already in here editing all the strings, can you add a
> period to make it more readable? Applies to all strings.
Right. Will do.
> >
> > + "Block device does not support DAX. Turning
> > DAX off.");
> ^
>
> >
> > + break;
> > + case -EINVAL:
> > + xfs_alert(mp,
> > + "Partition alignment invalid for DAX Turning
> > DAX off.");
> > + break;
> > + default:
> > + xfs_alert(mp,
> > + "DAX access failed (%d) DAX Turning DAX off.",
> > error);
>
> I DAX think you might DAX have too many DAXes in here. :)
Oops! :)
> >
> > + }
> > mp->m_flags &= ~XFS_MOUNT_DAX;
> > }
> > }
>
> Other than the nit-picking about the strings, this seems fine.
>
> You can add this for the series:
> Reviewed-by: Ross Zwisler <ross.zwisler@linux.intel.com>
Thanks!
-Toshi
next prev parent reply other threads:[~2016-05-02 20:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 18:42 [PATCH v2 0/3] Add alignment check for DAX mount Toshi Kani
2016-05-02 18:42 ` [PATCH v2 1/3] ext4: " Toshi Kani
2016-05-03 7:58 ` Jan Kara
2016-05-03 8:44 ` Christoph Hellwig
2016-05-03 9:00 ` Jan Kara
2016-05-03 14:43 ` Ross Zwisler
2016-05-03 15:41 ` Toshi Kani
2016-05-04 15:42 ` Toshi Kani
2016-05-02 18:42 ` [PATCH v2 2/3] ext2: " Toshi Kani
2016-05-03 8:01 ` Jan Kara
2016-05-02 18:42 ` [PATCH v2 3/3] xfs: " Toshi Kani
2016-05-02 19:50 ` Ross Zwisler
2016-05-02 19:54 ` Toshi Kani [this message]
2016-05-04 23:18 ` Dave Chinner
2016-05-04 23:41 ` Toshi Kani
2016-05-05 8:03 ` Jan Kara
2016-05-02 19:20 ` [PATCH v2 0/3] " Boaz Harrosh
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=1462218865.27137.18.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=adilger.kernel@dilger.ca \
--cc=boaz@plexistor.com \
--cc=dan.j.williams@intel.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=micah.parrish@hpe.com \
--cc=ross.zwisler@linux.intel.com \
--cc=tytso@mit.edu \
/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