Re: [PATCH 2/2] aio: initialize kiocb private in case any filesystems expect it.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: hubcap@xxxxxxxxxx
Subject: Re: [PATCH 2/2] aio: initialize kiocb private in case any filesystems expect it.
From: Christoph Hellwig <hch@xxxxxx>
Date: Wed, 6 Feb 2019 07:58:39 +0100
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, Mike Marshall <hubcap@xxxxxxxxxxxx>, viro@xxxxxxxxxxxxxxxxxx, axboe@xxxxxxxxx, hch@xxxxxx, martin@xxxxxxxxxxx
In-reply-to: <20190205191335.22056-3-hubcap@kernel.org>
User-agent: Mutt/1.5.17 (2007-11-01)

On Tue, Feb 05, 2019 at 02:13:35PM -0500, hubcap@xxxxxxxxxx wrote:
> From: Mike Marshall <hubcap@xxxxxxxxxxxx>
> 
> A recent optimization had left private uninitialized.
> 
> Signed-off-by: Mike Marshall <hubcap@xxxxxxxxxxxx>

Looks good,

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [PATCH 0/2] aio: intialize kiocb private
  - From: hubcap
- [PATCH 2/2] aio: initialize kiocb private in case any filesystems expect it.
  - From: hubcap

Prev by Date: Re: [PATCH 1/2] orangefs: remove two un-needed BUG_ONs...
Next by Date: [PATCH] ramfs: support O_TMPFILE
Previous by thread: [PATCH 2/2] aio: initialize kiocb private in case any filesystems expect it.
Next by thread: Re: [PATCH 0/2] aio: intialize kiocb private
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux