[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <x497gnai3nn.fsf@segfault.boston.devel.redhat.com>
Date: Fri, 18 Jan 2013 16:26:20 -0500
From: Jeff Moyer <jmoyer@...hat.com>
To: Dave Kleikamp <dave.kleikamp@...cle.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
Zach Brown <zab@...bo.net>,
"Maxim V. Patlasov" <mpatlasov@...allels.com>,
Alexander Viro <viro@...iv.linux.org.uk>
Subject: Re: [PATCH V5 17/30] fs: use read_iter and write_iter rather than aio_read and aio_write
Dave Kleikamp <dave.kleikamp@...cle.com> 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists