linux-kernel - Re: [PATCH v1] kernel.h: Move oops_in

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200914150018.GG3956970@smile.fi.intel.com>
Date:   Mon, 14 Sep 2020 18:00:18 +0300
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Petr Mladek <pmladek@...e.com>
Cc:     Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
        John Ogness <john.ogness@...utronix.de>
Subject: Re: [PATCH v1] kernel.h: Move oops_in_progress to printk.h

On Mon, Sep 14, 2020 at 10:43:32AM +0200, Petr Mladek wrote:
> On Fri 2020-09-11 20:02:02, Andy Shevchenko wrote:
> > The oops_in_progress is defined in printk.c, so it's logical
> > to move oops_in_progress to printk.h.
> > 
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
> 
> Yeah, it makes sense.
> 
> Acked-by: Petr Mladek <pmladek@...e.com>
> 
> I am always a bit afraid of messing with these heavily used includes.
> Let's see if boots complain about some build failure.

Agree.

Just to clarify: I assumed, might be wrongly, that this will go via PRINTK
tree. If you have something else in mind, please tell, I will route it to
the corresponding maintainer(s).

-- 
With Best Regards,
Andy Shevchenko