From: Jianxiong Gao <jxgao@google.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Christoph Hellwig" <hch@lst.de>,
"Dominique MARTINET" <dominique.martinet@atmark-techno.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Horia Geantă" <horia.geanta@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Lukas Hartmann" <lukas@mntmn.com>,
"Aymen Sghaier" <aymen.sghaier@nxp.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"Marc Orr" <marcorr@google.com>,
"Erdem Aktas" <erdemaktas@google.com>,
"Peter Gonda" <pgonda@google.com>
Subject: Re: swiotlb/caamjr regression (Was: [GIT PULL] (swiotlb) stable/for-linus-5.12)
Date: Wed, 16 Jun 2021 13:49:54 -0700 [thread overview]
Message-ID: <CAMGD6P1v2JoJoxSuAYL8UjdtCaLCc4K_7xzVkumspeb0qn=LBQ@mail.gmail.com> (raw)
In-Reply-To: <YMM8Ua0HMmErLIQg@0xbeefdead.lan>
On Fri, Jun 11, 2021 at 3:35 AM Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
>
> On Fri, Jun 11, 2021 at 08:21:53AM +0200, Christoph Hellwig wrote:
> > On Thu, Jun 10, 2021 at 05:52:07PM +0300, Horia Geantă wrote:
> > > I've noticed the failure also in v5.10 and v5.11 stable kernels,
> > > since the patch set has been backported.
> >
> > FYI, there has been a patch on the list that should have fixed this
> > for about a month:
> >
> > https://lore.kernel.org/linux-iommu/20210510091816.GA2084@lst.de/T/#m0d0df6490350a08dcc24c9086c8edc165b402d6f
> >
> > but it seems like it never got picked up.
>
> Jianxiong,
> Would you be up for testing this patch on your NVMe rig please? I don't
> forsee a problem.. but just in case
>
I have tested the attached patch and it generates an error when
formatting a disk to xfs format in Rhel 8 environment:
sudo mkfs.xfs -f /dev/nvme0n2
meta-data=/dev/nvme0n2 isize=512 agcount=4, agsize=32768000 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1
data = bsize=4096 blocks=131072000, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=64000, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Discarding blocks...Done.
bad magic number
bad magic number
Metadata corruption detected at 0x56211de4c0c8, xfs_sb block 0x0/0x200
libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200
releasing dirty buffer (bulk) to free list!
I applied the patch on commit 06af8679449d.
WARNING: multiple messages have this Message-ID (diff)
From: Jianxiong Gao via iommu <iommu@lists.linux-foundation.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: "Dominique MARTINET" <dominique.martinet@atmark-techno.com>,
"Aymen Sghaier" <aymen.sghaier@nxp.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Marc Orr" <marcorr@google.com>,
"Lukas Hartmann" <lukas@mntmn.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"Peter Gonda" <pgonda@google.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Christoph Hellwig" <hch@lst.de>
Subject: Re: swiotlb/caamjr regression (Was: [GIT PULL] (swiotlb) stable/for-linus-5.12)
Date: Wed, 16 Jun 2021 13:49:54 -0700 [thread overview]
Message-ID: <CAMGD6P1v2JoJoxSuAYL8UjdtCaLCc4K_7xzVkumspeb0qn=LBQ@mail.gmail.com> (raw)
In-Reply-To: <YMM8Ua0HMmErLIQg@0xbeefdead.lan>
On Fri, Jun 11, 2021 at 3:35 AM Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
>
> On Fri, Jun 11, 2021 at 08:21:53AM +0200, Christoph Hellwig wrote:
> > On Thu, Jun 10, 2021 at 05:52:07PM +0300, Horia Geantă wrote:
> > > I've noticed the failure also in v5.10 and v5.11 stable kernels,
> > > since the patch set has been backported.
> >
> > FYI, there has been a patch on the list that should have fixed this
> > for about a month:
> >
> > https://lore.kernel.org/linux-iommu/20210510091816.GA2084@lst.de/T/#m0d0df6490350a08dcc24c9086c8edc165b402d6f
> >
> > but it seems like it never got picked up.
>
> Jianxiong,
> Would you be up for testing this patch on your NVMe rig please? I don't
> forsee a problem.. but just in case
>
I have tested the attached patch and it generates an error when
formatting a disk to xfs format in Rhel 8 environment:
sudo mkfs.xfs -f /dev/nvme0n2
meta-data=/dev/nvme0n2 isize=512 agcount=4, agsize=32768000 blks
= sectsz=512 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1
data = bsize=4096 blocks=131072000, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=64000, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Discarding blocks...Done.
bad magic number
bad magic number
Metadata corruption detected at 0x56211de4c0c8, xfs_sb block 0x0/0x200
libxfs_writebufr: write verifer failed on xfs_sb bno 0x0/0x200
releasing dirty buffer (bulk) to free list!
I applied the patch on commit 06af8679449d.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next prev parent reply other threads:[~2021-06-16 20:50 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 16:00 [GIT PULL] (swiotlb) stable/for-linus-5.12 Konrad Rzeszutek Wilk
2021-02-26 22:24 ` pr-tracker-bot
2021-06-08 2:35 ` swiotlb/caamjr regression (Was: [GIT PULL] (swiotlb) stable/for-linus-5.12) Dominique MARTINET
2021-06-10 14:52 ` Horia Geantă
2021-06-10 14:52 ` Horia Geantă
2021-06-10 19:41 ` Linus Torvalds
2021-06-10 19:41 ` Linus Torvalds
2021-06-10 23:20 ` Horia Geantă
2021-06-10 23:20 ` Horia Geantă
2021-06-11 6:21 ` Christoph Hellwig
2021-06-11 6:21 ` Christoph Hellwig
2021-06-11 10:34 ` Konrad Rzeszutek Wilk
2021-06-11 10:34 ` Konrad Rzeszutek Wilk
2021-06-11 10:59 ` Horia Geantă
2021-06-11 10:59 ` Horia Geantă
2021-06-11 16:21 ` Linus Torvalds
2021-06-11 16:21 ` Linus Torvalds
2021-06-16 20:49 ` Jianxiong Gao [this message]
2021-06-16 20:49 ` Jianxiong Gao via iommu
2021-06-17 0:27 ` Konrad Rzeszutek Wilk
2021-06-17 0:27 ` Konrad Rzeszutek Wilk
2021-06-17 0:39 ` Dominique MARTINET
2021-06-17 0:39 ` Dominique MARTINET
2021-06-17 5:12 ` Christoph Hellwig
2021-06-17 5:12 ` Christoph Hellwig
2021-06-17 5:36 ` Dominique MARTINET
2021-06-17 5:36 ` Dominique MARTINET
2021-06-18 18:01 ` Jianxiong Gao
2021-06-18 18:01 ` Jianxiong Gao via iommu
2021-06-21 2:03 ` Dominique MARTINET
2021-06-21 2:03 ` Dominique MARTINET
2021-06-21 2:55 ` Chanho Park
2021-06-21 2:55 ` Chanho Park
2021-06-21 4:14 ` 'Dominique MARTINET'
2021-06-21 4:14 ` 'Dominique MARTINET'
2021-06-21 13:16 ` Konrad Rzeszutek Wilk
2021-06-21 13:16 ` Konrad Rzeszutek Wilk
2021-06-22 7:48 ` 'Dominique MARTINET'
2021-06-22 7:48 ` 'Dominique MARTINET'
2021-06-22 21:58 ` Konrad Rzeszutek Wilk
2021-06-22 21:58 ` Konrad Rzeszutek Wilk
2021-06-22 23:04 ` 'Dominique MARTINET'
2021-06-22 23:04 ` 'Dominique MARTINET'
2021-06-17 11:33 ` Christoph Hellwig
2021-06-17 11:33 ` Christoph Hellwig
2021-06-11 16:01 ` Linus Torvalds
2021-06-11 16:01 ` Linus Torvalds
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='CAMGD6P1v2JoJoxSuAYL8UjdtCaLCc4K_7xzVkumspeb0qn=LBQ@mail.gmail.com' \
--to=jxgao@google.com \
--cc=aymen.sghaier@nxp.com \
--cc=davem@davemloft.net \
--cc=dominique.martinet@atmark-techno.com \
--cc=erdemaktas@google.com \
--cc=hch@lst.de \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@mntmn.com \
--cc=marcorr@google.com \
--cc=pgonda@google.com \
--cc=torvalds@linux-foundation.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.