From: Tom Zanussi <zanussi@kernel.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Daniel Wagner <wagi@monom.org>,
Clark Williams <williams@redhat.com>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Subject: Re: [ANNOUNCE] 5.4.182-rt71
Date: Sat, 12 Mar 2022 09:56:30 -0600 [thread overview]
Message-ID: <50999bd57f5dacee8cf2077bec6de3bf275e6d75.camel@kernel.org> (raw)
In-Reply-To: <YivIg2H6BY5KuMQ/@linutronix.de>
On Fri, 2022-03-11 at 23:09 +0100, Sebastian Andrzej Siewior wrote:
> On 2022-03-11 15:46:23 [-0600], Tom Zanussi wrote:
> > index 79e34e98f812..e1dfb01f4623 100644
> > --- a/include/linux/sched.h
> > +++ b/include/linux/sched.h
> > @@ -802,6 +802,18 @@ struct task_struct {
> > /* to be used once the psi infrastructure lands upstream. */
> > unsigned use_memdelay:1;
> > #endif
> > +#ifdef CONFIG_PSI
> > + /* Stalled due to lack of memory */
> > + unsigned in_memstall:1;
> > +#endif
> > +#ifdef CONFIG_PAGE_OWNER
> > + /* Used by page_owner=on to detect recursion in page tracking.
> > */
> > + unsigned in_page_owner:1;
> > +#endif
>
> the upper two don't look like they belong here.
You're right, they don't - I missed those when fixing the conflict in
this file. Will do a new release shortly to fix that.
Thanks for reviewing and pointing it out.
Tom
>
> > +#ifdef CONFIG_EVENTFD
> > + /* Recursion prevention for eventfd_signal() */
> > + unsigned in_eventfd_signal:1;
> > +#endif
> >
> > unsigned long atomic_flags; /* Flags
> > requiring atomic access. */
> >
> > diff --git a/localversion-rt b/localversion-rt
>
> Sebastian
prev parent reply other threads:[~2022-03-12 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 21:46 [ANNOUNCE] 5.4.182-rt71 Tom Zanussi
2022-03-11 22:09 ` Sebastian Andrzej Siewior
2022-03-12 15:56 ` Tom Zanussi [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=50999bd57f5dacee8cf2077bec6de3bf275e6d75.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=williams@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