From: Andrew Donnellan <ajd@linux.ibm.com>
To: Andrew Melnichenko <andrew@daynix.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
jslaby@suse.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] Fix: buffer overflow during hvc_alloc().
Date: Tue, 7 Apr 2020 16:23:06 +1000 [thread overview]
Message-ID: <06ecf4d9-80d7-fbfd-3f95-9241d8d0d5cd@linux.ibm.com> (raw)
In-Reply-To: <CABcq3pHMSN9vZRrV1xL6nA7HOK-+wnFSEQsqTqFVvKr4usNbOg@mail.gmail.com>
On 6/4/20 6:05 pm, Andrew Melnichenko wrote:
>
> Steps to Reproduce:
>
> 1. boot guest with command [1]
> 2. load and unload virtio_console inside guest with loop.sh
> # cat loop.sh
> while [ 1 ]
> do
> modprobe virtio_console
> lsmod | grep virt
> modprobe -r virtio_console
> lsmod | grep virt
> done
>
>
>
> Actual results:
> Guest reboot and can get vmcore-dmesg.txt file
>
>
> Expected results:
> Guest works well without error
>
>
> Additional info:
> The whole log will attach to the attachments.
>
> Call Trace:
> [ 22.974500] fuse: init (API version 7.31)
> [ 81.498208] ------------[ cut here ]------------
> [ 81.499263] pvqspinlock: lock 0xffffffff92080020 has corrupted
> value 0xc0774ca0!
> [ 81.501000] WARNING: CPU: 0 PID: 785 at
> kernel/locking/qspinlock_paravirt.h:500
[snip]
Thanks!
You should include an appropriate excerpt from this - the WARNING
message and stack trace, and the steps to reproduce - in the commit
message of the patch.
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
prev parent reply other threads:[~2020-04-07 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 20:40 [PATCH] Fix: buffer overflow during hvc_alloc() andrew
2020-04-06 0:31 ` Andrew Donnellan
2020-04-06 8:05 ` Andrew Melnichenko
2020-04-07 6:23 ` Andrew Donnellan [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=06ecf4d9-80d7-fbfd-3f95-9241d8d0d5cd@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=andrew@daynix.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).