public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: Zheyu Ma <zheyuma97@gmail.com>,
	s.shtylyov@omp.ru, linux-ide@vger.kernel.org,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v2] ata: pata_marvell: Check the 'bmdma_addr' beforing reading
Date: Mon, 25 Apr 2022 12:18:51 +0200	[thread overview]
Message-ID: <YmZ1i0QYqlMdgck4@kroah.com> (raw)
In-Reply-To: <39f1ac3d-d8d8-1585-360f-ab534dac2a00@opensource.wdc.com>

On Mon, Apr 25, 2022 at 09:38:17AM +0900, Damien Le Moal wrote:
> On 4/22/22 08:47, Damien Le Moal wrote:
> > On 4/21/22 10:39, Zheyu Ma wrote:
> >> Before detecting the cable type on the dma bar, the driver should check
> >> whether the 'bmdma_addr' is zero, which means the adapter does not
> >> support DMA, otherwise we will get the following error:
> >>
> >> [    5.146634] Bad IO access at port 0x1 (return inb(port))
> >> [    5.147206] WARNING: CPU: 2 PID: 303 at lib/iomap.c:44 ioread8+0x4a/0x60
> >> [    5.150856] RIP: 0010:ioread8+0x4a/0x60
> >> [    5.160238] Call Trace:
> >> [    5.160470]  <TASK>
> >> [    5.160674]  marvell_cable_detect+0x6e/0xc0 [pata_marvell]
> >> [    5.161728]  ata_eh_recover+0x3520/0x6cc0
> >> [    5.168075]  ata_do_eh+0x49/0x3c0
> >>
> >> Signed-off-by: Zheyu Ma <zheyuma97@gmail.com>
> >> ---Changes in v2:
> >>      - Delete the useless 'else'
> > 
> > Note for future contributions: The change log should be placed *after* 
> > the "---" that comes before the "diff" line below. Otherwise, the change 
> > log pollutes the commit message.
> > 
> > I fixed that and applied to for-5.18-fixes. Thanks.
> 
> I completely overlooked that this needs a CC stable...
> 
> Greg,
> 
> Could you please pickup this commit for stable ?
> In Linus tree/rc4, it is:
> 
> aafa9f958342 ("ata: pata_marvell: Check the 'bmdma_addr' beforing reading")

Now queued up, thanks.

greg k-h

      reply	other threads:[~2022-04-25 10:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220421013920.3503034-1-zheyuma97@gmail.com>
     [not found] ` <e29fd64e-62ea-746e-f0fb-02ce86b4e61e@opensource.wdc.com>
2022-04-25  0:38   ` [PATCH v2] ata: pata_marvell: Check the 'bmdma_addr' beforing reading Damien Le Moal
2022-04-25 10:18     ` Greg KH [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=YmZ1i0QYqlMdgck4@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=s.shtylyov@omp.ru \
    --cc=stable@vger.kernel.org \
    --cc=zheyuma97@gmail.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