From: Peter Zijlstra <peterz@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: NeilBrown <neilb@suse.de>, Ingo Molnar <mingo@kernel.org>,
Evgeniy Polyakov <zbr@ioremap.net>,
Stephen Smalley <sds@tycho.nsa.gov>,
Alex Williamson <alex.williamson@redhat.com>,
Oleg Nesterov <oleg@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] signals: Generate warning when flush_signals() is called from non-kthread context
Date: Thu, 7 May 2015 14:54:53 +0200 [thread overview]
Message-ID: <20150507125453.GN17717@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CA+55aFybD6U8_ZbPYMm3pe6ZuNY8acyvCSFOabJd31my6qakDA@mail.gmail.com>
On Sat, May 02, 2015 at 09:27:49AM -0700, Linus Torvalds wrote:
> On Sat, May 2, 2015 at 1:30 AM, NeilBrown <neilb@suse.de> wrote:
> >
> > All the calls in md.c are in a kernel thread so safe, but I'd rather have an
> > explicit "uninterruptible, but no load-average" wait....
>
> Hmm. Our task state is a bitmask anyway, so we could probably just add a
>
> #define __TASK_NOLOAD 16
>
> (and move the EXIT_xyz defines *away* from the list that is actually
> the task state), and teach our load average thing to not count those
> kinds of waits. Then you could just use
>
> TASK_UNINTERRUPTIBLE | __TASK_NOLOAD
>
> to make processes not count towards the load.
>
> Or - probably preferably - we could really clean things up, and make
> things much more like the bitmask it *should* be, and have explicit
> bits for
>
> - SLEEPING/STOPPED/EXITING ("why not running?")
> - LOADAVG (accounted towards load)
> - WAKESIG (ie "interruptible")
> - WAKEKILL (this we already have)
>
> and just make the rule be that we use "__TASK_xyz" for the actual
> individual bits, and "TASK_xyz" for the helper combinations. So then
> we'd have
>
> #define TASK_UNINTERRUPTIBLE (__TASK_SLEEPING | __TASK_LOADAVG)
> #define TASK_INTERRUPTIBLE (__TASK_SLEEPING | __TASK_WAKESIG)
> #define TASK_KILLABLE (__TASK_SLEEPING | __TASK_WAKEKILL)
> #define TASK_NOLOADAVG (__TASK_SLEEPING)
>
> which is almost certainly how this *should* have been done, but isn't,
> because of historical use.
>
> Cleaning up like that *should* be fairly simple, but I'd be a bit
> nervous about getting all the state comparisons right (we have an
> unholy mix of "check this bit" and "check this whole state", and we'd
> need to make sure we get those cases all right).
>
> Ingo, what do you think? This is mostly a scheduler interface issue..
Hehe, a little something like this:
https://lkml.org/lkml/2013/11/12/710
Lemme go clean that up and finish it :-)
next prev parent reply other threads:[~2015-05-07 12:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-01 17:40 [GIT PULL] VFIO fixes for v4.1-rc2 Alex Williamson
2015-05-01 18:37 ` Linus Torvalds
2015-05-01 18:48 ` Alex Williamson
2015-05-01 20:23 ` Linus Torvalds
2015-05-01 22:03 ` Alex Williamson
2015-05-01 19:38 ` [PATCH] signals: Generate warning when flush_signals() is called from non-kthread context Ingo Molnar
2015-05-02 8:30 ` NeilBrown
2015-05-02 16:27 ` Linus Torvalds
2015-05-07 12:54 ` Peter Zijlstra [this message]
2015-05-04 17:35 ` Oleg Nesterov
2015-05-07 13:33 ` Jiri Kosina
2015-05-07 22:37 ` NeilBrown
2015-05-02 11:56 ` Evgeniy Polyakov
2015-05-02 16:33 ` Richard Weinberger
2015-05-03 17:34 ` Oleg Nesterov
2015-05-04 16:45 ` [PATCH 0/1] signals: don't abuse __flush_signals() in selinux_bprm_committed_creds() Oleg Nesterov
2015-05-04 16:45 ` [PATCH 1/1] " Oleg Nesterov
2015-05-04 19:43 ` Paul Moore
2015-05-06 10:19 ` [PATCH] signals: Generate warning when flush_signals() is called from non-kthread context Ingo Molnar
2015-05-01 20:11 ` [GIT PULL] VFIO fixes for v4.1-rc2 Richard Weinberger
2015-05-01 21:09 ` Richard Weinberger
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=20150507125453.GN17717@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alex.williamson@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=neilb@suse.de \
--cc=oleg@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=torvalds@linux-foundation.org \
--cc=zbr@ioremap.net \
/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
all inboxes | Powered by JetHome®