All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Baruch Siach <baruch@tkos.co.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] delay.h: add __must_check to msleep_interruptible
Date: Fri, 17 Dec 2010 15:49:47 -0800	[thread overview]
Message-ID: <20101217154947.3e95488c.akpm@linux-foundation.org> (raw)
In-Reply-To: <aed7ab07576c307653723b9bea04516879b3a3ed.1288860894.git.baruch@tkos.co.il>

On Thu,  4 Nov 2010 10:55:41 +0200
Baruch Siach <baruch@tkos.co.il> wrote:

> Code calling msleep_interruptible() must be aware that sleep time might be
> shorter than intended as a result of a signal being caught. Code not checking
> the return value of msleep_interruptible() is probably buggy, unless it's doing
> the signal_pending() check itself, which is redundant.
> 

True.  But there are around 250 callsites which don't check the
msleep_interruptible() return value.

I don't think I want to add 250 new warnings to the kernel build -
it'll take *years* to get them all weeded out and meanwhile it will
cause people to miss other warnings while they're ignoring the
msleep_interruptible() warnings.

So.  Some lucky duck needs to get down and start fixing all these
things first, please.  Meanwhile, a checkpatch rule which prevents new
occurrences would be good.

Except lots of developers and maintainers can't be assed running
checkpatch, so a volunteer who regularly runs linux-next.patch and
patch-2.6.Y-rcY through checkpatch and then hassles people would also be
good.


  parent reply	other threads:[~2010-12-17 23:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04  8:55 [PATCH] delay.h: add __must_check to msleep_interruptible Baruch Siach
2010-12-16  6:17 ` Baruch Siach
2010-12-16  8:20   ` Andrew Morton
2010-12-17 23:49 ` Andrew Morton [this message]
2010-12-17 23:55   ` Andrew Morton

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=20101217154947.3e95488c.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=baruch@tkos.co.il \
    --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 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.