kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: kristof@sigsegv.be (Kristof Provost)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Semaphore
Date: Wed, 22 Feb 2012 10:48:44 +0100	[thread overview]
Message-ID: <20120222094844.GK10865@thebe.jupiter.sigsegv.be> (raw)
In-Reply-To: <CADxo8W+95kHhQ0ciXY6mxY+6Fqx-cmiPQLiBRR82QhfnU9oeSw@mail.gmail.com>

On 2012-02-22 11:01:52 (+0200), Konstantin Zertsekel <zertsekel@gmail.com> wrote:
> On Tue, Feb 21, 2012 at 6:14 PM, Dave Hylands <dhylands@gmail.com> wrote:
> > I'm assuming that the semaphore is one which is held across multiple
> > calls into the kernel, otherwise you don't have an issue in the first
> > place, unless there is a bug on the kernel side of things which
> > actually caused the process to terminate.
> 
> Ok, but what happens if things go wrong?
> For example, it driver exists abnormally (segmentation fault or something)?
> Anyway, it seems very strange that the responsibility is of a driver alone!
> There is the *kernel* in the system to take care of abnormal
> situation, not the exit function of a driver...
> 
The driver is part of the kernel. If it dies the whole kernel can
(perhaps even should) die.

There are systems, like Minix, where drivers don't run in kernel mode
and where a crashing driver won't take the system down.
There are advantages and disadvantages to that approach.
See http://en.wikipedia.org/wiki/Microkernel

Kristof

  reply	other threads:[~2012-02-22  9:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-21 13:47 Semaphore SaNtosh kuLkarni
2012-02-21 15:12 ` Semaphore Konstantin Zertsekel
2012-02-21 16:14 ` Semaphore Dave Hylands
2012-02-22  9:01   ` Semaphore Konstantin Zertsekel
2012-02-22  9:48     ` Kristof Provost [this message]
2012-02-22 11:53       ` Semaphore Anuz Pratap Singh Tomar
2012-02-22 12:11         ` Semaphore Kristof Provost
2012-02-22 14:31           ` Semaphore Sri Ram Vemulpali
2012-02-23  6:12             ` Semaphore SaNtosh kuLkarni
2012-02-24  7:07               ` Semaphore Kosta Zertsekel
2012-02-24  9:04                 ` Semaphore Kristof Provost
2012-02-24  9:25                   ` Semaphore Kosta Zertsekel
2012-02-24  9:28                     ` Semaphore Kristof Provost
2012-02-24 10:15                       ` Semaphore Kosta Zertsekel
2012-02-24 10:24                         ` Semaphore Kristof Provost
2012-02-28  8:23                           ` Semaphore Rajath N R
2012-02-28  8:33                             ` Semaphore Rajath N R

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=20120222094844.GK10865@thebe.jupiter.sigsegv.be \
    --to=kristof@sigsegv.be \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).