From: Stefan Hajnoczi <stefanha@redhat.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Lingfeng Yang" <lfy@google.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2] coroutine-ucontext: Save fake stack for pooled coroutine
Date: Wed, 17 Jan 2024 09:07:36 -0500 [thread overview]
Message-ID: <20240117140736.GA1399147@fedora> (raw)
In-Reply-To: <20240117-asan-v2-1-26f9e1ea6e72@daynix.com>
[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]
On Wed, Jan 17, 2024 at 04:06:02PM +0900, Akihiko Odaki wrote:
> Coroutine may be pooled even after COROUTINE_TERMINATE if
> CONFIG_COROUTINE_POOL is enabled and fake stack should be saved in
> such a case to keep AddressSanitizerUseAfterReturn working. Even worse,
> I'm seeing stack corruption without fake stack being saved.
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> Changes in v2:
> - Added missing set_current() (Marc-André Lureau)
> - Added G_STATIC_ASSERT(!IS_ENABLED(CONFIG_TSAN)) (Marc-André Lureau)
> - Renamed terminate() to terminate_asan() for clarity and consistency.
> - Changed terminate_asan() to call start_switch_fiber_asan() for
> consistency.
> - Link to v1: https://lore.kernel.org/r/20240112-asan-v1-1-e330f0d0032c@daynix.com
> ---
> util/coroutine-ucontext.c | 35 ++++++++++++++++++++++++++---------
> 1 file changed, 26 insertions(+), 9 deletions(-)
Thanks, applied to my block tree:
https://gitlab.com/stefanha/qemu/commits/block
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2024-01-17 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-17 7:06 [PATCH v2] coroutine-ucontext: Save fake stack for pooled coroutine Akihiko Odaki
2024-01-17 7:26 ` Marc-André Lureau
2024-01-17 7:29 ` Marc-André Lureau
2024-01-17 14:07 ` Stefan Hajnoczi [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=20240117140736.GA1399147@fedora \
--to=stefanha@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=kwolf@redhat.com \
--cc=lfy@google.com \
--cc=marcandre.lureau@gmail.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).