[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20201106210845.e9e95e91b779a01b6751e240@linux-foundation.org>
Date: Fri, 6 Nov 2020 21:08:45 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Vineet Gupta <Vineet.Gupta1@...opsys.com>
Cc: Alexey Dobriyan <adobriyan@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Alexey Gladkov <gladkov.alexey@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Kees Cook <keescook@...omium.org>,
"Eric W . Biederman" <ebiederm@...ssion.com>,
Vlastimil Babka <vbabka@...e.cz>,
Michel Lespinasse <walken@...gle.com>,
Andrei Vagin <avagin@...il.com>,
Bernd Edlinger <bernd.edlinger@...mail.de>,
John Johansen <john.johansen@...onical.com>,
Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-arch@...r.kernel.org,
linux-snps-arc@...ts.infradead.org
Subject: Re: [RFC] proc: get_wchan() stack unwind only makes sense for
sleeping/non-self tasks
On Thu, 5 Nov 2020 15:11:32 -0800 Vineet Gupta <Vineet.Gupta1@...opsys.com> wrote:
> Most architectures currently check this in their get_wchan() implementation
> (ARC doesn't hence this patch). However doing this in core code shows
> the semantics better so move the check one level up (eventually remove
> the boiler-plate code from arches)
It would be nice to clean up the arch callees in the same patch, at
least so it doesn't get forgotten about. Are you prepared to propose
such a change?
Powered by blists - more mailing lists