public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Christoph Hellwig <hch@lst.de>,
	linux-xfs@vger.kernel.org, Eric Sandeen <sandeen@redhat.com>
Subject: Re: [PATCH 1/6] xfs: remove the agfl_bno member from struct xfs_agfl
Date: Mon, 24 Feb 2020 14:46:22 -0800	[thread overview]
Message-ID: <20200224224622.GA25075@infradead.org> (raw)
In-Reply-To: <20200224222737.GB6740@magnolia>

On Mon, Feb 24, 2020 at 02:27:37PM -0800, Darrick J. Wong wrote:
> On Mon, Feb 24, 2020 at 02:21:18PM -0800, Christoph Hellwig wrote:
> > On Mon, Feb 24, 2020 at 02:19:31PM -0800, Darrick J. Wong wrote:
> > > > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > > > 
> > > > Any chance we can pick this up for 5.6 to unbreak arm OABI?
> > > 
> > > Yeah, I can do that.  Is there a Fixes: tag that goes with this?
> > 
> > I'm not sure what to add.  I think the problem itself has actually
> > always been around since adding v5 fs support.  But the build break
> > was only caused by the addition of the BUILD_BUG_ON.
> 
> Hmm.  That's tricky, since in theory this should go all the way back to
> the introduction of the v5 format in 3.x, but that's going to require
> explicit backporting to get past all the reorganization and other things
> that have happened.  We might just have to hand-backport it to the
> stable kernels seeing how the macro name change will probably cause all
> sorts of problems with AI backports. :/

So which fixes tag do you want?  Or feel free to just add the one you
feel fits best.

> > > Also, will you have a chance to respin the last patch for 5.7?
> > 
> > Last patch in this series?
> 
> Yes.  From the discussion of patch 6/6,
> 
> "+   __xfs_sb_from_disk(&sb, bp->b_addr, false);
> 
> "why not dsb here
> 
> "Yes, this should just pass dsb."

Oh.  I've actually had the respun branch on my box since a day after
that comment.  But I think it doesn't make sense until the fix in
patch one is in the baseline tree, given how many outstanding patch
series we have.

  reply	other threads:[~2020-02-24 22:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 13:33 agfl and related cleanups Christoph Hellwig
2020-01-30 13:33 ` [PATCH 1/6] xfs: remove the agfl_bno member from struct xfs_agfl Christoph Hellwig
2020-02-03 17:46   ` Eric Sandeen
2020-02-03 17:47     ` Christoph Hellwig
2020-02-24 22:02   ` Christoph Hellwig
2020-02-24 22:19     ` Darrick J. Wong
2020-02-24 22:21       ` Christoph Hellwig
2020-02-24 22:27         ` Darrick J. Wong
2020-02-24 22:46           ` Christoph Hellwig [this message]
2020-02-24 22:27     ` Eric Sandeen
2020-02-24 22:30       ` Christoph Hellwig
2020-02-24 22:35         ` Eric Sandeen
2020-02-24 22:46           ` Christoph Hellwig
2020-02-24 22:50             ` Eric Sandeen
2020-02-25 17:24               ` Christoph Hellwig
2020-01-30 13:33 ` [PATCH 2/6] xfs: remove the xfs_agfl_t typedef Christoph Hellwig
2020-02-03 17:46   ` Eric Sandeen
2020-01-30 13:33 ` [PATCH 3/6] xfs: remove XFS_BUF_TO_AGFL Christoph Hellwig
2020-02-03 18:28   ` Eric Sandeen
2020-01-30 13:33 ` [PATCH 4/6] xfs: remove XFS_BUF_TO_AGI Christoph Hellwig
2020-02-03 18:30   ` Eric Sandeen
2020-01-30 13:33 ` [PATCH 5/6] xfs: remove XFS_BUF_TO_AGF Christoph Hellwig
2020-02-03 18:35   ` Eric Sandeen
2020-02-03 18:54   ` Eric Sandeen
2020-01-30 13:33 ` [PATCH 6/6] xfs: remove XFS_BUF_TO_SBP Christoph Hellwig
2020-02-03 18:38   ` Eric Sandeen
2020-02-04  6:15     ` Christoph Hellwig
2020-02-03  9:12 ` agfl and related cleanups Chandan Rajendra
  -- strict thread matches above, loose matches on Subject: below --
2020-03-06 14:52 agfl and related cleanups v2 Christoph Hellwig
2020-03-06 14:52 ` [PATCH 1/6] xfs: remove the agfl_bno member from struct xfs_agfl Christoph Hellwig
2020-03-10 11:23   ` Brian Foster

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=20200224224622.GA25075@infradead.org \
    --to=hch@infradead.org \
    --cc=darrick.wong@oracle.com \
    --cc=hch@lst.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox