From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Sage Weil <sage@redhat.com>, Alex Elder <elder@kernel.org>,
Mike Christie <mchristi@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rbd: Fix uninitialized variable use in rbd_acquire_lock
Date: Fri, 14 Jul 2017 19:25:37 +0800 [thread overview]
Message-ID: <cfedb533-916a-5a5b-13f4-eb66cbe0d080@huawei.com> (raw)
In-Reply-To: <CAOi1vP8cn91_JXdM9nRSn7=7qMshxc2d4q4NCEC2hONsnPajYw@mail.gmail.com>
On 2017/7/14 18:06, Ilya Dryomov wrote:
> On Thu, Jul 13, 2017 at 9:46 AM, Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>> drivers/block/rbd.c: In function 'rbd_acquire_lock':
>> drivers/block/rbd.c:3602:44: error: 'ret' may be used uninitialized in this function [-Werror=maybe-uninitialized]
>>
>> Silence the warning, found it when built old kernel(3.10) with
>> OBS(opensuse build service).
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>> drivers/block/rbd.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/block/rbd.c b/drivers/block/rbd.c
>> index b008b6a..b640ad8 100644
>> --- a/drivers/block/rbd.c
>> +++ b/drivers/block/rbd.c
>> @@ -3435,7 +3435,7 @@ static void rbd_acquire_lock(struct work_struct *work)
>> struct rbd_device *rbd_dev = container_of(to_delayed_work(work),
>> struct rbd_device, lock_dwork);
>> enum rbd_lock_state lock_state;
>> - int ret;
>> + int ret = 0;
>>
>> dout("%s rbd_dev %p\n", __func__, rbd_dev);
>> again:
>
> How did you get rbd_acquire_lock() into 3.10?
Using CentOS 7.3.
>
> Thanks,
>
> Ilya
>
>
next prev parent reply other threads:[~2017-07-14 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 7:46 Kefeng Wang
2017-07-14 10:06 ` Ilya Dryomov
2017-07-14 11:25 ` Kefeng Wang [this message]
2017-07-17 15:08 ` Ilya Dryomov
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=cfedb533-916a-5a5b-13f4-eb66cbe0d080@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=elder@kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchristi@redhat.com \
--cc=sage@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®