From: "Shah, Amit" <aams@amazon.de>
To: "Heyne, Maximilian" <mheyne@amazon.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Woodhouse, David" <dwmw@amazon.co.uk>, "hch@lst.de" <hch@lst.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Dannowski, Uwe" <uwed@amazon.de>,
"Mehlan, Torsten" <tomeh@amazon.de>
Subject: Re: [PATCH] fs: fix lost error code in dio_complete
Date: Wed, 31 Oct 2018 09:24:43 +0000 [thread overview]
Message-ID: <1540977883.6429.74.camel@amazon.com> (raw)
In-Reply-To: <20181030215739.4557-1-mheyne@amazon.de>
On Di, 2018-10-30 at 21:57 +0000, Maximilian Heyne wrote:
> commit e259221763a40403d5bb232209998e8c45804ab8 ("fs: simplify the
> generic_write_sync prototype") reworked callers of generic_write_sync(),
> and ended up dropping the error return for the directio path. Prior to
> that commit, in dio_complete(), an error would be bubbled up the stack,
> but after that commit, errors passed on to dio_complete were eaten up.
>
> This was reported on the list earlier, and a fix was proposed in
> https://lore.kernel.org/lkml/20160921141539.GA17898@infradead.org/, but
> never followed up with. We recently hit this bug in our testing where
> fencing io errors, which were previously erroring out with EIO, were
> being returned as success operations after this commit.
>
> The fix proposed on the list earlier was a little short -- it would have
> still called generic_write_sync() in case `ret` already contained an
> error. This fix ensures generic_write_sync() is only called when
> there's no pending error in the write.
>
> CC: stable@vger.kernel.org
> Reported-by: Ravi Nankani <rnankani@amazon.com>
> Signed-off-by: Maximilian Heyne <mheyne@amazon.de>
> Signed-off-by: Torsten Mehlan <tomeh@amazon.de>
> Signed-off-by: Uwe Dannowski <uwed@amazon.de>
> Signed-off-by: Amit Shah <aams@amazon.de>
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> ---
> fs/direct-io.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/direct-io.c b/fs/direct-io.c
> index 093fb54cd316..199146036093 100644
> --- a/fs/direct-io.c
> +++ b/fs/direct-io.c
> @@ -325,8 +325,8 @@ static ssize_t dio_complete(struct dio *dio, ssize_t ret, unsigned int flags)
> */
> dio->iocb->ki_pos += transferred;
>
> - if (dio->op == REQ_OP_WRITE)
> - ret = generic_write_sync(dio->iocb, transferred);
> + if (ret > 0 && dio->op == REQ_OP_WRITE)
> + ret = generic_write_sync(dio->iocb, ret);
Is the s/transferred/ret/ change necessary? Needs explaining, at least.
> dio->iocb->ki_complete(dio->iocb, ret, 0);
> }
>
Thanks,
Amit
Amazon Development Center Germany GmbH
Berlin - Dresden - Aachen
main office: Krausenstr. 38, 10117 Berlin
Geschaeftsfuehrer: Dr. Ralf Herbrich, Christian Schlaeger
Ust-ID: DE289237879
Eingetragen am Amtsgericht Charlottenburg HRB 149173 B
next prev parent reply other threads:[~2018-10-31 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 21:57 [PATCH] fs: fix lost error code in dio_complete Maximilian Heyne
2018-10-31 5:46 ` Christoph Hellwig
2018-10-31 9:24 ` Shah, Amit [this message]
2018-11-01 8:03 ` Maximilian Heyne
2018-11-01 9:06 ` Shah, Amit
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=1540977883.6429.74.camel@amazon.com \
--to=aams@amazon.de \
--cc=dwmw@amazon.co.uk \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mheyne@amazon.de \
--cc=stable@vger.kernel.org \
--cc=tomeh@amazon.de \
--cc=uwed@amazon.de \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.