diff options
| author | NeilBrown <neilb@suse.com> | 2018-02-20 13:23:37 +1100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-02-22 15:06:36 +0100 |
| commit | c90e17185722edb75ada5775f560279ab1d32b70 (patch) | |
| tree | fc42eafee068a8cac070d14bac6a01b45d3aee45 /drivers/staging/lustre/include | |
| parent | 033085ff96a1615b08e80fd4327f2608ff7408cb (diff) | |
| download | op-kernel-dev-c90e17185722edb75ada5775f560279ab1d32b70.zip op-kernel-dev-c90e17185722edb75ada5775f560279ab1d32b70.tar.gz | |
staging: lustre: discard libcfs_kvzalloc and linux-mem.c
The only interesting difference between libcfs_kvzalloc()
and kvzalloc() is that the former appears to work
with GFP_NOFS, which the latter gives a WARN_ON_ONCE()
when that is attempted.
Each libcfs_kvzalloc() should really be analysed
and either converted to a kzalloc() call if the size is never
more than a page, or to use GFP_KERNEL if no locks are held.
If there is ever a case where locks are held and a large allocation
is needed, then some other technique should be used.
It might be nice to not always blindly zero pages too...
For now, just convert libcfs_kvzalloc() calls to
kvzalloc(), and let the warning remind us that there is work to do.
Signed-off-by: NeilBrown <neilb@suse.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/lustre/include')
| -rw-r--r-- | drivers/staging/lustre/include/linux/libcfs/libcfs.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/staging/lustre/include/linux/libcfs/libcfs.h b/drivers/staging/lustre/include/linux/libcfs/libcfs.h index 0392057..3927935 100644 --- a/drivers/staging/lustre/include/linux/libcfs/libcfs.h +++ b/drivers/staging/lustre/include/linux/libcfs/libcfs.h @@ -112,8 +112,6 @@ static inline void *__container_of(void *ptr, unsigned long shift) #define _LIBCFS_H -void *libcfs_kvzalloc(size_t size, gfp_t flags); - extern struct miscdevice libcfs_dev; /** * The path of debug log dump upcall script. |
