On Thu, 21 Jun 2001, Andrea Arcangeli wrote: > > I think the patch is ok. We must have a way to track down which bh are > actually getting read, We _do_ have a way. The way is called "bh->b_end_io == end_io_async". What's the problem with the existing code, and why do people want to add a (unnecessary) new bit? Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- correction: fs/buffer.c underlocking async pages Stefan . Bader
- Re: correction: fs/buffer.c underlocking async pages Andrea Arcangeli
- Re: correction: fs/buffer.c underlocking async p... Chris Mason
- Re: correction: fs/buffer.c underlocking asy... Andrea Arcangeli
- Re: correction: fs/buffer.c underlocking async p... Linus Torvalds
- Re: correction: fs/buffer.c underlocking asy... Andrea Arcangeli
- Re: correction: fs/buffer.c underlocking async pages Andrea Arcangeli
- Re: correction: fs/buffer.c underlocking async p... Linus Torvalds
- Re: correction: fs/buffer.c underlocking asy... Andrea Arcangeli
- Re: correction: fs/buffer.c underlocking... Andrea Arcangeli
- Re: correction: fs/buffer.c underlocking... Chris Mason
- Re: correction: fs/buffer.c underlocking... Linus Torvalds
- Re: correction: fs/buffer.c underlocking async pages Stefan . Bader