All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: stefan.huebner@stud.tu-ilmenau.de
Cc: linux-ide@vger.kernel.org, jgarzik@pobox.com
Subject: Re: Maybe a bug in libata-core
Date: Tue, 24 Aug 2010 09:27:57 +0200	[thread overview]
Message-ID: <4C73747D.7090305@kernel.org> (raw)
In-Reply-To: <4C72F929.6090401@stud.tu-ilmenau.de>

Hello,

On 08/24/2010 12:41 AM, Stefan /*St0fF*/ Hübner wrote:
> As far as I know my code I thought I did send enough data.  Maybe I'm
> misunderstanding something: I valloc'ated block_count*logical_block_size
> bytes, filled them with data and presented this buffer to the
> sg_io_hdr_t structure by setting dxfer_len to the length of the buffer,
> setting dxferp to a pointer to the buffer and setting the
> dxfer_direction to SG_DXFER_TO_DEV.
> 
> The only thing coming to my mind would be overflow of dxfer_len, but as
> this is a unsigned int - wouldn't it be 32 bits wide? (and by that
> accepting f.e. 64k*512 bytes = 33 554 432 bytes (32M, needing 25 bits))
> 
> Any other suggestions, or do I have to present the code?

Yeah, posting a simple test case would be the best way to proceed
here.

Thanks.

-- 
tejun

  reply	other threads:[~2010-08-24  7:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-23  0:52 Fwd: Maybe a bug in libata-core Stefan /*St0fF*/ Hübner
2010-08-23  9:16 ` Tejun Heo
2010-08-23  9:27   ` [PATCH #upstream-fixes] libata: be less of a drama queen on empty data commands Tejun Heo
2010-08-23  9:44   ` Maybe a bug in libata-core Alan Cox
2010-08-23  9:27     ` Tejun Heo
2010-08-23 22:41   ` Stefan /*St0fF*/ Hübner
2010-08-24  7:27     ` Tejun Heo [this message]
2010-09-09  5:42       ` Stefan /*St0fF*/ Hübner
  -- strict thread matches above, loose matches on Subject: below --
2010-08-20 21:48 Stefan Hübner

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=4C73747D.7090305@kernel.org \
    --to=tj@kernel.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=stefan.huebner@stud.tu-ilmenau.de \
    /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.