linux-kernel - Re: [PATCH] staging/lustre: Replace jobid acquiring with per node setting

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

Message-Id: <AD08F6C5-1BAD-455B-9A09-1FFB8D2CA42E@linuxhacker.ru>
Date:	Sat, 3 May 2014 21:20:06 -0400
From:	Oleg Drokin <green@...uxhacker.ru>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org, devel@...verdev.osuosl.org,
	Andreas Dilger <andreas.dilger@...el.com>
Subject: Re: [PATCH] staging/lustre: Replace jobid acquiring with per node setting


On May 3, 2014, at 7:29 PM, Greg Kroah-Hartman wrote:

> On Sun, Apr 27, 2014 at 10:21:52PM -0400, Oleg Drokin wrote:
>> Insted of meddling directly in process environment variables
>> (which is also not possible on certain platforms due to not exported
>> symbols), create jobid_name proc file to represent this info
>> (to be filled by job scheduler epilogue).
> That looks better, but what are you going to do about getting rid of all
> of these proc files?  Just move them all at once?  I really don't like
> the idea of adding new ones, and want a plan for what you all are going
> to do here moving forward.

What proc files are to referring to, if I may ask?
I don't think I saw complaints about proc files, the complaints I saw were mostly about
reading env variables directly and the like so that was the focus of this patch.
Did I miss some side discussion? Any pointers?

Thanks!

Bye,
    Oleg--
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/