On Tue, 23 Jan 2007, Neil Brown wrote:
> On Monday January 22, cebbert@xxxxxxxxxx wrote:
> > Justin Piszcz wrote:
> > > My .config is attached, please let me know if any other information is
> > > needed and please CC (lkml) as I am not on the list, thanks!
> > >
> > > Running Kernel 184.108.40.206 on a MD RAID5 volume. Copying files over Samba
> > > to
> > > the RAID5 running XFS.
> > >
> > > Any idea what happened here?
> > >
> > Without digging too deeply, I'd say you've hit the same bug Sami Farin
> > and others
> > have reported starting with 2.6.19: pages mapped with kmap_atomic()
> > become unmapped
> > during memcpy() or similar operations. Try disabling preempt -- that
> > seems to be the
> > common factor.
> That is exactly the conclusion I had just come to (a kmap_atomic page
> must be being unmapped during memcpy). I wasn't aware that others had
> reported it - thanks for that.
> Turning off CONFIG_PREEMPT certainly seems like a good idea.
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Is this a bug that can or will be fixed or should I disable pre-emption on
critical and/or server machines?