remove set_fs from copy_strings_kernel

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

To: Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: remove set_fs from copy_strings_kernel
From: Christoph Hellwig <hch@xxxxxx>
Date: Fri, 1 May 2020 12:41:03 +0200
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx

Hi Al and Andrew,

can one of you pick up this small series to avoid the set_fs
call in copy_strings_kernel?

Follow-Ups:
- [PATCH 1/2] exec: simplify the copy_strings_kernel calling convention
  - From: Christoph Hellwig
- [PATCH 2/2] exec: open code copy_string_kernel
  - From: Christoph Hellwig

Prev by Date: Re: fuse doesn't use security_inode_init_security?
Next by Date: [PATCH 2/2] exec: open code copy_string_kernel
Previous by thread: fuse doesn't use security_inode_init_security?
Next by thread: [PATCH 2/2] exec: open code copy_string_kernel
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]

Powered by Linux