linux-ext4 - Re: [PATCH] Rename copy_file_range to _copy_file

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: <20171229035539.GB11757@thunk.org>
Date:   Thu, 28 Dec 2017 22:55:39 -0500
From:   Theodore Ts'o <tytso@....edu>
To:     Palmer Dabbelt <palmer@...belt.com>
Cc:     linux-ext4@...r.kernel.org, patches@...ups.riscv.org
Subject: Re: [PATCH] Rename copy_file_range to _copy_file_range

On Thu, Dec 28, 2017 at 06:18:28PM -0800, Palmer Dabbelt wrote:
> As of 2.27, glibc will have a copy_file_range library call to wrap the
> new copy_file_range system call.  This conflicts with the function in
> misc/create_inode.c, which this patch renames _copy_file_range.

Could you resend the patch renaming it to copy_file_chunk()?  That's
less likely to cause confusion with the copy_file_range system call.

Thanks,

					-	 Ted