linux-kernel - [PATCH v2 0/6] Patch series to make lustre safe(r) for W=1 compiles

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 11 Dec 2015 18:04:19 -0500
From:	Valdis Kletnieks <Valdis.Kletnieks@...edu>
To:	gregkh@...uxfoundation.org, oleg.drokin@...el.com,
	andreas.dilger@...el.com
Cc:	devel@...verdev.osuosl.org, lustre-devel@...ts.lustre.org,
	linux-kernel@...r.kernel.org,
	Valdis Kletnieks <Valdis.Kletnieks@...edu>
Subject: [PATCH v2 0/6] Patch series to make lustre safe(r) for W=1 compiles

Start of a batch series to clean up the Lustre tree. Other people have
done some sparse and checkpatch cleanups, but I found a bunch of
stuff building with W=1. There's probably more, but this was the
really low-hanging obvious fruit.

Valdis Kletnieks (6):
  staging/lustre: Silence warning about 'inline'
  staging/lustre: Fix set-but-unused whinge.
  staging/lustre: Clean up another C warnining: set but not used
  staging/lustre: Fix another C compiler whine: set but not used
  staging/lustre: Nuke an unsigned >= 0 assert
  staging/lustre: Nuke another unsigned >= 0 assert

 drivers/staging/lustre/lustre/fid/lproc_fid.c      |  1 +
 drivers/staging/lustre/lustre/include/lu_object.h  |  2 +-
 drivers/staging/lustre/lustre/include/lustre_cfg.h |  4 --
 drivers/staging/lustre/lustre/libcfs/module.c      | 15 ++++----
 drivers/staging/lustre/lustre/llite/rw.c           |  1 -
 drivers/staging/lustre/lustre/ptlrpc/sec_bulk.c    |  1 -
 6 files changed, 9 insertions(+), 15 deletions(-)

-- 
2.6.3

--
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/