From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Bharath SM <bharathsm@microsoft.com>,
Shyam Prasad N <nspmangalore@gmail.com>,
Steve French <smfrench@gmail.com>,
Robbie Harwood <rharwood@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
keyrings@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-crypto@vger.kernel.org, kexec@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] keys: Miscellaneous fixes/changes
Date: Tue, 21 Mar 2023 12:21:54 -0700 [thread overview]
Message-ID: <CAHk-=wi2yeuwCxvB18=AWG+YKnMgd28WGkHFMqTyMA=59cw3rg@mail.gmail.com> (raw)
In-Reply-To: <8d532de2-bf3a-dee4-1cad-e11714e914d0@kernel.dk>
On Tue, Mar 21, 2023 at 12:16 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> I haven't seen the patch yet as it hasn't been pushed,
Well, it went out a couple of minutes before your email, so it's out now.
> It may make sense to add some debug check for
> PF_KTHREAD having TIF_NOTIFY_RESUME set, or task_work pending for that
> matter, as that is generally not workable without doing something to
> handle it explicitly.
Yeah, I guess we could have some generic check for that. I'm not sure
where it would be. Scheduler?
Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Bharath SM <bharathsm@microsoft.com>,
Shyam Prasad N <nspmangalore@gmail.com>,
Steve French <smfrench@gmail.com>,
Robbie Harwood <rharwood@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
keyrings@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-crypto@vger.kernel.org, kexec@lists.infradead.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] keys: Miscellaneous fixes/changes
Date: Tue, 21 Mar 2023 12:21:54 -0700 [thread overview]
Message-ID: <CAHk-=wi2yeuwCxvB18=AWG+YKnMgd28WGkHFMqTyMA=59cw3rg@mail.gmail.com> (raw)
In-Reply-To: <8d532de2-bf3a-dee4-1cad-e11714e914d0@kernel.dk>
On Tue, Mar 21, 2023 at 12:16 PM Jens Axboe <axboe@kernel.dk> wrote:
>
> I haven't seen the patch yet as it hasn't been pushed,
Well, it went out a couple of minutes before your email, so it's out now.
> It may make sense to add some debug check for
> PF_KTHREAD having TIF_NOTIFY_RESUME set, or task_work pending for that
> matter, as that is generally not workable without doing something to
> handle it explicitly.
Yeah, I guess we could have some generic check for that. I'm not sure
where it would be. Scheduler?
Linus
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2023-03-21 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 16:43 [GIT PULL] keys: Miscellaneous fixes/changes David Howells
2023-03-21 16:43 ` David Howells
2023-03-21 18:48 ` Linus Torvalds
2023-03-21 18:48 ` Linus Torvalds
2023-03-21 19:16 ` Jens Axboe
2023-03-21 19:16 ` Jens Axboe
2023-03-21 19:21 ` Linus Torvalds [this message]
2023-03-21 19:21 ` Linus Torvalds
2023-03-21 19:32 ` Jens Axboe
2023-03-21 19:32 ` Jens Axboe
2023-03-21 19:12 ` pr-tracker-bot
2023-03-21 19:12 ` pr-tracker-bot
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='CAHk-=wi2yeuwCxvB18=AWG+YKnMgd28WGkHFMqTyMA=59cw3rg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bharathsm@microsoft.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko@kernel.org \
--cc=kexec@lists.infradead.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=rharwood@redhat.com \
--cc=smfrench@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.