linux-kernel - [PATCH 0/5] clean-up patch for autofs4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 Jul 2014 10:48:28 +1000
From:	NeilBrown <neilb@...e.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	autofs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] clean-up patch for autofs4

Hi Andrew,
 I believe you shepherd autofs4 patches at present.
 The following 5 patches are some simple cleanups.
 4 are trivial.  One (the third) is a very simple optimization
 which will be more important after the next patch set, but
 is simple enough to be included now.

 The next patch set will make autofs4 RCU-walk friendly so that in the
 common case a filename lookup can walk across an autofs4 filesystem
 without taking spinlocks or refcounts.  I'll submit that once more
 testing and review have convinced Ian and myself that it is ready.

 Thanks,
 NeilBrown

---

NeilBrown (5):
      autofs4: remove unused autofs4_ispending()
      autofs4: remove a redundant assignment
      autofs4: don't take spinlock when not needed in autofs4_lookup_expiring
      autofs4: remove some unused inline functions.
      autofs4: comment typo: remove a a doubled word.

 fs/autofs4/autofs_i.h |   63 -------------------------------------------------
 fs/autofs4/expire.c   |    1 -
 fs/autofs4/root.c     |   10 +++++---
 3 files changed, 7 insertions(+), 67 deletions(-)

-- 
Signature

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/