All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH][linux 2.6.18] remove pointless error handling in scsiback
Date: Wed, 02 Jul 2014 14:38:12 +0200	[thread overview]
Message-ID: <53B3FD34.2000401@suse.com> (raw)
In-Reply-To: <53B41856020000780001F81B@mail.emea.novell.com>

On 07/02/2014 02:33 PM, Jan Beulich wrote:
>>>> On 02.07.14 at 14:27, <JBeulich@suse.com> wrote:
>>>>> On 02.07.14 at 14:13, <JGross@suse.com> wrote:
>>> On 07/02/2014 01:57 PM, Jan Beulich wrote:
>>>> @@ -229,8 +230,8 @@ static void __report_luns(pending_req_t
>>>>    	unsigned int req_bufflen = 0;
>>>>    	unsigned int actual_len = 0;
>>>>    	unsigned int retry_cnt = 0;
>>>
>>> When you are cleaning up local variables, IMHO you could remove above 3
>>> unneeded initializations, too.
>>
>> Certainly not retry_cnt, but perhaps you meant (apart from the other
>> two visible here) alloc_luns (immediately prior to the first context line).

Sorry, yes.

>> Yes, I guess I'll do that.
>
> And indeed very useful to have this done, as it resulted in me spotting
> that alloc_len was of type unsigned char, i.e. setting us up for memory
> corruption as soon as the total buffer size needed would exceed 255
> bytes. Fixed at once (and I take it that this doesn't invalidate your
> Reviewed-by).

In this case covered by "In any case" :-)

Juergen

  reply	other threads:[~2014-07-02 12:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02  7:26 [PATCH][linux 2.6.18] remove pointless error handling in scsiback jgross
2014-07-02 11:57 ` Jan Beulich
2014-07-02 12:13   ` Jürgen Groß
2014-07-02 12:27     ` Jan Beulich
2014-07-02 12:33       ` Jan Beulich
2014-07-02 12:38         ` Jürgen Groß [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-07-01 15:27 jgross
2014-07-01 15:39 ` Jan Beulich
2014-07-01 18:51   ` Jürgen Groß
2014-07-02  6:52     ` Jan Beulich
2014-07-02  7:08       ` Juergen Gross

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=53B3FD34.2000401@suse.com \
    --to=jgross@suse.com \
    --cc=JBeulich@suse.com \
    --cc=xen-devel@lists.xen.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.