linux-kernel - Re: [PATCH] staging: lustre: remove IOC_LIBCFS_PING

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>] [day] [month] [year] [list]

Message-ID: <20151107032747.GA14108@kroah.com>
Date:	Fri, 6 Nov 2015 19:27:47 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	y@....ornl.gov
Cc:	devel@...verdev.osuosl.org, Oleg Drokin <oleg.drokin@...el.com>,
	Andreas Dilger <andreas.dilger@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	lustre-devel@...ts.lustre.org, James Simmons <uja.ornl@...oo.com>,
	James Simmons <jsimmons@...radead.org>
Subject: Re: [PATCH] staging: lustre: remove IOC_LIBCFS_PING_TEST ioctl

On Fri, Nov 06, 2015 at 09:08:03PM -0500, y@....ornl.gov wrote:
> From: James Simmons <uja.ornl@...oo.com>
> 
> The ioctl IOC_LIBCFS_PING_TEST has not been used in
> ages. The recent nidstring changes which moved all
> the nidstring operations from libcfs to the LNet
> layer but this ioctl code was still using an
> nidstring operation that was causing an circular
> dependency loop between libcfs and LNet.
> 
> Signed-off-by: James Simmons <jsimmons@...radead.org>
> ---
>  .../lustre/include/linux/libcfs/libcfs_ioctl.h     |    1 -
>  drivers/staging/lustre/lustre/libcfs/module.c      |   17 -----------------
>  2 files changed, 0 insertions(+), 18 deletions(-)

You sent me 2 copies of this, which am I supposed to apply?  I've
dropped both, please resend the correct one.

thanks,

greg k-h
--
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/