From: Vasiliy Kulikov <segoon@openwall.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Alexey Dobriyan <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] proc: remove superfluous debug output
Date: Thu, 8 Dec 2011 23:20:14 +0400 [thread overview]
Message-ID: <20111208192014.GA9794@albatros> (raw)
In-Reply-To: <20111206164840.b634b1d1.akpm@linux-foundation.org>
On Tue, Dec 06, 2011 at 16:48 -0800, Andrew Morton wrote:
> > - pr_debug("proc: options = %s\n", options);
> > -
> > if (!options)
> > return 1;
>
> So it turns out that this patch is a fix against the pending
> procfs-add-hidepid=-and-gid=-mount-options.patch. Please tell people
> this sort of thing to prevent confusion.
Oops, sorry. Will do this next time.
> Also, I have a note here that Alexey has issues with
> procfs-add-hidepid=-and-gid=-mount-options.patch (it is reproduced
> below) - he suggests that it is using incorrect types. Where do we
> stand with that?
This is not a bug, surely. IMHO, it's better to have it as the longest
possible format for the future changes. It's wearily to find such %d
for pid_t instances all over the kernel if we change pid_t from int to
long.
The same question, btw:
http://www.spinics.net/lists/kernel/msg1270730.html
Probably it's better to add official point about this issue into
Documentation/ ?
Thanks,
--
Vasiliy Kulikov
http://www.openwall.com - bringing security into open computing environments
prev parent reply other threads:[~2011-12-08 19:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201111220034.pAM0YHCC015781@wpaz9.hot.corp.google.com>
[not found] ` <20111125152601.GA2783@p183.telecom.by>
2011-12-05 11:35 ` [PATCH] proc: remove superfluous debug output Vasiliy Kulikov
2011-12-07 0:48 ` Andrew Morton
2011-12-08 19:20 ` Vasiliy Kulikov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111208192014.GA9794@albatros \
--to=segoon@openwall.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox