From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to 1baa2800e62d
Date: Mon, 9 Sep 2019 22:56:06 -0700 [thread overview]
Message-ID: <20190910055606.GA5132@infradead.org> (raw)
In-Reply-To: <20190904050627.GA2569@infradead.org>
On Tue, Sep 03, 2019 at 10:06:27PM -0700, Christoph Hellwig wrote:
> On Tue, Sep 03, 2019 at 04:40:24PM -0700, Darrick J. Wong wrote:
> > /me shrugs -- it's been broken for years, apparently, and we've been
> > arguing with almost no action for months. Developers who are building
> > things off of 5.3 should probably just add the patch (or turn off slub
> > debugging)....
>
> Well, this is a new breakage with the same old root cause. The root
> cause is that slub with debugging enabled gives us unaligned memory.
>
> But with my log recovery changes we may now use slub for allocations
> larger than a single page (before we only used it for smaller than
> page sizes allocations in the buffer cache), and that newly trips
> up in the pmem driver (and a few others).
Another ping. It would be really sad to release 5.3 with a known
regression we've fixed two weeks before the release.
prev parent reply other threads:[~2019-09-10 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 19:39 [ANNOUNCE] xfs-linux: for-next updated to 1baa2800e62d Darrick J. Wong
2019-09-01 7:33 ` Christoph Hellwig
2019-09-03 23:40 ` Darrick J. Wong
2019-09-04 5:06 ` Christoph Hellwig
2019-09-10 5:56 ` Christoph Hellwig [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=20190910055606.GA5132@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.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