From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <JBottomley@parallels.com>,
Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] scsi: fix random memory corruption with scsi-mq + T10 PI
Date: Thu, 11 Dec 2014 14:18:22 -0800 [thread overview]
Message-ID: <1418336302.1709.1.camel@haakon3.risingtidesystems.com> (raw)
In-Reply-To: <54862444.3020901@cybernetics.com>
Hi Tony,
On Mon, 2014-12-08 at 17:20 -0500, Tony Battersby wrote:
> This fixes random memory corruption triggered when all three of the
> following are true:
>
> * scsi-mq enabled
> * T10 Protection Information (DIF) enabled
> * SCSI host with sg_tablesize > SCSI_MAX_SG_SEGMENTS (128)
>
> The symptoms of this bug are unpredictable memory corruption, BUG()s,
> oopses, lockups, etc., any of which may appear to be completely
> unrelated to the root cause.
>
> Cc: <stable@vger.kernel.org> # 3.17.x, 3.18.x
> Signed-off-by: Tony Battersby <tonyb@cybernetics.com>
>
> ---
>
> I encountered this problem with a QLogic QLE2672 FC HBA using qla2xxx.
> On my system, this would trigger BUG_ON(atomic_read(&bio->bi_remaining) <= 0)
> in bio_endio(), or a general protection fault in __sg_free_table()
> trying to free prot_sdb, or any number of other weird random problems.
> All of this was caused by cmd->prot_sdb pointing to the wrong memory.
> To see how the memory is allocated, refer to scsi_mq_setup_tags() in
> scsi_lib.c.
>
> For inclusion in 3.19, 3.18.x, and 3.17.x.
>
> --- linux-3.18.0/drivers/scsi/scsi_lib.c.orig 2014-12-08 16:23:28.000000000 -0500
> +++ linux-3.18.0/drivers/scsi/scsi_lib.c 2014-12-08 16:24:00.000000000 -0500
> @@ -1829,7 +1829,9 @@ static int scsi_mq_prep_fn(struct reques
>
> if (scsi_host_get_prot(shost)) {
> cmd->prot_sdb = (void *)sg +
> - shost->sg_tablesize * sizeof(struct scatterlist);
> + min_t(unsigned int,
> + shost->sg_tablesize, SCSI_MAX_SG_SEGMENTS) *
> + sizeof(struct scatterlist);
> memset(cmd->prot_sdb, 0, sizeof(struct scsi_data_buffer));
>
> cmd->prot_sdb->table.sgl =
>
Nice catch.
Reviewed-by: Nicholas Bellinger <nab@linux-iscsi.org>
Adding a CC' to MKP, and HCH so he can pick it up.
--nab
next prev parent reply other threads:[~2014-12-11 22:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 22:20 Tony Battersby
2014-12-11 22:18 ` Nicholas A. Bellinger [this message]
2014-12-15 13:43 ` Christoph Hellwig
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=1418336302.1709.1.camel@haakon3.risingtidesystems.com \
--to=nab@linux-iscsi.org \
--cc=JBottomley@parallels.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tonyb@cybernetics.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
all inboxes | Powered by JetHome®