qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
	Marc Hartmayer <mhartmay@linux.ibm.com>,
	 qemu-devel@nongnu.org, qemu-s390x <qemu-s390x@nongnu.org>,
	virtio-fs@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	 Stefan Liebler <stli@linux.ibm.com>
Subject: Re: [PATCH] virtiofsd: Add `sigreturn` to the seccomp whitelist
Date: Tue, 29 Nov 2022 07:04:22 -0500	[thread overview]
Message-ID: <CAJSP0QWbQpysVn=oAQdvcq0WrBuPVf_MX4fbwobCLTS1AP_Ncg@mail.gmail.com> (raw)
In-Reply-To: <Y4XcByAJBWaCo0sP@work-vm>

To find out:
# perf record -e signal:signal_deliver
...wait for QEMU shutdown...
^C
# perf script
qemu-system-x86_64 2319136 [001] 1062886.415312:
signal:signal_deliver: sig=2 errno=0 code=128 sa_handler=7fc6ccfbabc0
sa_flags=14000004

sig=2 is SIGINT. This is just an example, I didn't run virtiofsd.


  reply	other threads:[~2022-11-29 12:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25 14:39 [PATCH] virtiofsd: Add `sigreturn` to the seccomp whitelist Marc Hartmayer
2022-11-25 16:32 ` [Virtio-fs] " German Maglione
2022-11-28  6:18   ` Christian Borntraeger
2022-11-28  9:00   ` Marc Hartmayer
2022-11-28 10:17     ` German Maglione
2022-12-01  9:44       ` Marc Hartmayer
2022-11-25 20:50 ` Stefan Hajnoczi
2022-11-28 18:47 ` Dr. David Alan Gilbert
2022-11-29  9:38   ` Marc Hartmayer
2022-11-29  9:42     ` Dr. David Alan Gilbert
2022-11-29  9:52       ` Christian Borntraeger
2022-11-29  9:57         ` Christian Borntraeger
2022-11-29 10:16           ` Dr. David Alan Gilbert
2022-11-29 12:04             ` Stefan Hajnoczi [this message]
2022-11-29 10:16           ` Marc Hartmayer

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='CAJSP0QWbQpysVn=oAQdvcq0WrBuPVf_MX4fbwobCLTS1AP_Ncg@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=borntraeger@de.ibm.com \
    --cc=dgilbert@redhat.com \
    --cc=mhartmay@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=stli@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --cc=virtio-fs@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;
as well as URLs for NNTP newsgroup(s).