Re: [patch V2 00/36] net: in_interrupt() cleanup and fixes
From: David Miller
Date: Tue Sep 29 2020 - 17:22:08 EST
From: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Date: Tue, 29 Sep 2020 22:25:09 +0200
> in the discussion about preempt count consistency accross kernel configurations:
>
> https://lore.kernel.org/r/20200914204209.256266093@xxxxxxxxxxxxx/
>
> Linus clearly requested that code in drivers and libraries which changes
> behaviour based on execution context should either be split up so that
> e.g. task context invocations and BH invocations have different interfaces
> or if that's not possible the context information has to be provided by the
> caller which knows in which context it is executing.
>
> This includes conditional locking, allocation mode (GFP_*) decisions and
> avoidance of code paths which might sleep.
>
> In the long run, usage of 'preemptible, in_*irq etc.' should be banned from
> driver code completely.
>
> This is the second version of the first batch of related changes. V1 can be
> found here:
>
> https://lore.kernel.org/r/20200927194846.045411263@xxxxxxxxxxxxx
...
Series applied to net-next, thanks.