From: hubcap@kernel.org
To: linux-fsdevel@vger.kernel.org
Cc: Mike Marshall <hubcap@omnibond.com>,
viro@zeniv.linux.org.uk, axboe@kernel.dk, hch@lst.de,
martin@omnibond.co
Subject: [PATCH 2/2] aio: initialize kiocb private in case any filesystems expect it.
Date: Tue, 5 Feb 2019 14:13:35 -0500 [thread overview]
Message-ID: <20190205191335.22056-3-hubcap@kernel.org> (raw)
In-Reply-To: <20190205191335.22056-1-hubcap@kernel.org>
From: Mike Marshall <hubcap@omnibond.com>
A recent optimization had left private uninitialized.
Signed-off-by: Mike Marshall <hubcap@omnibond.com>
---
fs/aio.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/aio.c b/fs/aio.c
index b906ff70c90f..aaaaf4d12c73 100644
--- a/fs/aio.c
+++ b/fs/aio.c
@@ -1436,6 +1436,7 @@ static int aio_prep_rw(struct kiocb *req, const struct iocb *iocb)
if (unlikely(!req->ki_filp))
return -EBADF;
req->ki_complete = aio_complete_rw;
+ req->private = NULL;
req->ki_pos = iocb->aio_offset;
req->ki_flags = iocb_flags(req->ki_filp);
if (iocb->aio_flags & IOCB_FLAG_RESFD)
--
2.20.1
next prev parent reply other threads:[~2019-02-05 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 19:13 [PATCH 0/2] aio: intialize kiocb private hubcap
2019-02-05 19:13 ` [PATCH 1/2] orangefs: remove two un-needed BUG_ONs hubcap
2019-02-06 6:58 ` Christoph Hellwig
2019-02-06 13:22 ` Mike Marshall
2019-02-05 19:13 ` hubcap [this message]
2019-02-06 6:58 ` [PATCH 2/2] aio: initialize kiocb private in case any filesystems expect it Christoph Hellwig
2019-02-06 15:05 ` [PATCH 0/2] aio: intialize kiocb private Jens Axboe
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=20190205191335.22056-3-hubcap@kernel.org \
--to=hubcap@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin@omnibond.co \
--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 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).