Re: [PATCH V5 17/30] fs: use read_iter and write_iter rather than aio_read and aio_write

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dave Kleikamp <dave.kleikamp@xxxxxxxxxx> writes:

> @@ -1315,10 +1317,10 @@ static ssize_t aio_rw_vect_retry(struct kiocb *iocb)
>  
>  	if ((iocb->ki_opcode == IOCB_CMD_PREADV) ||
>  		(iocb->ki_opcode == IOCB_CMD_PREAD)) {
> -		rw_op = file->f_op->aio_read;
> +		rw_op = do_aio_read;
>  		opcode = IOCB_CMD_PREADV;
>  	} else {
> -		rw_op = file->f_op->aio_write;
> +		rw_op = do_aio_read;
>  		opcode = IOCB_CMD_PWRITEV;
>  	}

That wants to be rw_op = do_aio_write in the else clause.  How did you
test this patch set?

Cheers,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux