From: "J. R. Okajima" <hooanon05g@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.15 .. and continuation of merge window
Date: Mon, 09 Jun 2014 12:30:34 +0900 [thread overview]
Message-ID: <13591.1402284634@jrobl> (raw)
In-Reply-To: <CA+55aFw3A=ycq4kRpsDDoV4+rzg0z2kwfE9C9Bg1nSwiYfUpLw@mail.gmail.com>
Linus Torvalds:
> So I ended up doing an rc8 because I was a bit worried about some
> last-minute dcache fixes, but it turns out that nobody seemed to even
> notice those. We did have other issues during the week, though, so it
:::
I am afraid there is a problem in dcache. Please read
http://marc.info/?l=linux-fsdevel&m=140214911608925&w=2
For 3.16, please consider these patches.
- for vfs
[PATCH v2] vfs: get_next_ino(), never inum=0
http://marc.info/?l=linux-fsdevel&m=140128600801771&w=2
- for tmpfs
[RFC PATCH v4 0/2] tmpfs: manage the inode-number by IDR (performance measure)
http://marc.info/?l=linux-fsdevel&m=140197128021025&w=2
[RFC PATCH v4 1/2] tmpfs: manage the inode-number by IDR, signed int inum
http://marc.info/?l=linux-fsdevel&m=140197128321029&w=2
[RFC PATCH v4 2/2] tmpfs: refine a file handle for NFS-exporting
http://marc.info/?l=linux-fsdevel&m=140197128121026&w=2
J. R. Okajima
next prev parent reply other threads:[~2014-06-09 3:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-08 18:52 Linux 3.15 .. and continuation of merge window Linus Torvalds
2014-06-09 3:30 ` J. R. Okajima [this message]
2014-06-11 1:10 ` Al Viro
2014-06-11 9:32 ` J. R. Okajima
2014-06-11 12:30 ` Al Viro
2014-06-11 17:56 ` J. R. Okajima
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=13591.1402284634@jrobl \
--to=hooanon05g@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.