Man Page: deactivate_locked_super
Operating Environment: suse
Section: 9
DEACTIVATE_LOCKED_SU(9) The Linux VFS DEACTIVATE_LOCKED_SU(9)NAMEdeactivate_locked_super - drop an active reference to superblockSYNOPSISvoid deactivate_locked_super(struct super_block * s);ARGUMENTSs superblock to deactivateDESCRIPTIONEquivalent of up_write(s->s_umount); deactivate_super(s);, except that it does not unlock it until it's all over. As the result, it's safe to use to dispose of new superblock on ->get_sb failure exits - nobody will see the sucker until it's all over. Equivalent using up_write + deactivate_super is safe for that purpose only if superblock is either safe to use or has NULL ->s_root when we unlock.COPYRIGHTKernel Hackers Manual 2.6. July 2010 DEACTIVATE_LOCKED_SU(9)
| Related Man Pages |
|---|
| fstyp(1m) - hpux |
| dumpe2fs(8) - minix |
| dumpe2fs(8) - opensolaris |
| dumpe2fs(8) - sunos |
| dumpe2fs(8) - php |
| Similar Topics in the Unix Linux Community |
|---|
| How to restrict user to a specific directory in solaris 10 |
| SOCKS proxy & PAM configuration exposure |
| Tar Command |
| Docker learning Phase-I |
| 32 bit process addressing more than 4GB |