From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Cc: Ladislav Michl <ladis@linux-mips.org>
Subject: [PATCH 0/2] fs: add revalidating of dentries
Date: Wed, 17 Oct 2018 10:43:51 +0200 [thread overview]
Message-ID: <20181017084353.5217-1-s.hauer@pengutronix.de> (raw)
Currently we do not revalidate dentries. I knew this is not correct for
network filesystems, but as it turned out it is also not correct for
devfs. In devfs files can be created/removed without the fs layer
noticing, so have to check if a dentry is still valid before using it.
Sascha Hauer (2):
fs: implement d_revalidate
fs: devfs: implement d_revalidate hook
fs/devfs.c | 27 +++++++++++++++++++++++++++
fs/fs.c | 37 ++++++++++++++++++++++++++++++++++++-
include/linux/dcache.h | 3 +++
3 files changed, 66 insertions(+), 1 deletion(-)
--
2.19.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2018-10-17 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 8:43 Sascha Hauer [this message]
2018-10-17 8:43 ` [PATCH 1/2] fs: implement d_revalidate Sascha Hauer
2018-10-17 8:43 ` [PATCH 2/2] fs: devfs: implement d_revalidate hook Sascha Hauer
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=20181017084353.5217-1-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=ladis@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox