[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200929.142200.67101764735438804.davem@davemloft.net>
Date: Tue, 29 Sep 2020 14:22:00 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: tglx@...utronix.de
Cc: linux-kernel@...r.kernel.org, peterz@...radead.org,
paulmck@...nel.org, willy@...radead.org, benve@...co.com,
_govind@....com, kuba@...nel.org, netdev@...r.kernel.org,
corbet@....net, mchehab+huawei@...nel.org,
linux-doc@...r.kernel.org, bigeasy@...utronix.de,
luc.vanoostenryck@...il.com, jcliburn@...il.com,
chris.snook@...il.com, vishal@...lsio.com,
jeffrey.t.kirsher@...el.com, intel-wired-lan@...ts.osuosl.org,
snelson@...sando.io, drivers@...sando.io, andrew@...n.ch,
hkallweit1@...il.com, linux@...linux.org.uk,
tsbogend@...ha.franken.de, linux-net-drivers@...arflare.com,
ecree@...arflare.com, mhabets@...arflare.com, jdmason@...zu.us,
dsd@...too.org, kune@...ne-taler.de, kvalo@...eaurora.org,
linux-wireless@...r.kernel.org, linux-usb@...r.kernel.org,
gregkh@...uxfoundation.org, arend.vanspriel@...adcom.com,
franky.lin@...adcom.com, hante.meuleman@...adcom.com,
chi-hsien.lin@...ress.com, wright.feng@...ress.com,
brcm80211-dev-list.pdl@...adcom.com,
brcm80211-dev-list@...ress.com, stas.yakovlev@...il.com,
stf_xl@...pl, johannes.berg@...el.com, emmanuel.grumbach@...el.com,
luciano.coelho@...el.com, linuxwifi@...el.com, j@...fi,
amitkarwar@...il.com
Subject: Re: [patch V2 00/36] net: in_interrupt() cleanup and fixes
From: Thomas Gleixner <tglx@...utronix.de>
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@linutronix.de/
>
> 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@linutronix.de
...
Series applied to net-next, thanks.
Powered by blists - more mailing lists