From: Oleg Nesterov <oleg@redhat.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: linux-mips@vger.kernel.org
Subject: Re: mips: question about switch_to()->__sanitize_fcr31()
Date: Tue, 28 Nov 2023 21:58:54 +0100 [thread overview]
Message-ID: <20231128205854.GA29462@redhat.com> (raw)
In-Reply-To: <20231121135220.GA952@redhat.com>
ping.
On 11/21, Oleg Nesterov wrote:
>
> Hello,
>
> I know absolutely nothing about arch/mips, I can't even find the
> definition of "current" or the caller of switch_to().
>
> So, __sanitize_fcr31() is called by switch_to() and it does
> force_fcr31_sig(fcr31, pc, next).
>
> Was "current" already updated at this stage so that next == current?
>
>
> Why I am asking. I want to add
>
> // otherwise the usage of ->siglock is not safe
> WARN_ON(!(t == current || task_is_traced(t)));
>
> into force_sig_info_to_task() and simplify it a bit, but I don't
> know if "t == current" is already true at the start of switch_to().
>
>
> Thanks,
>
> Oleg.
prev parent reply other threads:[~2023-11-28 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 13:52 mips: question about switch_to()->__sanitize_fcr31() Oleg Nesterov
2023-11-28 20:58 ` Oleg Nesterov [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=20231128205854.GA29462@redhat.com \
--to=oleg@redhat.com \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=tsbogend@alpha.franken.de \
/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).