From: David Hildenbrand <david@redhat.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Borislav Petkov <bp@alien8.de>,
virtualization@lists.linux-foundation.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] virtio_balloon: Fix unused label warning
Date: Sun, 16 Feb 2020 09:05:02 +0100 [thread overview]
Message-ID: <FF9BD3B9-7D78-4470-89CD-6F6831F4B6A6@redhat.com> (raw)
In-Reply-To: <20200216074639.GA25292@ubuntu-m2-xlarge-x86>
> Am 16.02.2020 um 08:46 schrieb Nathan Chancellor <natechancellor@gmail.com>:
>
> On Mon, Feb 10, 2020 at 10:33:28AM +0100, Borislav Petkov wrote:
>> From: Borislav Petkov <bp@suse.de>
>>
>> Fix
>>
>> drivers/virtio/virtio_balloon.c: In function ‘virtballoon_probe’:
>> drivers/virtio/virtio_balloon.c:963:1: warning: label ‘out_del_vqs’ defined but not used [-Wunused-label]
>> 963 | out_del_vqs:
>> | ^~
>>
>> The CONFIG_BALLOON_COMPACTION ifdeffery should enclose it too.
>>
>> Signed-off-by: Borislav Petkov <bp@suse.de>
>> Cc: David Hildenbrand <david@redhat.com>
>> ---
>> drivers/virtio/virtio_balloon.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
>> index 7bfe365d9372..b6ed5f8bccb1 100644
>> --- a/drivers/virtio/virtio_balloon.c
>> +++ b/drivers/virtio/virtio_balloon.c
>> @@ -959,9 +959,9 @@ static int virtballoon_probe(struct virtio_device *vdev)
>> iput(vb->vb_dev_info.inode);
>> out_kern_unmount:
>> kern_unmount(balloon_mnt);
>> -#endif
>> out_del_vqs:
>> vdev->config->del_vqs(vdev);
>> +#endif
>
> I noticed the same issue and sent an almost identical patch [1] but I
> kept the call to del_vqs outside of the CONFIG_BALLOON_COMPACTION guard
> since it seems like that should still be called when that config is
> unset, as that was the case before commit 1ad6f58ea936 ("virtio_balloon:
> Fix memory leaks on errors in virtballoon_probe()"). Is this patch fully
> correct? I am not a virtio expert at all, just noticing from a brief
> reading of this function.
I think you are right and this splipped my eyes!
prev parent reply other threads:[~2020-02-16 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 9:33 Borislav Petkov
2020-02-10 9:38 ` David Hildenbrand
2020-02-16 7:46 ` Nathan Chancellor
2020-02-16 8:05 ` David Hildenbrand [this message]
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=FF9BD3B9-7D78-4470-89CD-6F6831F4B6A6@redhat.com \
--to=david@redhat.com \
--cc=bp@alien8.de \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=natechancellor@gmail.com \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®