mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Fabio Coatti <cova@ferrara.linux.it>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net, zaitcev@redhat.com
Subject: Re: 2.6.10-rc2-mm2 usb storage still oopses
Date: Thu, 18 Nov 2004 13:58:09 -0800	[thread overview]
Message-ID: <20041118135809.3314ce41@lembas.zaitcev.lan> (raw)
In-Reply-To: <20041118133557.72f3b369.akpm@osdl.org>

On Thu, 18 Nov 2004 13:35:57 -0800, Andrew Morton <akpm@osdl.org> wrote:

> Fabio Coatti <cova@ferrara.linux.it> wrote:
> >
> > Just a reminder: it's possible to cause a kernel oops simply inserting and 
> > removing a usb storage (flash pen); using ub driver doesn't improve the 
> > situation; noticed in 2.6.9-rc4-mm1 and present in 2.6.10-rc2-mm2.
> > The same device works just fine with 2.6.8.1 (mdk cooker)
> 
> OK, that's something we'd like to get fixed prior to 2.6.10.

Actually Fabio told me that his oops was fixed by the patch present in
2.6.10-rc2. The problem is that his device needs special handling which
I do not know how to provide, so it does not work in the end. I hope it
will resolve itself eventually, as I get testers.

There was one last oops from Martin Schleminger ("Sahara") which I think
I fixed but I need a confirmation before pushing to Greg. Apparently, it
only happens on kernels with preempt enabled. If anyone knows of any other
problems, I'm all ears.

-- Pete

P.S. Current updates:

--- linux-2.6.10-rc2-usb/drivers/block/ub.c	2004-11-16 17:03:02.000000000 -0800
+++ linux-2.6.10-rc1-ub/drivers/block/ub.c	2004-11-07 19:01:03.000000000 -0800
@@ -36,7 +36,7 @@
 #define DRV_NAME "ub"
 #define DEVFS_NAME DRV_NAME
 
-#define UB_MAJOR 125	/* Stolen from Experimental range for a week - XXX */
+#define UB_MAJOR 180
 
 /*
  * Definitions which have to be scattered once we understand the layout better.
@@ -1535,8 +1535,11 @@
 
 	ub_revalidate(sc);
 	/* This is pretty much a long term P3 */
-	printk(KERN_INFO "%s: device %u capacity nsec %ld bsize %u\n",
-	    sc->name, sc->dev->devnum, sc->capacity.nsec, sc->capacity.bsize);
+	if (!atomic_read(&sc->poison)) {		/* Cover sc->dev */
+		printk(KERN_INFO "%s: device %u capacity nsec %ld bsize %u\n",
+		    sc->name, sc->dev->devnum,
+		    sc->capacity.nsec, sc->capacity.bsize);
+	}
 
 	/* XXX Support sector size switching like in sr.c */
 	blk_queue_hardsect_size(disk->queue, sc->capacity.bsize);

  reply	other threads:[~2004-11-18 22:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 21:03 Fabio Coatti
2004-11-18 21:35 ` Andrew Morton
2004-11-18 21:58   ` Pete Zaitcev [this message]
2004-11-18 23:42     ` Fabio Coatti
2004-11-18 23:55       ` Pete Zaitcev
2004-11-30  0:32         ` Andrew Morton
2004-11-30  3:22           ` James Bottomley
2004-11-30  9:13             ` Fabio Coatti
2004-11-30 19:27             ` Fabio Coatti
2004-11-30 20:58               ` [linux-usb-devel] " Alan Stern
2004-12-01  1:06                 ` Fabio Coatti
2004-11-19  2:41       ` Maneesh Soni
2004-11-19 16:47         ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041118135809.3314ce41@lembas.zaitcev.lan \
    --to=zaitcev@redhat.com \
    --cc=akpm@osdl.org \
    --cc=cova@ferrara.linux.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®