All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/6] scsi tgt: kill length alignment test in bin_map_user
Date: Thu, 16 Feb 2006 21:00:10 +0100	[thread overview]
Message-ID: <20060216200010.GZ4203@suse.de> (raw)
In-Reply-To: <1140119617.20193.49.camel@max>

On Thu, Feb 16 2006, Mike Christie wrote:
> Subject: [PATCH] block layer: kill length alignment test in bin_map_user
> 
> The tgt project is mapping in bios using bio_map_user. The current targets
> do not need their len to be aligned with a queue limit so this check is
> causing some problems. Note: pointers passed into the kernel are properly
> aligned by usersapace tgt code so the uaddr check in bio_map_user is ok.
> 
> 
> The major user, blk_bio_map_user checks for the len before mapping
> so it is not affected by this patch.
> 
> And the semi-newly added user blk_rq_map_user_iov has been failing
> out when the len is not aligned properly so maybe people have been
> good and not sending misaligned lens or that path is not used very
> often and this change will not be very dangerous. st and sg do not
> check the length and we have not seen any problem reports from those
> wider used paths so this patch should be fairly safe - for mm 
> and wider testing at least.

As previously discussed, this is fine with me. It's a mixed check
anyways, if we need length check in the future it should be a seperate
attribute.

-- 
Jens Axboe


      reply	other threads:[~2006-02-16 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 19:53 [PATCH 2/6] scsi tgt: kill length alignment test in bin_map_user Mike Christie
2006-02-16 20:00 ` Jens Axboe [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=20060216200010.GZ4203@suse.de \
    --to=axboe@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    /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.