[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-scsi
Subject:    [Bug 14214] BUG at drivers/scsi/scsi_lib.c:1108!
From:       bugzilla-daemon () bugzilla ! kernel ! org
Date:       2009-09-30 21:19:33
Message-ID: 200909302119.n8ULJXKO003868 () demeter ! kernel ! org
[Download RAW message or body]

http://bugzilla.kernel.org/show_bug.cgi?id=14214





--- Comment #2 from Anonymous Emailer <anonymous@kernel-bugs.osdl.org>  2009-09-30 21:19:32 ---
Reply-To: James.Bottomley@HansenPartnership.com

On Wed, 2009-09-30 at 12:56 -0700, Andrew Morton wrote:
> On Wed, 23 Sep 2009 11:13:26 GMT
> bugzilla-daemon@bugzilla.kernel.org wrote:
> 
> > http://bugzilla.kernel.org/show_bug.cgi?id=14214
> 
> Post-2.6.31 regression.  This, in scsi_setup_fs_cmnd():
> 
>         /*
>          * Filesystem requests must transfer data.
>          */
>         BUG_ON(!req->nr_phys_segments);

Well, the BUG_ON is correct: there can't be a FS type command with no
data.

This can't be a SCSI issue because the problem was caused before SCSI
was entered.  Looking at the backtrace (all functions listed as
unreliable, sigh) this is either a deadline scheduler problem (less
likely) or an md_raid one (more likely).

Let's start with what was the mdraid configuration and condition of the
filesystem being mounted? I've added linux-raid to the cc list so they
can chime in for more details.

James

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]