linux-toradex.git/kernel/acct.c, branch v4.8-rc1

acct: check FMODE_CAN_WRITE

2015-04-12T02:27:55+00:00

it's not calling ->write() directly anymore.

Signed-off-by: Al Viro

new fs_pin killing logics

2015-01-26T04:17:28+00:00

Signed-off-by: Al Viro

get rid of the second argument of acct_kill()

2015-01-26T04:17:27+00:00

Replace the old ns->bacct only with NULL and only if it still points
to acct.  And assign the new value to it *before* calling acct_kill()
in acct_on().  That way we don't need to pass the new acct to acct_kill().

Signed-off-by: Al Viro

take count and rcu_head out of fs_pin

2015-01-26T04:17:27+00:00

Signed-off-by: Al Viro

pull bumping refcount into ->kill()

2015-01-26T04:16:29+00:00

there will be one more change of ->kill() calling conventions; this
isn't final.

Signed-off-by: Al Viro

kill pin_put()

2015-01-26T04:16:28+00:00

Signed-off-by: Al Viro

acct: eliminate compile warning

2014-10-10T02:26:04+00:00

If ACCT_VERSION is not defined to 3, below warning appears:
  CC      kernel/acct.o
  kernel/acct.c: In function `do_acct_process':
  kernel/acct.c:475:24: warning: unused variable `ns' [-Wunused-variable]

[akpm@linux-foundation.org: retain the local for code size improvements
Signed-off-by: Ying Xue 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

kernel/acct.c: fix coding style warnings and errors

2014-08-07T18:40:09+00:00

Signed-off-by: Ionut Alexa 
Signed-off-by: Andrew Morton 
Signed-off-by: Al Viro

death to mnt_pinned

2014-08-07T18:40:09+00:00

Rather than playing silly buggers with vfsmount refcounts, just have
acct_on() ask fs/namespace.c for internal clone of file->f_path.mnt
and replace it with said clone.  Then attach the pin to original
vfsmount.  Voila - the clone will be alive until the file gets closed,
making sure that underlying superblock remains active, etc., and
we can drop the original vfsmount, so that it's not kept busy.
If the file lives until the final mntput of the original vfsmount,
we'll notice that there's an fs_pin (one in bsd_acct_struct that
holds that file) and mnt_pin_kill() will take it out.  Since
->kill() is synchronous, we won't proceed past that point until
these files are closed (and private clones of our vfsmount are
gone), so we get the same ordering warranties we used to get.

mnt_pin()/mnt_unpin()/->mnt_pinned is gone now, and good riddance -
it never became usable outside of kernel/acct.c (and racy wrt
umount even there).

Signed-off-by: Al Viro

take fs_pin stuff to fs/*

2014-08-07T18:40:08+00:00

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