linux-kernel - Re: [osd-dev] [PATCH 17/56] fs/exofs: support compiling out splice

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] [day] [month] [year] [list]

Message-ID: <5468681C.5000307@electrozaur.com>
Date:	Sun, 16 Nov 2014 11:02:20 +0200
From:	Boaz Harrosh <ooo@...ctrozaur.com>
To:	Pieter Smith <pieter@...sman.nl>
CC:	Benny Halevy <bhalevy@...marydata.com>,
	"open list:OSD LIBRARY and F..." <osd-dev@...n-osd.org>,
	Josh Triplett <josh@...htriplett.org>,
	open list <linux-kernel@...r.kernel.org>
Subject: Re: [osd-dev] [PATCH 17/56] fs/exofs: support compiling out splice

On 11/13/2014 11:22 PM, Pieter Smith wrote:
> Compile out splice support from exofs when the splice-family of syscalls is not
> supported by the system (i.e. CONFIG_SYSCALL_SPLICE is undefined).
> 
> Signed-off-by: Pieter Smith <pieter@...sman.nl>

ACK-by: Boaz Harrosh <ooo@...ctrozaur.com>

Or do you need that I push it through my tree ?
> ---
>  fs/exofs/file.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/exofs/file.c b/fs/exofs/file.c
> index 71bf8e4..23dfb05 100644
> --- a/fs/exofs/file.c
> +++ b/fs/exofs/file.c
> @@ -76,8 +76,8 @@ const struct file_operations exofs_file_operations = {
>  	.release	= exofs_release_file,
>  	.fsync		= exofs_file_fsync,
>  	.flush		= exofs_flush,
> -	.splice_read	= generic_file_splice_read,
> -	.splice_write	= iter_file_splice_write,
> +	SPLICE_READ_INIT(generic_file_splice_read)
> +	SPLICE_WRITE_INIT(iter_file_splice_write)
>  };
>  
>  const struct inode_operations exofs_file_inode_operations = {
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/