On Sun, 2006-05-21 at 18:00 -0700, Andrew Morton wrote: > Badari Pulavarty <[email protected]> wrote: > > > > This patch removes readv() and writev() methods and replaces > > them with aio_read()/aio_write() methods. > > And it breaks autofs4 > > autofs: pipe file descriptor does not contain proper ops > Any easy test case to reproduce the problem ? Thanks, Badari - 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/
- Follow-Ups:
- References:
- [PATCH 0/3] VFS changes to collapse AIO and vectored IO into single (set of) fileops.
- From: Badari Pulavarty <[email protected]>
- [PATCH 0/3] VFS changes to collapse AIO and vectored IO into single (set of) fileops.
- From: Badari Pulavarty <[email protected]>
- [PATCH 0/4] VFS fileop cleanups by collapsing AIO and vector IO
- From: Badari Pulavarty <[email protected]>
- [PATCH 0/4] VFS fileop cleanups by collapsing AIO and vector IO
- From: Badari Pulavarty <[email protected]>
- [PATCH 2/4] Remove readv/writev methods and use aio_read/aio_write instead
- From: Badari Pulavarty <[email protected]>
- Re: [PATCH 2/4] Remove readv/writev methods and use aio_read/aio_write instead
- From: Andrew Morton <[email protected]>
- [PATCH 0/3] VFS changes to collapse AIO and vectored IO into single (set of) fileops.
- Prev by Date: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- Next by Date: Re: [PATCH 2/6, 2nd try] reliable stack trace support (x86-64)
- Previous by thread: Re: [PATCH 2/4] Remove readv/writev methods and use aio_read/aio_write instead
- Next by thread: Re: [PATCH 2/4] Remove readv/writev methods and use aio_read/aio_write instead
- Index(es):