mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Chao Yu <chao@kernel.org>, linux-erofs@lists.ozlabs.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/4] erofs: support unencoded inodes for fileio
Date: Thu, 5 Sep 2024 17:13:33 +0800	[thread overview]
Message-ID: <55267cdd-c832-45c9-bbe1-9c02473a2269@linux.alibaba.com> (raw)
In-Reply-To: <d095a86b-a1f4-4b31-8092-afa3ef1dfdb5@kernel.org>

Hi Chao,

On 2024/9/5 17:01, Chao Yu wrote:
> On 2024/8/30 11:28, Gao Xiang wrote:

..

>> +
>> +static void erofs_fileio_rq_submit(struct erofs_fileio_rq *rq)
>> +{
>> +    struct iov_iter iter;
>> +    int ret;
>> +
>> +    if (!rq)
>> +        return;
>> +    rq->iocb.ki_pos = rq->bio.bi_iter.bi_sector << 9;
> 
> Trivial cleanup,
> 
> rq->iocb.ki_pos = rq->bio.bi_iter.bi_sector << SECTOR_SHIFT;

Will send a quick fix version.

> 
>> +    rq->iocb.ki_ioprio = get_current_ioprio();
>> +    rq->iocb.ki_complete = erofs_fileio_ki_complete;
>> +    rq->iocb.ki_flags = (rq->iocb.ki_filp->f_mode & FMODE_CAN_ODIRECT) ?
>> +                IOCB_DIRECT : 0;
>> +    iov_iter_bvec(&iter, ITER_DEST, rq->bvecs, rq->bio.bi_vcnt,
>> +              rq->bio.bi_iter.bi_size);
>> +    ret = vfs_iocb_iter_read(rq->iocb.ki_filp, &rq->iocb, &iter);
>> +    if (ret != -EIOCBQUEUED)
>> +        erofs_fileio_ki_complete(&rq->iocb, ret);
> 
> Shouldn't we pass return value to caller?

I don't think it's needed.  Since ki_complete will handle error cases
for both (a)sync I/Os.

Thanks,
Gao Xiang

> 
> Thanks,
> 

  reply	other threads:[~2024-09-05  9:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30  3:28 [PATCH v2 1/4] erofs: add file-backed mount support Gao Xiang
2024-08-30  3:28 ` [PATCH v2 2/4] erofs: support unencoded inodes for fileio Gao Xiang
2024-08-31  0:19   ` Sandeep Dhavale
2024-08-31  2:54     ` Gao Xiang
2024-08-31  4:25   ` Sandeep Dhavale
2024-08-31  7:54     ` Gao Xiang
2024-09-01 20:47       ` Sandeep Dhavale
2024-09-04  6:56   ` Gao Xiang
2024-09-05  9:01   ` Chao Yu
2024-09-05  9:13     ` Gao Xiang [this message]
2024-08-30  3:28 ` [PATCH v2 3/4] erofs: support compressed " Gao Xiang
2024-09-01 20:47   ` Sandeep Dhavale
2024-09-05  9:01   ` Chao Yu
2024-09-05  9:14     ` Gao Xiang
2024-09-05  9:46   ` Chao Yu
2024-08-30  3:28 ` [PATCH v2 4/4] erofs: mark experimental fscache backend deprecated Gao Xiang
2024-09-01 20:48   ` Sandeep Dhavale
2024-09-05  9:03   ` Chao Yu
2024-08-31  0:30 ` [PATCH v2 1/4] erofs: add file-backed mount support Sandeep Dhavale
2024-08-31  3:00   ` Gao Xiang
2024-09-01 20:46 ` Sandeep Dhavale
2024-09-05  8:22 ` Chao Yu
2024-09-05  9:30 ` [PATCH v3 2/4] erofs: support unencoded inodes for fileio Gao Xiang
2024-09-05  9:44   ` Chao Yu
2024-09-24  9:21 ` [PATCH v2 1/4] erofs: add file-backed mount support Geert Uytterhoeven
2024-09-24  9:29   ` Gao Xiang
2024-09-30 14:18   ` Jan Kara
2024-09-30 14:22     ` Geert Uytterhoeven
2024-10-02  6:12     ` Christian Brauner
2024-10-02 11:25       ` Gao Xiang

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=55267cdd-c832-45c9-bbe1-9c02473a2269@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=chao@kernel.org \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®