Hi Al,
Here are some changes I've made, based on your comments plus a little more:
(*) Get rid of the old vfs_new_sb_config() and rename
__vfs_new_sb_config() to that. The callers then have to provide a
file_system_type pointer and all the args.
(*) Add a "struct net *s_net_ns" to
Hi Al,
Here are some changes I've made, based on your comments plus a little more:
(*) Get rid of the old vfs_new_sb_config() and rename
__vfs_new_sb_config() to that. The callers then have to provide a
file_system_type pointer and all the args.
(*) Add a "struct net *s_net_ns" to
On Tue, May 30, 2017 at 5:36 PM, David Howells wrote:
> Al Viro wrote:
>
>> Random notes:
>> * "sb_config" looks rather odd in the current variant; mount_context,
>> perhaps? Or fs_context, for that matter... Anyway, that's trivial.
>
> You
On Tue, May 30, 2017 at 5:36 PM, David Howells wrote:
> Al Viro wrote:
>
>> Random notes:
>> * "sb_config" looks rather odd in the current variant; mount_context,
>> perhaps? Or fs_context, for that matter... Anyway, that's trivial.
>
> You can argue that one with Miklós. He argued
On Mon, May 22, 2017 at 04:50:56PM +0100, David Howells wrote:
>
> Here are a set of patches to create a superblock configuration context
> prior to setting up a new mount, populating it with the parsed
> options/binary data, creating the superblock and then effecting the mount.
>
> This allows
On Mon, May 22, 2017 at 04:50:56PM +0100, David Howells wrote:
>
> Here are a set of patches to create a superblock configuration context
> prior to setting up a new mount, populating it with the parsed
> options/binary data, creating the superblock and then effecting the mount.
>
> This allows
Al Viro wrote:
> Random notes:
> * "sb_config" looks rather odd in the current variant; mount_context,
> perhaps? Or fs_context, for that matter... Anyway, that's trivial.
You can argue that one with Miklós. He argued against mount_context as I had
it
Al Viro wrote:
> Random notes:
> * "sb_config" looks rather odd in the current variant; mount_context,
> perhaps? Or fs_context, for that matter... Anyway, that's trivial.
You can argue that one with Miklós. He argued against mount_context as I had
it originally. His point is that the
Here are a set of patches to create a superblock configuration context
prior to setting up a new mount, populating it with the parsed
options/binary data, creating the superblock and then effecting the mount.
This allows namespaces and other information to be conveyed through the
mount
Here are a set of patches to create a superblock configuration context
prior to setting up a new mount, populating it with the parsed
options/binary data, creating the superblock and then effecting the mount.
This allows namespaces and other information to be conveyed through the
mount
10 matches
Mail list logo