mirror of
https://github.com/FEX-Emu/linux.git
synced 2024-12-28 04:17:47 +00:00
613655fa39
All these files use the big kernel lock in a trivial
way to serialize their private file operations,
typically resulting from an earlier semi-automatic
pushdown from VFS.
None of these drivers appears to want to lock against
other code, and they all use the BKL as the top-level
lock in their file operations, meaning that there
is no lock-order inversion problem.
Consequently, we can remove the BKL completely,
replacing it with a per-file mutex in every case.
Using a scripted approach means we can avoid
typos.
These drivers do not seem to be under active
maintainance from my brief investigation. Apologies
to those maintainers that I have missed.
file=$1
name=$2
if grep -q lock_kernel ${file} ; then
if grep -q 'include.*linux.mutex.h' ${file} ; then
sed -i '/include.*<linux\/smp_lock.h>/d' ${file}
else
sed -i 's/include.*<linux\/smp_lock.h>.*$/include <linux\/mutex.h>/g' ${file}
fi
sed -i ${file} \
-e "/^#include.*linux.mutex.h/,$ {
1,/^\(static\|int\|long\)/ {
/^\(static\|int\|long\)/istatic DEFINE_MUTEX(${name}_mutex);
} }" \
-e "s/\(un\)*lock_kernel\>[ ]*()/mutex_\1lock(\&${name}_mutex)/g" \
-e '/[ ]*cycle_kernel_lock();/d'
else
sed -i -e '/include.*\<smp_lock.h\>/d' ${file} \
-e '/cycle_kernel_lock()/d'
fi
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
|
||
|---|---|---|
| .. | ||
| aten.c | ||
| bpck6.c | ||
| bpck.c | ||
| comm.c | ||
| dstr.c | ||
| epat.c | ||
| epia.c | ||
| fit2.c | ||
| fit3.c | ||
| friq.c | ||
| frpw.c | ||
| kbic.c | ||
| Kconfig | ||
| ktti.c | ||
| Makefile | ||
| mkd | ||
| on20.c | ||
| on26.c | ||
| paride.c | ||
| paride.h | ||
| pcd.c | ||
| pd.c | ||
| pf.c | ||
| pg.c | ||
| ppc6lnx.c | ||
| pseudo.h | ||
| pt.c | ||
| Transition-notes | ||