All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akinobu Mita <akinobu.mita@gmail.com>
To: Sagi Grimberg <sagig@dev.mellanox.co.il>
Cc: target-devel@vger.kernel.org,
	Nicholas Bellinger <nab@linux-iscsi.org>,
	Asias He <asias@redhat.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2/2] target/rd: Don't pass imcomplete scatterlist entries to sbc_dif_verify_*
Date: Sun, 5 Apr 2015 21:42:46 +0900	[thread overview]
Message-ID: <CAC5umyivMAXcO=OqSieEmTO4SVfLky29rjfcSaGa=VTi7iNHLg@mail.gmail.com> (raw)
In-Reply-To: <55210A27.5020001@dev.mellanox.co.il>

2015-04-05 19:10 GMT+09:00 Sagi Grimberg <sagig@dev.mellanox.co.il>:
> On 4/4/2015 3:24 PM, Akinobu Mita wrote:
>>
>> The scatterlist for protection information which is passed to
>> sbc_dif_verify_read() or sbc_dif_verify_write() requires that
>> neighboring scatterlist entries are contiguous or chained so that they
>> can be iterated by sg_next().
>>
>> However, the protection information for RD-MCP backends could be located
>> in the multiple scatterlist arrays when the ramdisk space is too large.
>> So if the read/write request straddles this boundary,
>> sbc_dif_verify_read()
>> or sbc_dif_verify_write() can't iterate all scatterlist entries.
>>
>> This fixes it by allocating temporary scatterlist if it is needed.
>>
>> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
>> Cc: Nicholas Bellinger <nab@linux-iscsi.org>
>> Cc: Asias He <asias@redhat.com>
>> Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
>> Cc: Christoph Hellwig <hch@lst.de>
>> Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
>> Cc: target-devel@vger.kernel.org
>> Cc: linux-scsi@vger.kernel.org
>> ---
>>   drivers/target/target_core_rd.c | 39
>> +++++++++++++++++++++++++++++++++++----
>>   1 file changed, 35 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/target/target_core_rd.c
>> b/drivers/target/target_core_rd.c
>> index 4d614c9..19c893d 100644
>> --- a/drivers/target/target_core_rd.c
>> +++ b/drivers/target/target_core_rd.c
>> @@ -387,11 +387,12 @@ static sense_reason_t rd_do_prot_rw(struct se_cmd
>> *cmd, bool is_write)
>>         struct se_device *se_dev = cmd->se_dev;
>>         struct rd_dev *dev = RD_DEV(se_dev);
>>         struct rd_dev_sg_table *prot_table;
>> +       bool need_to_release = false;
>>         struct scatterlist *prot_sg;
>>         u32 sectors = cmd->data_length / se_dev->dev_attrib.block_size;
>> -       u32 prot_offset, prot_page;
>> +       u32 prot_offset, prot_page, prot_npages;
>>         u64 tmp;
>> -       sense_reason_t rc;
>> +       sense_reason_t rc = TCM_LOGICAL_UNIT_COMMUNICATION_FAILURE;
>>         sense_reason_t (*dif_verify)(struct se_cmd *, sector_t, unsigned
>> int,
>>                         unsigned int, struct scatterlist *, int) =
>>                 is_write ?  sbc_dif_verify_write : sbc_dif_verify_read;
>> @@ -404,10 +405,40 @@ static sense_reason_t rd_do_prot_rw(struct se_cmd
>> *cmd, bool is_write)
>>         if (!prot_table)
>>                 return TCM_LOGICAL_UNIT_COMMUNICATION_FAILURE;
>>
>> -       prot_sg = &prot_table->sg_table[prot_page -
>> -                                       prot_table->page_start_offset];
>> +       prot_npages = DIV_ROUND_UP(prot_offset + sectors *
>> se_dev->prot_length,
>> +                                  PAGE_SIZE);
>> +
>> +       /* prot pages straddles multiple scatterlist tables */
>> +       if (prot_table->page_end_offset < prot_page + prot_npages - 1) {
>> +               int i;
>> +
>> +               prot_sg = kcalloc(prot_npages, sizeof(*prot_sg),
>> GFP_KERNEL);
>> +               if (!prot_sg)
>> +                       return TCM_LOGICAL_UNIT_COMMUNICATION_FAILURE;
>> +
>> +               need_to_release = true;
>> +               sg_init_table(prot_sg, prot_npages);
>> +
>> +               for (i = 0; i < prot_npages; i++) {
>> +                       if (prot_page + i > prot_table->page_end_offset) {
>> +                               prot_table = rd_get_prot_table(dev,
>> +                                                               prot_page
>> + i);
>> +                               if (!prot_table)
>> +                                       goto out;
>> +                               sg_unmark_end(&prot_sg[i - 1]);
>> +                       }
>> +                       prot_sg[i] = prot_table->sg_table[prot_page + i -
>> +
>> prot_table->page_start_offset];
>> +               }
>> +       } else {
>> +               prot_sg = &prot_table->sg_table[prot_page -
>> +
>> prot_table->page_start_offset];
>> +       }
>>
>>         rc = dif_verify(cmd, cmd->t_task_lba, sectors, 0, prot_sg,
>> prot_offset);
>> +out:
>> +       if (need_to_release)
>> +               kfree(prot_sg);
>
>
> I think it is safe to free prot_sg if you just make sure to initialize
> it to NULL at declaration time, no need for 'need_to_release'.

'need_to_release' is required to avoid kfree when 'prot_sg' is
initialized to a pointer in the real prot space (i.e. "else" case above).

  reply	other threads:[~2015-04-05 12:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-04 12:24 [PATCH 1/2] target/rd: reduce code duplication in rd_execute_rw() Akinobu Mita
2015-04-04 12:24 ` [PATCH 2/2] target/rd: Don't pass imcomplete scatterlist entries to sbc_dif_verify_* Akinobu Mita
2015-04-05 10:10   ` Sagi Grimberg
2015-04-05 12:42     ` Akinobu Mita [this message]
2015-04-05 10:01 ` [PATCH 1/2] target/rd: reduce code duplication in rd_execute_rw() Sagi Grimberg
2015-04-05 12:40   ` Akinobu Mita

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='CAC5umyivMAXcO=OqSieEmTO4SVfLky29rjfcSaGa=VTi7iNHLg@mail.gmail.com' \
    --to=akinobu.mita@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=asias@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=nab@linux-iscsi.org \
    --cc=sagig@dev.mellanox.co.il \
    --cc=target-devel@vger.kernel.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: link
Be 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.