Re: [RFC PATCH v4 1/4] fs: add flags argument to i_op->link()

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Omar Sandoval <osandov@xxxxxxxxxxx>
Subject: Re: [RFC PATCH v4 1/4] fs: add flags argument to i_op->link()
From: David Howells <dhowells@xxxxxxxxxx>
Date: Fri, 31 Jan 2020 13:48:42 +0000
Cc: dhowells@xxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, Al Viro <viro@xxxxxxxxxxxxxxxxxx>, kernel-team@xxxxxx, linux-api@xxxxxxxxxxxxxxx, Amir Goldstein <amir73il@xxxxxxxxx>, Xi Wang <xi@xxxxxxxxxxxxxxxxx>
In-reply-to: <5b94d23baef8c2a256384f436650f4c4868915a2.1580251857.git.osandov@fb.com>
Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903

Omar Sandoval <osandov@xxxxxxxxxxx> wrote:

> -	int (*link) (struct dentry *,struct inode *,struct dentry *);
> +	int (*link) (struct dentry *,struct inode *,struct dentry *, int);

Can you make it unsigned int?

David

Follow-Ups:
- Re: [RFC PATCH v4 1/4] fs: add flags argument to i_op->link()
  - From: Omar Sandoval

References:
- [RFC PATCH v4 1/4] fs: add flags argument to i_op->link()
  - From: Omar Sandoval
- [RFC PATCH v4 0/4] fs: add flag to linkat() for replacing destination
  - From: Omar Sandoval

Prev by Date: [linux-next:master 4531/12088] fs/fs_parser.c:191:5: sparse: sparse: symbol 'fs_param_bad_value' was not declared. Should it be static?
Next by Date: Re: [PATCH ghak90 V8 13/16] audit: track container nesting
Previous by thread: [PATCH 0/4] ovl: allow virtiofs as upper
Next by thread: [RFC PATCH linux-next] fs_param_bad_value() can be static
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [Samba] [Device Mapper] [CEPH Development]