From: Christoph Hellwig <hch@lst.de> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: Christoph Hellwig <hch@lst.de>, kernel test robot <oliver.sang@intel.com>, Jens Axboe <axboe@kernel.dk>, LKML <linux-kernel@vger.kernel.org>, lkp@lists.01.org, kernel test robot <lkp@intel.com>, "H. Peter Anvin" <hpa@zytor.com>, Borislav Petkov <bp@alien8.de> Subject: Re: [ide] b7fb14d3ac: EIP:ioread32_rep Date: Tue, 6 Jul 2021 16:36:47 +0200 [thread overview] Message-ID: <20210706143647.GA28289@lst.de> (raw) In-Reply-To: <CAHk-=wj_Gfqkdp+K3iCiqMjAZQK_BrRWDs2eOS_BAw=bB=CdRw@mail.gmail.com> On Mon, Jul 05, 2021 at 01:00:09PM -0700, Linus Torvalds wrote: > It might perhaps be worth adding some kind of > > WARN_ON_ONCE(offset & 511); > > in the callchain somewhere for that ata_queued_cmd(). But at that > point I no longer know the code. Yeah, there's usually a huge offset into the page. The otherwise similar ATAPI code actually has checks to chunk it up and not cross page boundaries, and copying that over fixes the problem. The testbot config then crashes in an infiband driver, but disabling that driver entirely makes it boot fine: diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c index ae7189d1a568..018f021c45a3 100644 --- a/drivers/ata/libata-sff.c +++ b/drivers/ata/libata-sff.c @@ -651,7 +651,7 @@ static void ata_pio_sector(struct ata_queued_cmd *qc) int do_write = (qc->tf.flags & ATA_TFLAG_WRITE); struct ata_port *ap = qc->ap; struct page *page; - unsigned int offset; + unsigned int offset, count; unsigned char *buf; if (!qc->cursg) { @@ -670,16 +670,22 @@ static void ata_pio_sector(struct ata_queued_cmd *qc) DPRINTK("data %s\n", qc->tf.flags & ATA_TFLAG_WRITE ? "write" : "read"); + /* don't overrun current sg */ + count = min(qc->cursg->length - qc->cursg_ofs, qc->sect_size); + + /* don't cross page boundaries */ + count = min(count, (unsigned int)PAGE_SIZE - offset); + /* do the actual data transfer */ buf = kmap_atomic(page); - ap->ops->sff_data_xfer(qc, buf + offset, qc->sect_size, do_write); + ap->ops->sff_data_xfer(qc, buf + offset, count, do_write); kunmap_atomic(buf); if (!do_write && !PageSlab(page)) flush_dcache_page(page); - qc->curbytes += qc->sect_size; - qc->cursg_ofs += qc->sect_size; + qc->curbytes += count; + qc->cursg_ofs += count; if (qc->cursg_ofs == qc->cursg->length) { qc->cursg = sg_next(qc->cursg);
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de> To: lkp@lists.01.org Subject: Re: [ide] b7fb14d3ac: EIP:ioread32_rep Date: Tue, 06 Jul 2021 16:36:47 +0200 [thread overview] Message-ID: <20210706143647.GA28289@lst.de> (raw) In-Reply-To: <CAHk-=wj_Gfqkdp+K3iCiqMjAZQK_BrRWDs2eOS_BAw=bB=CdRw@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1885 bytes --] On Mon, Jul 05, 2021 at 01:00:09PM -0700, Linus Torvalds wrote: > It might perhaps be worth adding some kind of > > WARN_ON_ONCE(offset & 511); > > in the callchain somewhere for that ata_queued_cmd(). But at that > point I no longer know the code. Yeah, there's usually a huge offset into the page. The otherwise similar ATAPI code actually has checks to chunk it up and not cross page boundaries, and copying that over fixes the problem. The testbot config then crashes in an infiband driver, but disabling that driver entirely makes it boot fine: diff --git a/drivers/ata/libata-sff.c b/drivers/ata/libata-sff.c index ae7189d1a568..018f021c45a3 100644 --- a/drivers/ata/libata-sff.c +++ b/drivers/ata/libata-sff.c @@ -651,7 +651,7 @@ static void ata_pio_sector(struct ata_queued_cmd *qc) int do_write = (qc->tf.flags & ATA_TFLAG_WRITE); struct ata_port *ap = qc->ap; struct page *page; - unsigned int offset; + unsigned int offset, count; unsigned char *buf; if (!qc->cursg) { @@ -670,16 +670,22 @@ static void ata_pio_sector(struct ata_queued_cmd *qc) DPRINTK("data %s\n", qc->tf.flags & ATA_TFLAG_WRITE ? "write" : "read"); + /* don't overrun current sg */ + count = min(qc->cursg->length - qc->cursg_ofs, qc->sect_size); + + /* don't cross page boundaries */ + count = min(count, (unsigned int)PAGE_SIZE - offset); + /* do the actual data transfer */ buf = kmap_atomic(page); - ap->ops->sff_data_xfer(qc, buf + offset, qc->sect_size, do_write); + ap->ops->sff_data_xfer(qc, buf + offset, count, do_write); kunmap_atomic(buf); if (!do_write && !PageSlab(page)) flush_dcache_page(page); - qc->curbytes += qc->sect_size; - qc->cursg_ofs += qc->sect_size; + qc->curbytes += count; + qc->cursg_ofs += count; if (qc->cursg_ofs == qc->cursg->length) { qc->cursg = sg_next(qc->cursg);
next prev parent reply other threads:[~2021-07-06 14:36 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-07-04 15:00 [ide] b7fb14d3ac: EIP:ioread32_rep kernel test robot 2021-07-04 15:00 ` kernel test robot 2021-07-05 12:57 ` Christoph Hellwig 2021-07-05 12:57 ` Christoph Hellwig 2021-07-05 20:00 ` Linus Torvalds 2021-07-05 20:00 ` Linus Torvalds 2021-07-06 14:36 ` Christoph Hellwig [this message] 2021-07-06 14:36 ` Christoph Hellwig 2021-07-06 19:08 ` Linus Torvalds 2021-07-06 19:08 ` Linus Torvalds 2021-07-07 8:12 ` Christoph Hellwig 2021-07-07 8:12 ` Christoph Hellwig 2021-07-07 8:35 ` Christoph Hellwig 2021-07-07 8:35 ` Christoph Hellwig 2021-07-07 19:05 ` Linus Torvalds 2021-07-07 19:05 ` 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=20210706143647.GA28289@lst.de \ --to=hch@lst.de \ --cc=axboe@kernel.dk \ --cc=bp@alien8.de \ --cc=hpa@zytor.com \ --cc=linux-kernel@vger.kernel.org \ --cc=lkp@intel.com \ --cc=lkp@lists.01.org \ --cc=oliver.sang@intel.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: linkBe 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.