Re: [PATCH] iomap: stop using ioend after it's been freed in iomap_finish_ioend()

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

Subject: Re: [PATCH] iomap: stop using ioend after it's been freed in iomap_finish_ioend()
From: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>
Date: Thu, 5 Dec 2019 07:39:44 -0800
Cc: Zorro Lang <zlang@xxxxxxxxxx>, linux-xfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <20191205075235.GA21619@infradead.org>
References: <20191205065132.21604-1-zlang@redhat.com> <20191205075235.GA21619@infradead.org>
User-agent: Mutt/1.9.4 (2018-02-28)

On Wed, Dec 04, 2019 at 11:52:35PM -0800, Christoph Hellwig wrote:
> The code changes looks good, although we usually don't do that
> style of comment.  Otherwise looksgood:

I specifically requested it to avoid future maintainer fail. :)

> Reviewed-by: Christoph Hellwig <hch@xxxxxx>

Thanks for the reviews!

--D

References:
- [PATCH] iomap: stop using ioend after it's been freed in iomap_finish_ioend()
  - From: Zorro Lang
- Re: [PATCH] iomap: stop using ioend after it's been freed in iomap_finish_ioend()
  - From: Christoph Hellwig

Prev by Date: Re: [PATCH 6/6] xfs_repair: check plausibility of root dir pointer before trashing it
Next by Date: Re: [PATCH 3/6] xfs_repair: enforce that inode btree chunks can't point to AG headers
Previous by thread: Re: [PATCH] iomap: stop using ioend after it's been freed in iomap_finish_ioend()
Next by thread: KASAN: slab-out-of-bounds Read in iov_iter_alignment
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux