From: Salvatore Bonaccorso <carnil@debian.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>,
Martin Wilck <mwilck@suse.com>,
Christoph Hellwig <hch@infradead.org>,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>
Cc: linux-scsi@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [PATCH 1/1] mpt3sas: Remove usage of dma_get_required_mask api
Date: Wed, 22 Feb 2023 17:44:43 +0100 [thread overview]
Message-ID: <Y/ZGe8c1XyqSuCSk@eldamar.lan> (raw)
In-Reply-To: <Y8+m0w4Og2CLFImY@lorien.valinor.li>
Hi,
On Tue, Jan 24, 2023 at 10:37:23AM +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Mon, Jan 02, 2023 at 08:06:41AM -0500, Martin K. Petersen wrote:
> >
> > Martin,
> >
> > > is anything blocking mainline inclusion of this patch?
> >
> > I applied these to 6.2/scsi-fixes last week. The patches have been
> > sitting in a topic branch for a bit due to the three-way conflict
> > between fixes, queue, and upstream.
>
> It landed in 6.2-rc4 recently in fact. Thank you!
>
> Would it be posssible to backport the fix as well back to the stable
> series affected?
>
> In Debian we have the reports as per https://bugs.debian.org/1022126
> where the issue was introduced back in 5.10.y. Context in
> https://lore.kernel.org/linux-scsi/CAK=zhgr=MYn=-mrz3gKUFoXG_+EQ796bHEWSdK88o1Aqamby7g@mail.gmail.com/
> .
Friendly ping on this, can this change be backported as well to the
relevant stable series? It would apply already cleanly to 6.1.y, but
due to 9df650963bf6 ("scsi: mpt3sas: Don't change DMA mask while
reallocating pools") it might need some additional review for the
older stable series (in particular of interest due to the above for
5.10.y).
Thanks already! If the change for older series needs some additional
testing we might ask the affected users from the Debian bug 1022126 to
test on 5.10.y as well.
Regards,
Salvatore
next prev parent reply other threads:[~2023-02-22 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 9:16 [PATCH 0/1] mpt3sas: Remove usage of dma_get_required_mask api Sreekanth Reddy
2022-10-28 9:16 ` [PATCH 1/1] " Sreekanth Reddy
2022-10-30 11:52 ` Christoph Hellwig
2022-10-30 11:57 ` Christoph Hellwig
2023-01-02 11:17 ` Martin Wilck
2023-01-02 13:06 ` Martin K. Petersen
2023-01-24 9:37 ` Salvatore Bonaccorso
2023-02-22 16:44 ` Salvatore Bonaccorso [this message]
2023-02-27 14:07 ` Thorsten Leemhuis
2023-03-03 9:39 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-04 9:16 ` Salvatore Bonaccorso
2023-03-07 1:39 ` Martin K. Petersen
2023-03-07 15:04 ` Martin Wilck
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=Y/ZGe8c1XyqSuCSk@eldamar.lan \
--to=carnil@debian.org \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mwilck@suse.com \
--cc=regressions@lists.linux.dev \
--cc=sreekanth.reddy@broadcom.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