linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux kernel regression tracking (#update)"  <regressions@leemhuis.info>
To: Bjorn Helgaas <helgaas@kernel.org>, Koba Ko <koba.ko@canonical.com>
Cc: vsd@suremail.info, "Tom Lendacky" <thomas.lendacky@amd.com>,
	"John Allen" <john.allen@amd.com>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	linux-crypto@vger.kernel.org, linux-pci@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [Bug 216888] New: "sysfs: cannot create duplicate filename /dma/dma0chan0" with 68dbe80f ("crypto: ccp - Release dma channels before dmaengine unrgister")
Date: Mon, 30 Jan 2023 13:54:16 +0100	[thread overview]
Message-ID: <d018d4ba-802d-76f4-0892-97b033fbc7bb@leemhuis.info> (raw)
In-Reply-To: <7b38ae22-b13d-64af-7c79-a56cdba26754@leemhuis.info>

[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]

On 06.01.23 09:38, Linux kernel regression tracking (#adding) wrote:
> On 05.01.23 18:47, Bjorn Helgaas wrote:
>> Per the report, this is a regression and reverting 68dbe80f5b51
>> ("crypto: ccp - Release dma channels before dmaengine unrgister"),
>> which appeared in v6.1, avoids the problem.
>>
>> The bugzilla is assigned to PCI, and I know PCI does have similar
>> sysfs duplicate filename issues, but I don't know whether this
>> instance is related to 68dbe80f5b51 or to the PCI core.
>>
>> On Thu, Jan 05, 2023 at 03:12:26PM +0000, bugzilla-daemon@kernel.org wrote:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=216888

#regzbot fix: crypto: ccp - Failure on re-initialization due to
duplicate sysfs filename

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.

#regzbot ignore-activity

      reply	other threads:[~2023-01-30 12:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-216888-41252@https.bugzilla.kernel.org/>
2023-01-05 17:47 ` [Bug 216888] New: "sysfs: cannot create duplicate filename /dma/dma0chan0" with 68dbe80f ("crypto: ccp - Release dma channels before dmaengine unrgister") Bjorn Helgaas
2023-01-06  8:38   ` Linux kernel regression tracking (#adding)
2023-01-30 12:54     ` Linux kernel regression tracking (#update) [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=d018d4ba-802d-76f4-0892-97b033fbc7bb@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=helgaas@kernel.org \
    --cc=john.allen@amd.com \
    --cc=koba.ko@canonical.com \
    --cc=kw@linux.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=thomas.lendacky@amd.com \
    --cc=vsd@suremail.info \
    /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;
as well as URLs for NNTP newsgroup(s).