From: Manfred Spraul <manfred@colorfullife.com>
To: Joe Perches <joe@perches.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Davidlohr Bueso <davidlohr.bueso@hp.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
1vier1@web.de
Subject: Re: [PATCH 7/6] ipc/sem.c: add a printk_once for semctl(GETNCNT/GETZCNT)
Date: Sun, 25 May 2014 21:41:59 +0200 [thread overview]
Message-ID: <53824787.4030905@colorfullife.com> (raw)
In-Reply-To: <1401043188.22191.16.camel@joe-AO725>
Hi Joe,
On 05/25/2014 08:39 PM, Joe Perches wrote:
> On Sun, 2014-05-25 at 20:21 +0200, Manfred Spraul wrote:
> + */
> + printk_once(KERN_INFO "semctl(GETNCNT/GETZCNT) is since 3.16 Single " \
> + "Unix Specification compliant.\n" \
> + "The task %d triggered the difference, " \
> + "watch for misbehavior.", current->pid);
> Unnecessary line continuations.
> Missing terminating newline after "misbehavior"
> Ideally coalesced or broken at linebreaks like:
>
> pr_info_once("semctl(GETNCNT/GETZCNT) is Single Unix Specification compliant since kernel v3.16\n"
> "Task %d triggered the difference, watch for misbehavior\n",
> current->pid);
Thanks. I'll try to remember to really run checkpatch instead of
assuming what it might report.
>> if (sop->sem_num != semnum)
>> return 0;
>>
> Should the printk_once (which could be pr_info_once or _ratelimited
> or maybe even emitted at KERN_DEBUG) be done only when
> the return is 1?
>
To fully check if there is a difference would mean that the old code and
the new code run in parallel.
The code might trigger slightly too often, but since there are zero
known users of GETZCNT / GETNCNT simplicity wins.
--
Manfred
next prev parent reply other threads:[~2014-05-25 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 18:21 [PATCH 7/6] ipc/sem.c: add a printk_once for semctl(GETNCNT/GETZCNT) Manfred Spraul
2014-05-25 18:39 ` Joe Perches
2014-05-25 19:41 ` Manfred Spraul [this message]
2014-05-26 15:48 ` Davidlohr Bueso
-- strict thread matches above, loose matches on Subject: below --
2014-05-25 19:43 Manfred Spraul
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=53824787.4030905@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=1vier1@web.de \
--cc=akpm@linux-foundation.org \
--cc=davidlohr.bueso@hp.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.