The pull request you sent on Tue, 7 May 2019 01:50:37 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.icache
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/168e153d5ebbdd6a3fa85db1cc4879ed4b7030e0
Thank you!
--
Deet-doot-dot, I am a bot.
htt
Introduction of separate method for RCU-delayed
part of ->destroy_inode() (if any). Pretty much as posted,
except that destroy_inode() stashes ->free_inode into the
victim (anon-unioned with ->i_fops) before scheduling
i_callback() and the last two patches (sockfs conversion
and folding st
More sendmsg work; this is a fairly separate isolated stuff (there's
a continuation around lustre, but that one was too late to soak in
-next), thus the separate pull request. One trivial conflict in
drivers/block/nbd.c, proposed resolution in vfs.git#merge-1
The following changes since commit b4
The big thing in this pile is Eric's unmount-on-rmdir series; we finally
have everything we need for that. The final piece of prereqs is delayed
mntput() - now filesystem shutdown always happens on shallow stack.
Other than that, we have several new primitives for iov_iter (Matt Wilcox,
culled fr
Stuff in there:
1) acct.c fixes and general rework of mnt_pin mechanism. That allows to go for
delayed-mntput stuff, which will permit mntput() on deep stack without worrying
about stack overflows - fs shutdown will happen on shallow stack. IOW, we
can do Eric's umount-on-rmdir series wit
On 07/23/2012 12:03 PM, Al Viro wrote:
> On Mon, Jul 23, 2012 at 11:20:25AM +0300, Boaz Harrosh wrote:
>> On 07/22/2012 11:20 PM, Al Viro wrote:
>>
>>> I think the least painful solution is this: I've created a new branch
>>> (for-linus-2) in there, growing off the parent of merge in nfs.git.
>>>
On Mon, Jul 23, 2012 at 11:20:25AM +0300, Boaz Harrosh wrote:
> On 07/22/2012 11:20 PM, Al Viro wrote:
>
> > I think the least painful solution is this: I've created a new branch
> > (for-linus-2) in there, growing off the parent of merge in nfs.git.
> > I've put the fixup to kern_path_locked() th
On 07/22/2012 11:20 PM, Al Viro wrote:
> I think the least painful solution is this: I've created a new branch
> (for-linus-2) in there, growing off the parent of merge in nfs.git.
> I've put the fixup to kern_path_locked() there as a separate commit
> + stuff that went in for-linus after that poi
Hi Al,
On Mon, 23 Jul 2012 07:09:09 +0100 Al Viro wrote:
>
> On Sun, Jul 22, 2012 at 09:20:30PM +0100, Al Viro wrote:
> > Result: for-linus-2 + v3.5 and for-linus + v3.5 give identical trees,
> > and for-linus-2 merges clean with nfs/nfs-for-3.6. Would you be OK
> > with pulling that one? Again
On Sun, Jul 22, 2012 at 09:20:30PM +0100, Al Viro wrote:
> Result: for-linus-2 + v3.5 and for-linus + v3.5 give identical trees,
> and for-linus-2 merges clean with nfs/nfs-for-3.6. Would you be OK
> with pulling that one? Again, my apologies to everyone involved ;-/
>
> If you are OK with pulli
On Sun, Jul 22, 2012 at 10:34:10AM -0700, Linus Torvalds wrote:
> I'm not pulling this until the mess with the NFS tree is sorted out.
> Apparently you rebased your (public!) VFS tree, and now half of your
> old pre-rebase patches are in the NFS tree.
>
> Rebasing public trees IS NOT A VALID OPERA
I'm not pulling this until the mess with the NFS tree is sorted out.
Apparently you rebased your (public!) VFS tree, and now half of your
old pre-rebase patches are in the NFS tree.
Rebasing public trees IS NOT A VALID OPERATION! Exactly because of
messes like this.
So no. No way am I pulling a b
This one is *big* and changes quite a few things around VFS. What's in there:
* the first of two really major architecture changes - death to
open intents. The former is finally there; it was very long in making,
but with Miklos getting through really hard and messy final push in
fs/name
13 matches
Mail list logo
