From: Wolfram Sang <wsa@the-dreams.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jerry.Hoemann@hpe.com,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [RFC PATCH v3 1/4] watchdog: core: add mechanism to prevent removing if NOWAYOUT
Date: Wed, 5 Sep 2018 17:33:55 +0200 [thread overview]
Message-ID: <20180905153354.GA7726@kunai> (raw)
In-Reply-To: <CAMuHMdVZ_TPLFqj1fkdW6uPm_urDYHKk9Rp8hXd_9gm-0CXcuA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 455 bytes --]
> > Is the intent of the proposed changes to prevent the unload of
> > a module if it was loaded with the "nowayout" parameter?
> >
> > If so, I thought the WD "nowayout" semantic was only supposed to be in effect
> > after /dev/watchdog was opened. The proposed change looks like it makes the
> > "nowayout" semantic take effect before /dev/watchdog is opened.
>
> Thanks, that's IMHO a very valid point.
I agree, thanks for this input.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-09-05 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 7:42 [RFC PATCH v3 0/4] watchdog: prevent removing a driver if NOWAYOUT Wolfram Sang
2018-08-29 7:42 ` [RFC PATCH v3 1/4] watchdog: core: add mechanism to prevent removing " Wolfram Sang
2018-08-29 16:14 ` Guenter Roeck
2018-08-29 20:55 ` Jerry Hoemann
2018-09-05 13:54 ` Geert Uytterhoeven
2018-09-05 15:33 ` Wolfram Sang [this message]
2018-08-29 7:42 ` [RFC PATCH v3 2/4] watchdog: renesas_wdt: avoid " Wolfram Sang
2018-08-29 7:42 ` [RFC PATCH v3 3/4] watchdog: core: add module_watchdog_pci_driver() Wolfram Sang
2018-08-29 7:42 ` [RFC PATCH v3 4/4] watchdog: i6300esb: avoid removing if NOWAYOUT Wolfram Sang
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=20180905153354.GA7726@kunai \
--to=wsa@the-dreams.de \
--cc=Jerry.Hoemann@hpe.com \
--cc=geert@linux-m68k.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.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.