From: Peter Xu <peterx@redhat.com>
To: Prasad Pandit <ppandit@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
Prasad Pandit <pjp@fedoraproject.org>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH] vhost: release memory objects in error path
Date: Fri, 26 May 2023 10:35:11 -0400 [thread overview]
Message-ID: <ZHDDn62S3MhwLhIp@x1n> (raw)
In-Reply-To: <CAE8KmOyeV2HB-Fd5PsqVPh7NZBQ7KRH9CrP_7xOsHLac2dwFVA@mail.gmail.com>
On Fri, May 26, 2023 at 12:24:07PM +0530, Prasad Pandit wrote:
> Hello Peter, all
>
> On Thu, 25 May 2023 at 18:33, Peter Xu <peterx@redhat.com> wrote:
>
> > IIRC this bug used to only reproduce on rt kernels, is it still the case?
> >
>
> * Yes, it's a same crash.
>
>
> > Here besides doing correct unregister, does it also mean that even if
> > event_notifier_init() failed there's totally no error message anywhere?
> > Should we dump something when it fails? And did you check why that failed?
> >
>
> * In the qemu logs we see following error
>
> VHOST_OPS_DEBUG(r, "vhost_set_mem_table failed");
> goto fail_mem
>
> After this execution likely did not reach the event_notifier_init() call,
> because: goto fail_mem.
Ah so it's not about eventfd, okay!
>
> * But in case it fails, no error message gets logged. Do we want to add it
> in this same patch?
I see you already sent one, will read.
Thanks!
--
Peter Xu
prev parent reply other threads:[~2023-05-26 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 18:10 [PATCH] vhost: release memory objects in error path P J P
2023-05-25 13:02 ` Peter Xu
2023-05-26 6:54 ` Prasad Pandit
2023-05-26 14:35 ` Peter Xu [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=ZHDDn62S3MhwLhIp@x1n \
--to=peterx@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.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).