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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58920289-6947-c079-6d96-779408436aeb@fb.com>
Date:   Tue, 13 Dec 2016 21:08:18 -0700
From:   Jens Axboe <axboe@...com>
To:     Shaohua Li <shli@...com>, <linux-block@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
CC:     <kernel-team@...com>, Christoph Hellwig <hch@....de>
Subject: Re: [PATCH] block_dev: don't update file access position for sync
 direct IO

On 12/13/2016 08:07 PM, Shaohua Li wrote:
> For sync direct IO, generic_file_direct_write/generic_file_read_iter
> will update file access position. Don't duplicate the update in
> .direct_IO. This cause my raid array can't assemble.

That's not great... Thanks, added.

-- 
Jens Axboe

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ