On Thu, Aug 23, 2012 at 10:54:44AM +0200, Marco Stornelli wrote:
> >>For brtfs
> >>
> >>objectid = fid->objectid;
> >>root_objectid = fid->root_objectid;
> >>generation = fid->gen;
> >>
> >>return btrfs_get_dentry(sb, objectid, root_objectid, generation, 1);
> >
> >For btrfs it
Il 23/08/2012 10:06, Cyrill Gorcunov ha scritto:
On Wed, Aug 22, 2012 at 11:19:07AM +0530, Aneesh Kumar K.V wrote:
Pavel Emelyanov writes:
Why? For e.g. ext4 you can construct a handle in userspace and open by
it.
open_by_handle use exportfs_decode_fh which use file system specific
On Wed, Aug 22, 2012 at 11:19:07AM +0530, Aneesh Kumar K.V wrote:
> Pavel Emelyanov writes:
>
> > Why? For e.g. ext4 you can construct a handle in userspace and open by
> > it.
>
> open_by_handle use exportfs_decode_fh which use file system specific
> fh_to_dentry
>
> foe ext4 we require a
On Wed, Aug 22, 2012 at 11:19:07AM +0530, Aneesh Kumar K.V wrote:
Pavel Emelyanov xe...@parallels.com writes:
Why? For e.g. ext4 you can construct a handle in userspace and open by
it.
open_by_handle use exportfs_decode_fh which use file system specific
fh_to_dentry
foe ext4 we
Il 23/08/2012 10:06, Cyrill Gorcunov ha scritto:
On Wed, Aug 22, 2012 at 11:19:07AM +0530, Aneesh Kumar K.V wrote:
Pavel Emelyanov xe...@parallels.com writes:
Why? For e.g. ext4 you can construct a handle in userspace and open by
it.
open_by_handle use exportfs_decode_fh which use file
On Thu, Aug 23, 2012 at 10:54:44AM +0200, Marco Stornelli wrote:
For brtfs
objectid = fid-objectid;
root_objectid = fid-root_objectid;
generation = fid-gen;
return btrfs_get_dentry(sb, objectid, root_objectid, generation, 1);
For btrfs it become more complex. But still
Pavel Emelyanov writes:
> On 08/21/2012 02:42 PM, Aneesh Kumar K.V wrote:
>> Pavel Emelyanov writes:
>>
>>> On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
> On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields
On Tue, Aug 21, 2012 at 08:29:08AM -0400, J. Bruce Fields wrote:
> > Initial problem -- we don't know what is being watched by an inotify fd.
> >
> > Having a dentry somewhere was the 1st attempt to solve this -- keep a path
> > in inotify and show it when required. It doesn't work since holding
On Tue, Aug 21, 2012 at 03:51:36PM +0300, Boaz Harrosh wrote:
> For the minority of FSs that do not have a filehandle support it should
> be easy to generate a generic one, that should work 95% of the time.
Great. Your task, then, is to show how to do that for sysfs. Or for nfs.
Those should be
On 08/21/2012 03:59 PM, Pavel Emelyanov wrote:
> On 08/21/2012 04:51 PM, Boaz Harrosh wrote:
>> On 08/21/2012 03:29 PM, J. Bruce Fields wrote:
>> <>
>
> Strictly speaking -- no we don't. Migration should to work across kernel
> versions (from older to newer). Why kernel version matters in this
On 08/21/2012 04:51 PM, Boaz Harrosh wrote:
> On 08/21/2012 03:29 PM, J. Bruce Fields wrote:
> <>
>
>> OK. So if you don't mind the fact that there are filesystems with
>> inotify support but not filehandle support, then I think generating a
>> filehandle early as you describe would work. I
On 08/21/2012 03:29 PM, J. Bruce Fields wrote:
<>
> OK. So if you don't mind the fact that there are filesystems with
> inotify support but not filehandle support, then I think generating a
> filehandle early as you describe would work. I guess it's a little more
> memory per watched inode.
>
Al, Bruce, Aneesh,
What if we calculate the handle at the time we do have struct path at
hands (i.e.
when we create the inotify) and store it on the inotify structure purely
to be
shown later in proc. Would that be acceptable?
>>>
>>> Was it the lack of a
On Tue, Aug 21, 2012 at 04:22:31PM +0400, Pavel Emelyanov wrote:
> On 08/21/2012 04:11 PM, J. Bruce Fields wrote:
> > On Tue, Aug 21, 2012 at 03:09:05PM +0400, Pavel Emelyanov wrote:
> >> On 08/21/2012 02:54 PM, Cyrill Gorcunov wrote:
> >>> On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov
On 08/21/2012 04:09 PM, J. Bruce Fields wrote:
> On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
>> On 08/21/2012 02:42 PM, Aneesh Kumar K.V wrote:
>>> Pavel Emelyanov writes:
>>>
On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
> On Mon, Aug 20, 2012 at 11:06:06PM +0400,
On 08/21/2012 04:11 PM, J. Bruce Fields wrote:
> On Tue, Aug 21, 2012 at 03:09:05PM +0400, Pavel Emelyanov wrote:
>> On 08/21/2012 02:54 PM, Cyrill Gorcunov wrote:
>>> On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
>>
>> However, if you have some better ideas on what
On Tue, Aug 21, 2012 at 03:09:05PM +0400, Pavel Emelyanov wrote:
> On 08/21/2012 02:54 PM, Cyrill Gorcunov wrote:
> > On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
>
> However, if you have some better ideas on what information about inode
> should be exported
>
On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
> On 08/21/2012 02:42 PM, Aneesh Kumar K.V wrote:
> > Pavel Emelyanov writes:
> >
> >> On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
> >>> On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
> On Mon, Aug 20,
On 08/21/2012 02:54 PM, Cyrill Gorcunov wrote:
> On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
However, if you have some better ideas on what information about inode
should be exported
to the userspace please share.
>>>
>>> Why not use
On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
> >>
> >> However, if you have some better ideas on what information about inode
> >> should be exported
> >> to the userspace please share.
> >>
> >
> > Why not use name_to_handle(fd,...) and open_by_handle(handle,..) ?
>
>
On 08/21/2012 02:42 PM, Aneesh Kumar K.V wrote:
> Pavel Emelyanov writes:
>
>> On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
>>> On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
> On Mon, Aug 20, 2012 at
Pavel Emelyanov writes:
> On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
>> On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
>>> On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
> On Mon,
On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
> On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
>> On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
>>> On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 07:49:23PM +0530,
Pavel Emelyanov xe...@parallels.com writes:
On 08/21/2012 02:42 PM, Aneesh Kumar K.V wrote:
Pavel Emelyanov xe...@parallels.com writes:
On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 02:32:25PM -0400,
On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 07:49:23PM +0530, Aneesh
Pavel Emelyanov xe...@parallels.com writes:
On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
On
On 08/21/2012 02:42 PM, Aneesh Kumar K.V wrote:
Pavel Emelyanov xe...@parallels.com writes:
On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
On Mon, Aug 20, 2012
On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
However, if you have some better ideas on what information about inode
should be exported
to the userspace please share.
Why not use name_to_handle(fd,...) and open_by_handle(handle,..) ?
Because we don't have an
On 08/21/2012 02:54 PM, Cyrill Gorcunov wrote:
On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
However, if you have some better ideas on what information about inode
should be exported
to the userspace please share.
Why not use name_to_handle(fd,...) and
On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
On 08/21/2012 02:42 PM, Aneesh Kumar K.V wrote:
Pavel Emelyanov xe...@parallels.com writes:
On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20,
On Tue, Aug 21, 2012 at 03:09:05PM +0400, Pavel Emelyanov wrote:
On 08/21/2012 02:54 PM, Cyrill Gorcunov wrote:
On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
However, if you have some better ideas on what information about inode
should be exported
to the userspace
On 08/21/2012 04:11 PM, J. Bruce Fields wrote:
On Tue, Aug 21, 2012 at 03:09:05PM +0400, Pavel Emelyanov wrote:
On 08/21/2012 02:54 PM, Cyrill Gorcunov wrote:
On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
However, if you have some better ideas on what information about
On 08/21/2012 04:09 PM, J. Bruce Fields wrote:
On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
On 08/21/2012 02:42 PM, Aneesh Kumar K.V wrote:
Pavel Emelyanov xe...@parallels.com writes:
On 08/20/2012 11:32 PM, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 11:06:06PM +0400,
On Tue, Aug 21, 2012 at 04:22:31PM +0400, Pavel Emelyanov wrote:
On 08/21/2012 04:11 PM, J. Bruce Fields wrote:
On Tue, Aug 21, 2012 at 03:09:05PM +0400, Pavel Emelyanov wrote:
On 08/21/2012 02:54 PM, Cyrill Gorcunov wrote:
On Tue, Aug 21, 2012 at 02:49:47PM +0400, Pavel Emelyanov wrote:
Al, Bruce, Aneesh,
What if we calculate the handle at the time we do have struct path at
hands (i.e.
when we create the inotify) and store it on the inotify structure purely
to be
shown later in proc. Would that be acceptable?
Was it the lack of a dentry that was really the problem? I
On 08/21/2012 03:29 PM, J. Bruce Fields wrote:
OK. So if you don't mind the fact that there are filesystems with
inotify support but not filehandle support, then I think generating a
filehandle early as you describe would work. I guess it's a little more
memory per watched inode.
For
On 08/21/2012 04:51 PM, Boaz Harrosh wrote:
On 08/21/2012 03:29 PM, J. Bruce Fields wrote:
OK. So if you don't mind the fact that there are filesystems with
inotify support but not filehandle support, then I think generating a
filehandle early as you describe would work. I guess it's a
On 08/21/2012 03:59 PM, Pavel Emelyanov wrote:
On 08/21/2012 04:51 PM, Boaz Harrosh wrote:
On 08/21/2012 03:29 PM, J. Bruce Fields wrote:
Strictly speaking -- no we don't. Migration should to work across kernel
versions (from older to newer). Why kernel version matters in this case?
I
On Tue, Aug 21, 2012 at 03:51:36PM +0300, Boaz Harrosh wrote:
For the minority of FSs that do not have a filehandle support it should
be easy to generate a generic one, that should work 95% of the time.
Great. Your task, then, is to show how to do that for sysfs. Or for nfs.
Those should be
On Tue, Aug 21, 2012 at 08:29:08AM -0400, J. Bruce Fields wrote:
Initial problem -- we don't know what is being watched by an inotify fd.
Having a dentry somewhere was the 1st attempt to solve this -- keep a path
in inotify and show it when required. It doesn't work since holding a ref on
On Mon, Aug 20, 2012 at 03:32:04PM -0400, J. Bruce Fields wrote:
> > > > Hi, sorry for dealy. Well, the last idea is to get rid of this helper,
> > > > I've sent out an updated version where ino+dev is only printed.
> > >
> > > I don't understand how ino and dev are useful to you, though, if
On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
> On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
> > On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
> > > On Mon, Aug 20, 2012 at 07:49:23PM +0530, Aneesh Kumar K.V wrote:
> > > > Cyrill Gorcunov
On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
> On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
> > On Mon, Aug 20, 2012 at 07:49:23PM +0530, Aneesh Kumar K.V wrote:
> > > Cyrill Gorcunov writes:
> > >
> > > > To provide fsnotify object inodes being watched
On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
> On Mon, Aug 20, 2012 at 07:49:23PM +0530, Aneesh Kumar K.V wrote:
> > Cyrill Gorcunov writes:
> >
> > > To provide fsnotify object inodes being watched without
> > > binding to alphabetical path we need to encode them with
> > >
On Mon, Aug 20, 2012 at 07:49:23PM +0530, Aneesh Kumar K.V wrote:
> Cyrill Gorcunov writes:
>
> > To provide fsnotify object inodes being watched without
> > binding to alphabetical path we need to encode them with
> > exportfs help. This patch adds a helper which operates
> > with plain inodes
Cyrill Gorcunov writes:
> To provide fsnotify object inodes being watched without
> binding to alphabetical path we need to encode them with
> exportfs help. This patch adds a helper which operates
> with plain inodes directly.
doesn't name_to_handle_at() work for you ? It also allows to get a
Cyrill Gorcunov gorcu...@openvz.org writes:
To provide fsnotify object inodes being watched without
binding to alphabetical path we need to encode them with
exportfs help. This patch adds a helper which operates
with plain inodes directly.
doesn't name_to_handle_at() work for you ? It also
On Mon, Aug 20, 2012 at 07:49:23PM +0530, Aneesh Kumar K.V wrote:
Cyrill Gorcunov gorcu...@openvz.org writes:
To provide fsnotify object inodes being watched without
binding to alphabetical path we need to encode them with
exportfs help. This patch adds a helper which operates
with
On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 07:49:23PM +0530, Aneesh Kumar K.V wrote:
Cyrill Gorcunov gorcu...@openvz.org writes:
To provide fsnotify object inodes being watched without
binding to alphabetical path we need to encode them
On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 07:49:23PM +0530, Aneesh Kumar K.V wrote:
Cyrill Gorcunov gorcu...@openvz.org writes:
To provide fsnotify object inodes being
On Mon, Aug 20, 2012 at 11:06:06PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 02:32:25PM -0400, J. Bruce Fields wrote:
On Mon, Aug 20, 2012 at 08:33:38PM +0400, Cyrill Gorcunov wrote:
On Mon, Aug 20, 2012 at 07:49:23PM +0530, Aneesh Kumar K.V wrote:
Cyrill Gorcunov
On Mon, Aug 20, 2012 at 03:32:04PM -0400, J. Bruce Fields wrote:
Hi, sorry for dealy. Well, the last idea is to get rid of this helper,
I've sent out an updated version where ino+dev is only printed.
I don't understand how ino and dev are useful to you, though, if you're
still
Al Viro writes:
> On Thu, Aug 16, 2012 at 06:15:53PM +0400, Cyrill Gorcunov wrote:
>> On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
>> > > > What's wrong with saying "we don't support idiotify"?
>> > >
>> > > Al, we need some way to restore inotifies after checkpoint.
>> > >
Al Viro v...@zeniv.linux.org.uk writes:
On Thu, Aug 16, 2012 at 06:15:53PM +0400, Cyrill Gorcunov wrote:
On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
What's wrong with saying we don't support idiotify?
Al, we need some way to restore inotifies after checkpoint.
On Thu, Aug 16, 2012 at 07:06:18PM +0400, Pavel Emelyanov wrote:
> On 08/16/2012 06:55 PM, Al Viro wrote:
> > On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
> >
> >>> Good luck doing that with e.g. VFAT... And then there's such thing
> >>> as filesystems that don't have
On Thu, Aug 16, 2012 at 04:05:42PM +0100, Al Viro wrote:
> On Thu, Aug 16, 2012 at 06:57:00PM +0400, Cyrill Gorcunov wrote:
>
> > Guys, would the patch below be more-less acceptible?
> > In inotify I think we could pass "parent" as NULL and use general
> > encode engine then (ie it will look like
On Thu, Aug 16, 2012 at 03:55:27PM +0100, Al Viro wrote:
> On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
>
> > > Good luck doing that with e.g. VFAT... And then there's such thing
> > > as filesystems that don't have ->encode_fh() for a lot of very good
> >
> > Wait, Al, it
On 08/16/2012 06:55 PM, Al Viro wrote:
> On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
>
>>> Good luck doing that with e.g. VFAT... And then there's such thing
>>> as filesystems that don't have ->encode_fh() for a lot of very good
>>
>> Wait, Al, it seems I messed up. If some
On Thu, Aug 16, 2012 at 06:57:00PM +0400, Cyrill Gorcunov wrote:
> Guys, would the patch below be more-less acceptible?
> In inotify I think we could pass "parent" as NULL and use general
> encode engine then (ie it will look like someone called for
> name_to_handle_at on inotify target).
Wait.
On Thu, Aug 16, 2012 at 08:47:03AM -0400, J. Bruce Fields wrote:
> On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
> > On Thu, Aug 16, 2012 at 10:24:48AM +0400, Cyrill Gorcunov wrote:
> > > > > > On the other hand, if you want a real filehandle then wouldn't you
> > > > > > want
On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
> > Good luck doing that with e.g. VFAT... And then there's such thing
> > as filesystems that don't have ->encode_fh() for a lot of very good
>
> Wait, Al, it seems I messed up. If some fs has no encode_fh() implemented
> the
On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
> On Thu, Aug 16, 2012 at 03:41:52PM +0100, Al Viro wrote:
> > On Thu, Aug 16, 2012 at 06:15:53PM +0400, Cyrill Gorcunov wrote:
> > > On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
> > > > > > What's wrong with
On Thu, Aug 16, 2012 at 03:41:52PM +0100, Al Viro wrote:
> On Thu, Aug 16, 2012 at 06:15:53PM +0400, Cyrill Gorcunov wrote:
> > On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
> > > > > What's wrong with saying "we don't support idiotify"?
> > > >
> > > > Al, we need some way to
On Thu, Aug 16, 2012 at 06:15:53PM +0400, Cyrill Gorcunov wrote:
> On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
> > > > What's wrong with saying "we don't support idiotify"?
> > >
> > > Al, we need some way to restore inotifies after checkpoint.
> > > At the very early
On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
> > > What's wrong with saying "we don't support idiotify"?
> >
> > Al, we need some way to restore inotifies after checkpoint.
> > At the very early versions of these patches I simply added
> > dentry to the inotify mark thus once
On 08/16/2012 06:03 PM, James Bottomley wrote:
> On Thu, 2012-08-16 at 17:54 +0400, Cyrill Gorcunov wrote:
>> On Thu, Aug 16, 2012 at 02:50:19PM +0100, Al Viro wrote:
>>> On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
On 08/16/2012 05:43 PM, Al Viro wrote:
> On Thu, Aug
On Thu, 2012-08-16 at 17:54 +0400, Cyrill Gorcunov wrote:
> On Thu, Aug 16, 2012 at 02:50:19PM +0100, Al Viro wrote:
> > On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
> > > On 08/16/2012 05:43 PM, Al Viro wrote:
> > > > On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov
On Thu, Aug 16, 2012 at 02:50:19PM +0100, Al Viro wrote:
> On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
> > On 08/16/2012 05:43 PM, Al Viro wrote:
> > > On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
> > >
> > >> Hi Bruce, thinking a bit more I guess using
On 08/16/2012 05:50 PM, Al Viro wrote:
> On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
>> On 08/16/2012 05:43 PM, Al Viro wrote:
>>> On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
>>>
Hi Bruce, thinking a bit more I guess using general encode_fh is not
On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
> On 08/16/2012 05:43 PM, Al Viro wrote:
> > On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
> >
> >> Hi Bruce, thinking a bit more I guess using general encode_fh is not that
> >> convenient since it operates with
On Thu, Aug 16, 2012 at 02:43:39PM +0100, Al Viro wrote:
> On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
>
> > Hi Bruce, thinking a bit more I guess using general encode_fh is not that
> > convenient since it operates with dentries while our fdinfo output deals
> > with inodes.
On 08/16/2012 05:43 PM, Al Viro wrote:
> On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
>
>> Hi Bruce, thinking a bit more I guess using general encode_fh is not that
>> convenient since it operates with dentries while our fdinfo output deals
>> with inodes. Thus I should either
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
> Hi Bruce, thinking a bit more I guess using general encode_fh is not that
> convenient since it operates with dentries while our fdinfo output deals
> with inodes. Thus I should either provide some new encode_fh variant
> which
On Thu, Aug 16, 2012 at 08:47:03AM -0400, J. Bruce Fields wrote:
> > Hi Bruce, thinking a bit more I guess using general encode_fh is not that
> > convenient since it operates with dentries while our fdinfo output deals
> > with inodes. Thus I should either provide some new encode_fh variant
> >
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
> On Thu, Aug 16, 2012 at 10:24:48AM +0400, Cyrill Gorcunov wrote:
> > > > > On the other hand, if you want a real filehandle then wouldn't you
> > > > > want
> > > > > to e.g. call the filesystem's ->encode_fh() if necessary, as
>
On Thu, Aug 16, 2012 at 10:24:48AM +0400, Cyrill Gorcunov wrote:
> > > > On the other hand, if you want a real filehandle then wouldn't you want
> > > > to e.g. call the filesystem's ->encode_fh() if necessary, as
> > > > exportfs_encode_fh() does?
> > >
> > > Well, one of the problem I hit when
On Wed, Aug 15, 2012 at 06:06:23PM -0400, J. Bruce Fields wrote:
> On Thu, Aug 16, 2012 at 01:02:37AM +0400, Cyrill Gorcunov wrote:
> > On Wed, Aug 15, 2012 at 04:45:46PM -0400, J. Bruce Fields wrote:
> > > On Wed, Aug 15, 2012 at 01:21:20PM +0400, Cyrill Gorcunov wrote:
> > > > To provide
On Wed, Aug 15, 2012 at 06:06:23PM -0400, J. Bruce Fields wrote:
On Thu, Aug 16, 2012 at 01:02:37AM +0400, Cyrill Gorcunov wrote:
On Wed, Aug 15, 2012 at 04:45:46PM -0400, J. Bruce Fields wrote:
On Wed, Aug 15, 2012 at 01:21:20PM +0400, Cyrill Gorcunov wrote:
To provide fsnotify object
On Thu, Aug 16, 2012 at 10:24:48AM +0400, Cyrill Gorcunov wrote:
On the other hand, if you want a real filehandle then wouldn't you want
to e.g. call the filesystem's -encode_fh() if necessary, as
exportfs_encode_fh() does?
Well, one of the problem I hit when I've been trying to
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
On Thu, Aug 16, 2012 at 10:24:48AM +0400, Cyrill Gorcunov wrote:
On the other hand, if you want a real filehandle then wouldn't you
want
to e.g. call the filesystem's -encode_fh() if necessary, as
On Thu, Aug 16, 2012 at 08:47:03AM -0400, J. Bruce Fields wrote:
Hi Bruce, thinking a bit more I guess using general encode_fh is not that
convenient since it operates with dentries while our fdinfo output deals
with inodes. Thus I should either provide some new encode_fh variant
which
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
Hi Bruce, thinking a bit more I guess using general encode_fh is not that
convenient since it operates with dentries while our fdinfo output deals
with inodes. Thus I should either provide some new encode_fh variant
which would
On 08/16/2012 05:43 PM, Al Viro wrote:
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
Hi Bruce, thinking a bit more I guess using general encode_fh is not that
convenient since it operates with dentries while our fdinfo output deals
with inodes. Thus I should either provide
On Thu, Aug 16, 2012 at 02:43:39PM +0100, Al Viro wrote:
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
Hi Bruce, thinking a bit more I guess using general encode_fh is not that
convenient since it operates with dentries while our fdinfo output deals
with inodes. Thus I
On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
On 08/16/2012 05:43 PM, Al Viro wrote:
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
Hi Bruce, thinking a bit more I guess using general encode_fh is not that
convenient since it operates with dentries
On 08/16/2012 05:50 PM, Al Viro wrote:
On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
On 08/16/2012 05:43 PM, Al Viro wrote:
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
Hi Bruce, thinking a bit more I guess using general encode_fh is not that
convenient
On Thu, Aug 16, 2012 at 02:50:19PM +0100, Al Viro wrote:
On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
On 08/16/2012 05:43 PM, Al Viro wrote:
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
Hi Bruce, thinking a bit more I guess using general
On Thu, 2012-08-16 at 17:54 +0400, Cyrill Gorcunov wrote:
On Thu, Aug 16, 2012 at 02:50:19PM +0100, Al Viro wrote:
On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
On 08/16/2012 05:43 PM, Al Viro wrote:
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
On 08/16/2012 06:03 PM, James Bottomley wrote:
On Thu, 2012-08-16 at 17:54 +0400, Cyrill Gorcunov wrote:
On Thu, Aug 16, 2012 at 02:50:19PM +0100, Al Viro wrote:
On Thu, Aug 16, 2012 at 05:47:06PM +0400, Pavel Emelyanov wrote:
On 08/16/2012 05:43 PM, Al Viro wrote:
On Thu, Aug 16, 2012 at
On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
What's wrong with saying we don't support idiotify?
Al, we need some way to restore inotifies after checkpoint.
At the very early versions of these patches I simply added
dentry to the inotify mark thus once inotify
On Thu, Aug 16, 2012 at 06:15:53PM +0400, Cyrill Gorcunov wrote:
On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
What's wrong with saying we don't support idiotify?
Al, we need some way to restore inotifies after checkpoint.
At the very early versions of these
On Thu, Aug 16, 2012 at 03:41:52PM +0100, Al Viro wrote:
On Thu, Aug 16, 2012 at 06:15:53PM +0400, Cyrill Gorcunov wrote:
On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
What's wrong with saying we don't support idiotify?
Al, we need some way to restore inotifies
On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
On Thu, Aug 16, 2012 at 03:41:52PM +0100, Al Viro wrote:
On Thu, Aug 16, 2012 at 06:15:53PM +0400, Cyrill Gorcunov wrote:
On Thu, Aug 16, 2012 at 02:03:00PM +, James Bottomley wrote:
What's wrong with saying we don't
On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
Good luck doing that with e.g. VFAT... And then there's such thing
as filesystems that don't have -encode_fh() for a lot of very good
Wait, Al, it seems I messed up. If some fs has no encode_fh() implemented
the default
On Thu, Aug 16, 2012 at 08:47:03AM -0400, J. Bruce Fields wrote:
On Thu, Aug 16, 2012 at 04:38:14PM +0400, Cyrill Gorcunov wrote:
On Thu, Aug 16, 2012 at 10:24:48AM +0400, Cyrill Gorcunov wrote:
On the other hand, if you want a real filehandle then wouldn't you
want
to e.g.
On Thu, Aug 16, 2012 at 06:57:00PM +0400, Cyrill Gorcunov wrote:
Guys, would the patch below be more-less acceptible?
In inotify I think we could pass parent as NULL and use general
encode engine then (ie it will look like someone called for
name_to_handle_at on inotify target).
Wait. What
On 08/16/2012 06:55 PM, Al Viro wrote:
On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
Good luck doing that with e.g. VFAT... And then there's such thing
as filesystems that don't have -encode_fh() for a lot of very good
Wait, Al, it seems I messed up. If some fs has no
On Thu, Aug 16, 2012 at 03:55:27PM +0100, Al Viro wrote:
On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
Good luck doing that with e.g. VFAT... And then there's such thing
as filesystems that don't have -encode_fh() for a lot of very good
Wait, Al, it seems I messed
On Thu, Aug 16, 2012 at 04:05:42PM +0100, Al Viro wrote:
On Thu, Aug 16, 2012 at 06:57:00PM +0400, Cyrill Gorcunov wrote:
Guys, would the patch below be more-less acceptible?
In inotify I think we could pass parent as NULL and use general
encode engine then (ie it will look like someone
On Thu, Aug 16, 2012 at 07:06:18PM +0400, Pavel Emelyanov wrote:
On 08/16/2012 06:55 PM, Al Viro wrote:
On Thu, Aug 16, 2012 at 06:48:35PM +0400, Cyrill Gorcunov wrote:
Good luck doing that with e.g. VFAT... And then there's such thing
as filesystems that don't have -encode_fh() for a
1 - 100 of 108 matches
Mail list logo
