* [RFC]fs: fsprivate data argument for get_block_t
@ 2012-09-07 9:04 Dmitry Monakhov
0 siblings, 0 replies; only message in thread
From: Dmitry Monakhov @ 2012-09-07 9:04 UTC (permalink / raw)
To: linux-fsdevel, linux-kernel
Hi, I'm wonder why generic get_block_t callback has not fsprivate
argument?
Each filesystem implement it's own get_block_t callback.
Each filesystem call generic functions which use callback from
known context, but where is no good way to pass that context
to fs_specific_get_block callback.
This result in situation where fs-specific data passed via
inode's data (xxx_inode->cur_get_block_data)
All this means that inode's private pointer becomes implicit
serialization point even if get_block() are allowed to be called
concurrently.
I'm going to add fsprivate argument, number of generic function which
use get_block_t is not really huge, so the patch should be too big.
If some one has any objections why this shouldn't be done, please
welcome.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-09-07 9:04 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-09-07 9:04 [RFC]fs: fsprivate data argument for get_block_t Dmitry Monakhov
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).