linux-kernel - Re: [PATCH] fuse: Allow parallel DIO reads and check NOWAIT case for DIO writes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 2 Feb 2020 22:25:43 +0100
From:   Bernd Schubert <bernd.schubert@...tmail.fm>
To:     qiwuchen55@...il.com, miklos@...redi.hu
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        chenqiwu <chenqiwu@...omi.com>
Subject: Re: [PATCH] fuse: Allow parallel DIO reads and check NOWAIT case for
 DIO writes



> @@ -1518,6 +1525,9 @@ static ssize_t fuse_direct_read_iter(struct kiocb *iocb, struct iov_iter *to)
>  
>  		res = __fuse_direct_read(&io, to, &iocb->ki_pos);
>  	}
> +	inode_unlock_shared(inode);
> +
> +	file_accessed(iocb->ki_filp);


Shouldn't the file_accessed() in different patch, with a description? It
looks totally unrelated to locking?


Thanks,
Bernd