Logo
Explore Help
Register Sign In
Evolution-x-devices/kernel_google_b1c1
2
0
Fork 0
You've already forked kernel_google_b1c1
mirror of https://github.com/Evolution-X-Devices/kernel_google_b1c1 synced 2026-02-10 12:20:09 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
38da1703060a520e69b00405f9bdf765d1396cd0
kernel_google_b1c1/include/linux/fs_pin.h

18 lines
326 B
C
Raw Normal View History

take fs_pin stuff to fs/* Add a new field to fs_pin - kill(pin). That's what umount and r/o remount will be calling for all pins attached to vfsmount and superblock resp. Called after bumping the refcount, so it won't go away under us. Dropping the refcount is responsibility of the instance. All generic stuff moved to fs/fs_pin.c; the next step will rip all the knowledge of kernel/acct.c from fs/super.c and fs/namespace.c. After that - death to mnt_pin(); it was intended to be usable as generic mechanism for code that wants to attach objects to vfsmount, so that they would not make the sucker busy and would get killed on umount. Never got it right; it remained acct.c-specific all along. Now it's very close to being killable. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2014-08-07 08:39:04 -04:00
#include <linux/fs.h>
struct fs_pin {
atomic_long_t count;
union {
struct {
struct hlist_node s_list;
struct hlist_node m_list;
};
struct rcu_head rcu;
};
void (*kill)(struct fs_pin *);
};
void pin_put(struct fs_pin *);
void pin_remove(struct fs_pin *);
void pin_insert(struct fs_pin *, struct vfsmount *);
Reference in New Issue Copy Permalink
Powered by Gitea Version: 1.25.3 Page: 51ms Template: 1ms
English
Bahasa Indonesia Deutsch English Español Français Gaeilge Italiano Latviešu Magyar nyelv Nederlands Polski Português de Portugal Português do Brasil Suomi Svenska Türkçe Čeština Ελληνικά Български Русский Українська فارسی മലയാളം 日本語 简体中文 繁體中文(台灣) 繁體中文(香港) 한국어
Licenses API