J. R. Okajima:

     Anyway here is a new and consolidated patch. Apply this after all aufs
     patches you use and tmpfs-idr.patch. In other words, revert all patches
     I've sent via mail.

   I am sorry, but when I tried to patch I got following result (Hunk #4 FAILED
   at 1161.):
   test-comp linux # patch < 30-debug.patch -p1 --verbose
   Hmm...  Looks like a unified diff to me...
   The text leading up to this was:
   --------------------------
   |diff --git a/fs/dcache.c b/fs/dcache.c
   |index 581e93d..4231b85 100644
   |--- a/fs/dcache.c
   |+++ b/fs/dcache.c
   --------------------------
   Patching file fs/dcache.c using Plan A...
   Hunk #1 succeeded at 14.
   Hunk #2 succeeded at 280 (offset -32 lines).
   Hunk #3 succeeded at 301 (offset -32 lines).
   Hunk #4 FAILED at 1161.
   1 out of 4 hunks FAILED -- saving rejects to file fs/dcache.c.rej
   Hmm...  The next patch looks like a unified diff to me...
   The text leading up to this was:
   --------------------------
   |diff --git a/include/linux/shmem_fs.h b/include/linux/shmem_fs.h
   |index ca658a8..035f52c 100644
   |--- a/include/linux/shmem_fs.h
   |+++ b/include/linux/shmem_fs.h
   --------------------------
   Patching file include/linux/shmem_fs.h using Plan A...
   Hunk #1 succeeded at 26.
   Hmm...  The next patch looks like a unified diff to me...
   The text leading up to this was:
   --------------------------
   |diff --git a/lib/idr.c b/lib/idr.c
   |index bfe4db4..9e64a65 100644
   |--- a/lib/idr.c
   |+++ b/lib/idr.c
   --------------------------
   Patching file lib/idr.c using Plan A...
   Hunk #1 succeeded at 26.
   Hunk #2 succeeded at 40.
   Hunk #3 succeeded at 528.
   Hmm...  The next patch looks like a unified diff to me...
   The text leading up to this was:
   --------------------------
   |diff --git a/mm/shmem.c b/mm/shmem.c
   |index ecd2314..f5a9a5a 100644
   |--- a/mm/shmem.c
   |+++ b/mm/shmem.c
   --------------------------
   Patching file mm/shmem.c using Plan A...
   Hunk #1 succeeded at 21.
   Hunk #2 succeeded at 652 (offset -8 lines).
   Hunk #3 succeeded at 1438 (offset -17 lines).
   Hunk #4 succeeded at 2075 (offset -29 lines).
   Hunk #5 succeeded at 2632 (offset -22 lines).
   Hmm...  Ignoring the trailing garbage.
   done
   This is fs/dcache.c.rej file:
   --- fs/dcache.c
   +++ fs/dcache.c
   @@ -1161,6 +1175,13 @@
   Â Â Â Â  Â Â Â  Â Â Â  if (inode) {
   Â Â Â Â  Â Â Â  Â Â Â  Â Â Â  dentry->d_inode = NULL;
   Â Â Â Â  Â Â Â  Â Â Â  Â Â Â  hlist_del_init(&dentry->d_alias);
   +Â Â Â  Â Â Â  Â Â Â  Â Â Â  if (inode->i_sb->s_magic == TMPFS_MAGIC
   +Â Â Â  Â Â Â  Â Â Â  Â Â Â  Â Â Â  && inode->i_ino == 0x08000) {
   +Â Â Â  Â Â Â  Â Â Â  Â Â Â  Â Â Â  pr_info("%s %p i%lu 0%o %p\n",
   +Â Â Â   Â Â Â   Â Â Â   Â Â Â   Â Â Â  Â Â Â  dentry->[1]d_name.name,
   inode->i_sb,
   +Â Â Â  Â Â Â  Â Â Â  Â Â Â  Â Â Â  Â Â Â  inode->i_ino, inode->i_mode,
   inode);
   +Â Â Â   Â Â Â   Â Â Â   Â Â Â   Â Â Â   WARN_ON_ONCE(dentry->d_sb  !=
   inode->i_sb);
   +Â Â Â  Â Â Â  Â Â Â  Â Â Â  }
   Â Â Â Â  Â Â Â  Â Â Â  Â Â Â  if (dentry->d_op && dentry->d_op->d_iput)
   Â Â Â Â  Â Â Â  Â Â Â  Â Â Â  Â Â Â  dentry->d_op->d_iput(dentry, inode);
   Â Â Â Â  Â Â Â  Â Â Â  Â Â Â  else
   If  I  understand  correctly  there  should  be  function  static void
   shrink_dcache_for_umount_subtree(struct dentry *dentry)
   But I do not have this function in dcache.c
   I use Gentoo provided aufs-sources 3.14.6. Neither my sources nor master
   Github sources
   ([2]https://github.com/torvalds/linux/blob/master/fs/dcache.c) have this
   function. I also did not find it in any aufs patches.
   What did I do wrong?
   --
   Use GNU/Linux

References

   1. http://d_name.name/
   2. https://github.com/torvalds/linux/blob/master/fs/dcache.c
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems

Reply via email to