All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [PATCHSET 0/7] xfsprogs: random fixes for 6.0
Date: Mon, 21 Nov 2022 09:06:06 -0800	[thread overview]
Message-ID: <Y3uv/mL79tbW/uir@magnolia> (raw)
In-Reply-To: <20221118144615.o6l7v6cgehirk2n2@andromeda>

On Fri, Nov 18, 2022 at 03:46:15PM +0100, Carlos Maiolino wrote:
> On Tue, Nov 08, 2022 at 06:05:00PM -0800, Darrick J. Wong wrote:
> > Hi all,
> > 
> > This is a rollup of all the random fixes I've collected for xfsprogs
> > 6.0.  At this point it's just an assorted collection, no particular
> > theme.  Many of them are leftovers from the last posting.
> > 
> > If you're going to start using this mess, you probably ought to just
> > pull from my git trees, which are linked below.
> > 
> > This is an extraordinary way to destroy everything.  Enjoy!
> > Comments and questions are, as always, welcome.
> > 
> > --D
> > 
> > xfsprogs git tree:
> > https://git.kernel.org/cgit/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=xfsprogs-fixes-6.0
> > ---
> >  db/btblock.c             |    2 +
> >  db/namei.c               |    2 +
> >  db/write.c               |    4 +-
> >  io/pread.c               |    2 +
> >  libfrog/linux.c          |    1 +
> >  libxfs/libxfs_api_defs.h |    2 +
> >  libxfs/libxfs_io.h       |    1 +
> >  libxfs/libxfs_priv.h     |    2 +
> >  libxfs/rdwr.c            |    8 +++++
> >  libxfs/util.c            |    1 +
> >  mkfs/xfs_mkfs.c          |    2 +
> >  repair/phase2.c          |    8 +++++
> >  repair/phase6.c          |    9 +++++
> >  repair/protos.h          |    1 +
> >  repair/xfs_repair.c      |   77 ++++++++++++++++++++++++++++++++++++++++------
> >  scrub/inodes.c           |    2 +
> >  16 files changed, 105 insertions(+), 19 deletions(-)
> > 
> 
> The whole series looks good. Will test
> 
> Reviewed-by: Carlos Maiolino <cmaiolino@redhat.com>

Thank you!

--D

> -- 
> Carlos Maiolino

      reply	other threads:[~2022-11-21 17:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3bbCi5OklUNOpVog9KVqiGD2TPkUD4x6PJjtZuKJCzP-QYMXvnqh7kZB8Vnp2BnxW6jn-dlyN7DIFoDTnryqNw==@protonmail.internalid>
2022-11-09  2:05 ` [PATCHSET 0/7] xfsprogs: random fixes for 6.0 Darrick J. Wong
2022-11-09  2:05   ` [PATCH 1/7] libxfs: consume the xfs_warn mountpoint argument Darrick J. Wong
2022-11-09  2:05   ` [PATCH 2/7] misc: add static to various sourcefile-local functions Darrick J. Wong
2022-11-09  2:05   ` [PATCH 3/7] misc: add missing includes Darrick J. Wong
2022-11-09  2:05   ` [PATCH 4/7] xfs_db: fix octal conversion logic Darrick J. Wong
2022-11-09  2:05   ` [PATCH 5/7] xfs_db: fix printing of reverse mapping record blockcounts Darrick J. Wong
2022-11-09  2:05   ` [PATCH 6/7] xfs_repair: don't crash on unknown inode parents in dry run mode Darrick J. Wong
2022-11-09  2:05   ` [PATCH 7/7] xfs_repair: retain superblock buffer to avoid write hook deadlock Darrick J. Wong
2022-11-18 14:45     ` Carlos Maiolino
2022-11-21 17:05       ` Darrick J. Wong
2022-11-18 14:46   ` [PATCHSET 0/7] xfsprogs: random fixes for 6.0 Carlos Maiolino
2022-11-21 17:06     ` Darrick J. Wong [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=Y3uv/mL79tbW/uir@magnolia \
    --to=djwong@kernel.org \
    --cc=cem@kernel.org \
    --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 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.