public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 365] New: Raid-0 causes kernel BUG at drivers/block/ll_rw_blk.c:1996
Date: Sun, 16 Feb 2003 10:54:16 +0100	[thread overview]
Message-ID: <20030216095416.GT26738@suse.de> (raw)
In-Reply-To: <5630000.1045364322@[10.10.2.4]>

On Sat, Feb 15 2003, Martin J. Bligh wrote:
> 
> http://bugme.osdl.org/show_bug.cgi?id=365
> 
>            Summary: Raid-0 causes kernel BUG at
>                     drivers/block/ll_rw_blk.c:1996
>     Kernel Version: 2.5.61
>             Status: NEW
>           Severity: blocking
>              Owner: bugme-janitors@lists.osdl.org
>          Submitter: harisri@bigpond.com
> 
> 
> Distribution: RH 8.0
> Hardware Environment: Athlon, AMD 761 (AMD North Bridge, VIA South bridge),
> IDE Hard drives
> Software Environment: Gnu C 3.2, Linux C Library 2.2.93,
> raidtools-1.00.2-3.3 Problem Description: 2.5.61 oops while trying to
> activate raid-0 volumes. Please refer the thread
> http://marc.theaimsgroup.com/?l=linux-kernel&m=103830814911111&w=2 for more
> information from Neil Brown, Jens Axboe and Andrew Morton.
> 
> Steps to reproduce: Try to enable raid-0 volumes under 2.5.49 to 2.5.61

Known bug, raid0 doesn't accept a full PAGE_CACHE_SIZE page at any
offset, and the api relies on that. Fix is probably to add the sub-page
split stuff.

-- 
Jens Axboe


      reply	other threads:[~2003-02-16  9:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-16  2:58 [Bug 365] New: Raid-0 causes kernel BUG at drivers/block/ll_rw_blk.c:1996 Martin J. Bligh
2003-02-16  9:54 ` Jens Axboe [this message]

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=20030216095416.GT26738@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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