From: Dawson Engler <engler@csl.Stanford.EDU>
To: linux-kernel@vger.kernel.org
Subject: [QUESTION] MOD_INC/MOD_DEC: useful to check for correct usage?
Date: Wed, 4 Apr 2001 18:25:08 -0700 (PDT) [thread overview]
Message-ID: <200104050125.SAA21252@csl.Stanford.EDU> (raw)
Hi,
in the old days you couldn't call a sleeping function in a module
before doing a MOD_INC or after doing a MOD_DEC. Then some safety nets
were added that made these obsolete (in some number of places). I was
told that people had decided to potentially get rid of all safety
nets. Is this true? Is it worthwhile to have a checker for these two
rules?
next reply other threads:[~2001-04-05 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-05 1:25 Dawson Engler [this message]
2001-04-05 1:34 ` Alexander Viro
2001-04-23 22:57 ` Keith Owens
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=200104050125.SAA21252@csl.Stanford.EDU \
--to=engler@csl.stanford.edu \
--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
all inboxes | Powered by JetHome®