On Wednesday, 30 July 2003 at 21:11:15 +0200, Sander van Malssen wrote:
> On Wednesday, 30 July 2003 at 12:00:02 -0700, Andrew Morton wrote:
>
> > OK, looks like the new readahead stuff confused the error reporting.
> >
> > Does this make the error messages go away?
> >
> >
> > diff -puN mm/readahead.c~a mm/readahead.c
> > --- 25/mm/readahead.c~a 2003-07-30 11:58:07.000000000 -0700
> > +++ 25-akpm/mm/readahead.c 2003-07-30 11:58:20.000000000 -0700
> > @@ -96,7 +96,7 @@ static int read_pages(struct address_spa
> > struct pagevec lru_pvec;
> > int ret = 0;
> >
> > - current->flags |= PF_READAHEAD;
> > +// current->flags |= PF_READAHEAD;
> >
> > if (mapping->a_ops->readpages) {
> > ret = mapping->a_ops->readpages(filp, mapping, pages, nr_pages);
>
> That seems to have fixed it!
Well, that's funny. If I run a pristine test2-mm3-1 kernel I don't get
those "Buffer I/O error on device ..." kernel messages anymore, but I do
get the actual I/O error itself.
Putting that dump_stack() call back into buffer_io_error() doesn't
trigger a stack dump either. Different bug perhaps?
Cheers,
Sander
--
Sander van Malssen -- svm@kozmix.org -- http://www.kozmix.org/
http://www.peteandtommysdayout.com/ -- http://www.1-2-5.net/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 07 2003 - 22:00:20 EST