[lkml]   [2002]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
SubjectRe: 2.5.33-bk testing
In article <Pine.LNX.4.44.0208312209240.1129-100000@dad.molina>,
Thomas Molina <> wrote:
>I've beat on the floppy driver and it seems to work well. I haven't been
>able to make it hiccup yet.

Really? I was looking at my cleanups, and I'm fairly certain they are
buggy. I just pushed an update to the BK tree a few minutes ago that I
think should fix it, but since I'm not a floppy user myself I can only
go by the source and trying to imagine everything that could go wrong.

Anyway, can you please pull the floppy patch from BK or apply this patch
on top of clean 2.5.33 to see if it makes any difference?

[ Now, in all honesty this should _only_ make a difference in case the
floppy request queue empties and another proces comes in and adds a
new request while the previous one is pending, so the timing for the
bug triggering is probably fairly interesting. Which may explain why
you find the floppy driver solid even without this.

Alternatively, I'm just full of crap, and this "fix" is bogus. In
either case I'd like to know about it ;]

Thanks for testing,


# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 02/08/31 1.576
# De-queue the floppy request late, so that the higher levels
# know the floppy driver is busy.
# --------------------------------------------
diff -Nru a/drivers/block/floppy.c b/drivers/block/floppy.c
--- a/drivers/block/floppy.c Sat Aug 31 22:25:41 2002
+++ b/drivers/block/floppy.c Sat Aug 31 22:25:41 2002
@@ -2299,12 +2299,11 @@
+ blkdev_dequeue_request(req);

/* Get the next request */
req = elv_next_request(QUEUE);
- if (req)
- blkdev_dequeue_request(req);
CURRENT = req;

@@ -2939,7 +2938,6 @@
- blkdev_dequeue_request(req);
CURRENT = req;
if (major(CURRENT->rq_dev) != MAJOR_NR)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.049 / U:0.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site