From: Kentaro Makita <k-makita@np.css.fujitsu.com>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
viro@ZenIV.linux.org.uk, harvey.harrison@gmail.com
Subject: [RESEND][PATCH -mm 0/2] vfs: __shrink_dcache_sb() fixes
Date: Tue, 24 Jun 2008 10:45:06 +0900 [thread overview]
Message-ID: <486051A2.6040805@np.css.fujitsu.com> (raw)
Hi,
I fix my patch based on Dave Chinner's comments as follows:
http://lkml.org/lkml/2008/5/22/469
This fix contains following two patches.
- fix coding style. (patch 1/2)
- add cond_resched_lock() in scanning LRU. (patch 2/2)
These patches depend on following patches on -mmotm tree, and tested on -rc5:
http://userweb.kernel.org/~akpm/mmotm/broken-out/fix-soft-lock-up-at-nfs-mount-by-per-sb-lru-list-of-unused-dentries.patch
http://userweb.kernel.org/~akpm/mmotm/broken-out/fix-soft-lock-up-at-nfs-mount-by-per-sb-lru-list-of-unused-dentries-fix.patch
Best Regards,
Kentaro Makita
reply other threads:[~2008-06-24 1:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=486051A2.6040805@np.css.fujitsu.com \
--to=k-makita@np.css.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).