From: Dave Chinner <david@fromorbit.com>
To: David Howells <dhowells@redhat.com>
Cc: mbobrowski@mbobrowski.org, jack@suse.cz,
linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Is ext4_dio_read_iter() broken?
Date: Fri, 13 Mar 2020 10:23:37 +1100 [thread overview]
Message-ID: <20200312232337.GZ10737@dread.disaster.area> (raw)
In-Reply-To: <969260.1584004779@warthog.procyon.org.uk>
On Thu, Mar 12, 2020 at 09:19:39AM +0000, David Howells wrote:
> Hi Matthew,
>
> Is ext4_dio_read_iter() broken? It calls:
>
> file_accessed(iocb->ki_filp);
>
> at the end of the function - but surely iocb should be expected to have been
> freed when iocb->ki_complete() was called?
>
> In my cachefiles rewrite, I'm seeing the attached kasan dump. The offending
> RIP, ext4_file_read_iter+0x12b is at the above line, where it is trying to
> read iocb->ki_filp.
>
> Here's an excerpt of the relevant bits from my code:
>
> static void cachefiles_read_complete(struct kiocb *iocb, long ret, long ret2)
> {
> struct cachefiles_kiocb *ki =
> container_of(iocb, struct cachefiles_kiocb, iocb);
> struct fscache_io_request *req = ki->req;
> ...
> fput(ki->iocb.ki_filp);
> kfree(ki);
> fscache_end_io_operation(req->cookie);
> ...
> }
>
> int cachefiles_read(struct fscache_object *obj,
> struct fscache_io_request *req,
> struct iov_iter *iter)
> {
> struct cachefiles_object *object =
> container_of(obj, struct cachefiles_object, fscache);
> struct cachefiles_kiocb *ki;
> struct file *file = object->backing_file;
> ssize_t ret = -ENOBUFS;
> ...
> ki = kzalloc(sizeof(struct cachefiles_kiocb), GFP_KERNEL);
> if (!ki)
> goto presubmission_error;
>
> ki->iocb.ki_filp = get_file(file);
> ki->iocb.ki_pos = req->pos;
> ki->iocb.ki_flags = IOCB_DIRECT;
> ki->iocb.ki_hint = ki_hint_validate(file_write_hint(file));
> ki->iocb.ki_ioprio = get_current_ioprio();
> ki->req = req;
>
> if (req->io_done)
> ki->iocb.ki_complete = cachefiles_read_complete;
>
> ret = rw_verify_area(READ, file, &ki->iocb.ki_pos, iov_iter_count(iter));
> if (ret < 0)
> goto presubmission_error_free;
>
> fscache_get_io_request(req);
> trace_cachefiles_read(object, file_inode(file), req);
> ret = call_read_iter(file, &ki->iocb, iter);
> ...
> }
>
> The allocation point, cachefiles_read+0xd0, is the kzalloc() you can see and
> the free point, cachefiles_read_complete+0x86, is the kfree() in the callback
> function.
It looks to me like you are creating your own iocb that you are
doing AIO+DIO on, and you aren't taking a reference count to the
iocb yourself to ensure that it exists for the entire submission
path. i.e. see how the AIO code uses ki_refcnt and iocb_put() to
ensure the iocb does not get destroyed by IO completion before the
submission path has completed.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2020-03-12 23:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 9:19 Is ext4_dio_read_iter() broken? David Howells
2020-03-12 10:07 ` Is ext4_dio_read_iter() broken? - and xfs_file_dio_aio_read() David Howells
2020-03-12 10:42 ` Christoph Hellwig
2020-03-12 10:49 ` David Howells
2020-03-12 10:53 ` Christoph Hellwig
2020-03-12 10:20 ` Is ext4_dio_read_iter() broken? Matthew Bobrowski
2020-03-12 10:26 ` btrfs may be broken too - " David Howells
2020-03-12 23:23 ` Dave Chinner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200312232337.GZ10737@dread.disaster.area \
--to=david@fromorbit.com \
--cc=dhowells@redhat.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mbobrowski@mbobrowski.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).