Re: [PATCH] fs/locks.c: prepare for BKL removal

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

 



On Tuesday 21 September 2010 18:12:07 Sage Weil wrote:
> On Mon, 20 Sep 2010, Stephen Rothwell wrote:
> 
> > On Sun, 19 Sep 2010 20:59:01 -0700 (PDT) Sage Weil <sage@xxxxxxxxxxxx> wrote:
> > >
> > > I suspect the easiest thing is to leave Ceph out of this stage of your 
> > > series, I'll switch lock_kernel() to lock_flocks() once that exists 
> > > upstream.  Unless there is a better way? 
> > 
> > Maybe someone could write a trivial implementation of lock_flocks() (i.e.
> > one that does not make any changes to behaviour) and ask Linus to take it
> > now in preparation for the next merge window (he has done that before).
> > That way, more of this could be put into individual other trees and avoid
> > more conflicts ...
> 
> This sounds like the easiest solution to me.  Something as simple as
> 
> #define lock_flocks lock_kernel
> #define unlock_flocks unlock_kernel
> 
> in fs.h?

Sounds fine to me. I don't think it's necessary but if you prefer to do
it, you can have my Ack.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[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