public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Who uses the 'nodev' flag in /proc/filesystems ???
@ 2006-03-19  5:27 Neil Brown
  2006-03-19  9:27 ` Jan Engelhardt
  2006-03-20 21:14 ` Andreas Schwab
  0 siblings, 2 replies; 12+ messages in thread
From: Neil Brown @ 2006-03-19  5:27 UTC (permalink / raw)
  To: linux-kernel



Hi, 
 I just noticed that the FS_REQUIRES_DEV flag is used for just two
 things in the kernel.

  1/ to place the text 'nodev' at the start of the line in
       /proc/filesystems
  2/ to tell nfsd that it is reasonably OK to use the s_dev field 
     in the superblock as a stable, unique identifier for the
     filesystem.

I have a filesystem I am playing with for which I am quite happy to
lose the second aspect of FS_REQUIRES_DEV (it does use a device, but
there could well be multiple devices, and the fs can migrate from one
device to another so s_dev is even less stable than normal).  However
I would like to understand the implications of losing the first aspect
of FS_REQUIRES_DEV before deciding whether to provide the flag or not.

Hence the question in the subject:

  Who uses the 'nodev' flag in /proc/filesystems?

Are there any known users of this flag?

Thanks,
NeilBrown


^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2006-03-21 17:32 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-19  5:27 Who uses the 'nodev' flag in /proc/filesystems ??? Neil Brown
2006-03-19  9:27 ` Jan Engelhardt
2006-03-20  4:46   ` Neil Brown
2006-03-20 16:06     ` Jan Engelhardt
2006-03-20 16:17       ` Matheus Izvekov
2006-03-20 17:56         ` Jeff Dike
2006-03-20 19:22           ` Matheus Izvekov
2006-03-20 19:48             ` Jeff Dike
2006-03-20 19:58               ` Jan Engelhardt
2006-03-21  0:32                 ` Jeff Dike
2006-03-21 17:31                   ` Jan Engelhardt
2006-03-20 21:14 ` Andreas Schwab

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox