All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Boaz Harrosh <openosd@gmail.com>, Jeff Moyer <jmoyer@redhat.com>
Cc: Joe Lawrence <joe.lawrence@stratus.com>,
	linux-kernel@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
	Boaz Harrosh <bharrosh@panasas.com>
Subject: Re: [PATCH v3 0/2] block,scsi: fixup blk_get_request dead queue scenarios
Date: Wed, 27 Aug 2014 10:05:36 -0600	[thread overview]
Message-ID: <53FE01D0.1030902@kernel.dk> (raw)
In-Reply-To: <53FDFE54.6050600@gmail.com>

On 08/27/2014 09:50 AM, Boaz Harrosh wrote:
> On 08/27/2014 05:07 PM, Jens Axboe wrote:
>> On 08/26/2014 04:01 PM, Jeff Moyer wrote:
>>> Jens Axboe <axboe@kernel.dk> writes:
> <>
>> There's also a bug in osd_initiator.c, _init_blk_request(). We jump to
>> 'out' for IS_ERR(req), which attempts to print or->request, which hasn't
>> been assigned yet. 
> 
> You mean this code:
> 	req = _make_request(q, has_out, has_out ? &or->out : &or->in, flags);
> 	if (IS_ERR(req)) {
> 		ret = PTR_ERR(req);
> 		goto out;
> 	}
> 
> 	or->request = req;
> 
> But _make_request used to already return -ENOMEM as a pointer in req
> So if this is a bug it was not introduced by this patch.

Joe brought this up too, I guess it's been there before this patch.

> And it is not a bug at all the print prints the pointer. The all of
> this code assumes osd_request was allocated ZERO set. the print of %p
> is fine with NULLs (and any number for that matter)

If or->request is NULL initialized, it's fine. I didn't track the path
to check if it was garbage or NULL.

> I have reviewed this patch for osd part, it is fine

Thanks!

-- 
Jens Axboe


  reply	other threads:[~2014-08-27 16:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 19:35 [PATCH v3 0/2] block,scsi: fixup blk_get_request dead queue scenarios Joe Lawrence
2014-07-02 19:35 ` [PATCH v3 1/2] block,scsi: verify return pointer from blk_get_request Joe Lawrence
2014-07-02 19:35 ` [PATCH v3 2/2] block,scsi: fixup blk_get_request dead queue scenarios Joe Lawrence
2014-07-02 20:26 ` [PATCH v3 0/2] " Joe Lawrence
2014-08-26 17:24 ` Jeff Moyer
2014-08-26 21:19   ` Jens Axboe
2014-08-26 21:24     ` Jens Axboe
2014-08-26 21:27     ` Jeff Moyer
2014-08-26 21:33       ` Jens Axboe
2014-08-26 21:37         ` Jens Axboe
2014-08-26 22:01           ` Jeff Moyer
2014-08-27 14:07             ` Jens Axboe
2014-08-27 15:33               ` Joe Lawrence
2014-08-27 15:50               ` Boaz Harrosh
2014-08-27 16:05                 ` Jens Axboe [this message]
2014-08-27 14:13             ` Joe Lawrence

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=53FE01D0.1030902@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=bharrosh@panasas.com \
    --cc=jkosina@suse.cz \
    --cc=jmoyer@redhat.com \
    --cc=joe.lawrence@stratus.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openosd@gmail.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 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.