[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <200609282228.02611.annabellesgarden@yahoo.de>
Date: Thu, 28 Sep 2006 22:28:02 +0200
From: Karsten Wiese <annabellesgarden@...oo.de>
To: linux-kernel@...r.kernel.org, Takashi Iwai <tiwai@...e.de>
Cc: mingo@...e.hu, alsa-devel@...ts.sourceforge.net
Subject: [PATCH] Reset file->f_op in snd_card_file_remove(). Take 2
Hi
It oopses with 2.6.18-rt4 + alsa-kernel-1.0.13rc3 now.
I wrote before, 2.6.18-rt3 + alsa-driver-1.0.13rc3 would be ok,
but its not. bug showed again reliably under memory-pressure.
Karsten
===
Reset file->f_op in snd_card_file_remove(). Take 2
i think what happens here is:
us428control runs, kernel has allocated a struct file for /dev/hwC1D0.
usb disconnect
snd_usb_usx2y calls snd_card_disconnect,
tells us428control to exit.
snd_card_disconnect replaces /dev/hwC1D0's file->f_op
with a kmalloc()ed version, that would only allow releases.
us428control starts exiting
__fput is called with struct file for /dev/hwC1D0.
snd_card_file_remove() is called, alsa notices struct file
for /dev/hwC1D0 is about to be closed.
with patch below, file->f_op would be set NULL now.
snd_usb_usx2y's free()s snd_card instance and /dev/hwC1D0's
file->f_ops, those that would only allow releases.
for reason I would like to know,
__fput is called again with struct file for /dev/hwC1D0
from us428control's do_exit().
__fput see's file->f_op is still set.
Without patch and under memory pressure, file->f_op can
point to anything now.
Signed-off-by: Karsten Wiese <annabellesgarden@...oo.de>
diff -pur ../alsa/1.0.13/alsa-driver-1.0.13rc3/alsa-kernel/core/init.c rt4-kw/sound/core/init.c
--- ../alsa/1.0.13/alsa-driver-1.0.13rc3/alsa-kernel/core/init.c 2006-09-25 15:33:19.000000000 +0200
+++ rt4-kw/sound/core/init.c 2006-09-28 18:48:15.000000000 +0200
@@ -707,6 +707,8 @@ int snd_card_file_remove(struct snd_card
mfile = card->files;
while (mfile) {
if (mfile->file == file) {
+ fops_put(file->f_op);
+ file->f_op = NULL;
if (pfile)
pfile->next = mfile->next;
else
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists