public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Lougher <phillip@lougher.demon.co.uk>
To: kernel-janitors@vger.kernel.org
Subject: Re: squashfs: enhance parallel I/O
Date: Fri, 08 Nov 2013 01:34:38 +0000	[thread overview]
Message-ID: <527C3FAE.1040906@lougher.demon.co.uk> (raw)
In-Reply-To: <20131106161836.GN15603@elgon.mountain>

On 08/11/13 01:27, Minchan Kim wrote:
> On Thu, Nov 7, 2013 at 2:33 AM, Phillip Lougher
> <phillip.lougher@gmail.com>wrote:
>
>> On Wed, Nov 6, 2013 at 4:18 PM, Dan Carpenter <dan.carpenter@oracle.com>wrote:
>>
>>> Hello Minchan Kim,
>>>
>>> This is a semi-automatic email about new static checker warnings.
>>>
>>> The patch 8ae6a7f5a3a8: "squashfs: enhance parallel I/O" from Oct 28,
>>> 2013, leads to the following Smatch complaint:
>>>
>>> fs/squashfs/decompressor_multi.c:124 squashfs_decompressor_destroy()
>>>           error: we previously assumed 'stream' could be null (see line
>>> 111)
>>>
>>> fs/squashfs/decompressor_multi.c
>>>     110          struct squashfs_stream *stream = msblk->stream;
>>>     111          if (stream) {
>>>                      ^^^^^^
>>> Patch introduces a check.
>>>
>>>     112                  struct decomp_stream *decomp_strm;
>>>     113
>>>     114                  while (!list_empty(&stream->strm_list)) {
>>>     115                          decomp_strm >>> list_entry(stream->strm_list.prev,
>>>     116                                                  struct
>>> decomp_stream, list);
>>>     117                          list_del(&decomp_strm->list);
>>>     118
>>>   msblk->decompressor->free(decomp_strm->stream);
>>>     119                          kfree(decomp_strm);
>>>     120                          stream->avail_decomp--;
>>>     121                  }
>>>     122          }
>>>     123
>>>     124          WARN_ON(stream->avail_decomp);
>>>     125          kfree(stream->comp_opts);
>>>                        ^^^^^^^^^^^^^^^^^
>>>
>>
>> Hi Minchan,
>>
>> These two lines should be moved into the scope of the if (stream) { } ...
>>
>> Do you want to send a V3 patch?  Or I can add a fix-up patch to this V2
>> patch,
>> whatever you prefer.
>>
>
>
> My bad, :(
> Confirmed.
>
> Phillip, Please add a fix-up patch to v2 patch.
> Thanks, Dan and Phillip.
>

np :-)   I'll send the fix-up patch tomorrow.

Dan, I'll credit you with a Reported-by, unless you object.

Phillip

>


  reply	other threads:[~2013-11-08  1:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 16:18 squashfs: enhance parallel I/O Dan Carpenter
2013-11-08  1:34 ` Phillip Lougher [this message]
2013-11-08  7:42 ` Dan Carpenter

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=527C3FAE.1040906@lougher.demon.co.uk \
    --to=phillip@lougher.demon.co.uk \
    --cc=kernel-janitors@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox