All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@redhat.com>
To: linux-xfs@vger.kernel.org
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
	Brian Foster <bfoster@redhat.com>,
	Eric Sandeen <sandeen@redhat.com>,
	Dave Chinner <david@fromorbit.com>,
	Gao Xiang <hsiangkao@redhat.com>
Subject: [PATCH v6 0/3] xfsprogs: consolidate stripe validation
Date: Tue, 13 Oct 2020 12:06:24 +0800	[thread overview]
Message-ID: <20201013040627.13932-1-hsiangkao@redhat.com> (raw)

v5: https://lore.kernel.org/r/20201009052421.3328-1-hsiangkao@redhat.com

Hi,

This is another approach suggested by Eric in the reply of v3
(if I understand correctly), which also attempts to use
i18n-enabled xfsprogs xfs_notice() to error out sanity check
failure suggested by Dave on IRC.

kernel side of [PATCH 2/3]
https://lore.kernel.org/r/20201013034853.28236-1-hsiangkao@redhat.com

Changes since v5:
 - rename the helper to xfs_validate_stripe_geometry() (Brian);
 - drop a new added trailing newline in xfs_sb.c (Brian);
 - add "bool silent" argument to avoid too many error messages (Brian).

Thanks,
Gao Xiang

Gao Xiang (3):
  libxfs: allow i18n to xfs printk
  xfs: introduce xfs_validate_stripe_geometry()
  mkfs: make use of xfs_validate_stripe_geometry()

 libxfs/libxfs_api_defs.h |  1 +
 libxfs/libxfs_priv.h     |  8 ++---
 libxfs/xfs_sb.c          | 70 +++++++++++++++++++++++++++++++++-------
 libxfs/xfs_sb.h          |  3 ++
 mkfs/xfs_mkfs.c          | 23 ++++---------
 5 files changed, 74 insertions(+), 31 deletions(-)

-- 
2.18.1


             reply	other threads:[~2020-10-13  4:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-13  4:06 Gao Xiang [this message]
2020-10-13  4:06 ` [PATCH v6 1/3] libxfs: allow i18n to xfs printk Gao Xiang
2020-10-13  4:06 ` [PATCH v6 2/3] xfs: introduce xfs_validate_stripe_geometry() Gao Xiang
2020-10-13  4:06 ` [PATCH v6 3/3] mkfs: make use of xfs_validate_stripe_geometry() Gao Xiang
2020-10-13 13:44   ` Brian Foster
2020-10-14 16:20   ` Darrick J. Wong
2021-02-16  1:04   ` Eric Sandeen
2021-02-18  2:41     ` Gao Xiang
2021-02-18  5:24       ` Gao Xiang
2021-02-18 16:38         ` Eric Sandeen
2021-02-19  0:39           ` Gao Xiang
2021-02-19  1:37   ` [PATCH v7 " Gao Xiang
2021-02-24  0:10     ` Eric Sandeen
2021-02-24  0:55       ` Gao Xiang

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=20201013040627.13932-1-hsiangkao@redhat.com \
    --to=hsiangkao@redhat.com \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.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 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.