Re: [PATCH] ovl: inode reference leak in ovl_is_inuse true case.

Hi youngjun! Thank you for your patch. You asked for guidance about posting patch revisions so let me repeat my comment in a more clear way (see below). On Tue, Jun 16, 2020 at 7:46 AM youngjun wrote: > When posting a revision of a patch already posted, the practice is to use the subject

[PATCH] ovl: inode reference leak in ovl_is_inuse true case.

When "ovl_is_inuse" true case, trap inode reference not put. plus adding the comment explaining sequence of ovl_is_inuse after ovl_setup_trap. Signed-off-by: youngjun --- fs/overlayfs/super.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/fs/overlayfs/super.c

Re: [PATCH] ovl: inode reference leak in "ovl_is_inuse" true case.

On Mon, Jun 15, 2020 at 6:57 PM youngjun wrote: > > When "ovl_is_inuse" true case, trap inode reference not put. > > Signed-off-by: youngjun Fixes: 0be0bfd2de9d ("ovl: fix regression caused by overlapping layers detection") Cc: # v4.19+ Reviewed-by: Amir Goldstein > --- >

[PATCH] ovl: inode reference leak in "ovl_is_inuse" true case.

When "ovl_is_inuse" true case, trap inode reference not put. Signed-off-by: youngjun --- fs/overlayfs/super.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c index 91476bc422f9..8837fc1ec3be 100644 --- a/fs/overlayfs/super.c +++