From: Christoph Hellwig <hch@lst.de>
To: Tianyu Lan <ltykernel@gmail.com>
Cc: kernel test robot <oliver.sang@intel.com>,
Tianyu Lan <Tianyu.Lan@microsoft.com>,
Christoph Hellwig <hch@lst.de>,
linux-doc@vger.kernel.org, iommu@lists.linux.dev,
lkp@lists.01.org, lkp@intel.com
Subject: Re: [EXTERNAL] [swiotlb] 44d89f2248: Kernel_panic-not_syncing:swiotlb_init_remap:nslabs=#too_small
Date: Wed, 13 Jul 2022 08:02:46 +0200 [thread overview]
Message-ID: <20220713060246.GA13497@lst.de> (raw)
In-Reply-To: <c8edfbd4-afad-c018-daf6-aa2ac1f7b2fe@gmail.com>
On Wed, Jul 13, 2022 at 01:58:38PM +0800, Tianyu Lan wrote:
> Thanks for report. The issue is caused by auto merging between
> commit44d89f("swiotlb: split up the global swiotlb lock") and commit
> 0bf28fc40(swiotlb: panic if nslabs is too small). nslab is checked before
> initialization.
>
> Christoph, do you prefer to update patch "swiotlb: split up the global
> swiotlb lock" or append a fix patch on current brand?
Please just send a patch againt the current tree. I'll see if squashing
it in makes any sense.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: lkp@lists.01.org
Subject: Re: [EXTERNAL] [swiotlb] 44d89f2248: Kernel_panic-not_syncing:swiotlb_init_remap:nslabs=#too_small
Date: Wed, 13 Jul 2022 08:02:46 +0200 [thread overview]
Message-ID: <20220713060246.GA13497@lst.de> (raw)
In-Reply-To: <c8edfbd4-afad-c018-daf6-aa2ac1f7b2fe@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
On Wed, Jul 13, 2022 at 01:58:38PM +0800, Tianyu Lan wrote:
> Thanks for report. The issue is caused by auto merging between
> commit44d89f("swiotlb: split up the global swiotlb lock") and commit
> 0bf28fc40(swiotlb: panic if nslabs is too small). nslab is checked before
> initialization.
>
> Christoph, do you prefer to update patch "swiotlb: split up the global
> swiotlb lock" or append a fix patch on current brand?
Please just send a patch againt the current tree. I'll see if squashing
it in makes any sense.
next prev parent reply other threads:[~2022-07-13 6:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 3:08 [swiotlb] 44d89f2248: Kernel_panic-not_syncing:swiotlb_init_remap:nslabs=#too_small kernel test robot
2022-07-13 3:08 ` kernel test robot
2022-07-13 5:58 ` [EXTERNAL] " Tianyu Lan
2022-07-13 5:58 ` Tianyu Lan
2022-07-13 6:02 ` Christoph Hellwig [this message]
2022-07-13 6:02 ` Christoph Hellwig
2022-07-13 16:11 ` Conor Dooley
2022-07-13 16:11 ` Conor Dooley
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=20220713060246.GA13497@lst.de \
--to=hch@lst.de \
--cc=Tianyu.Lan@microsoft.com \
--cc=iommu@lists.linux.dev \
--cc=linux-doc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=ltykernel@gmail.com \
--cc=oliver.sang@intel.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.