From: Ruben Safir <ruben@mrbrklyn.com>
To: kernelnewbies@kernelnewbies.org
Subject: Re: Try/catch for modules?
Date: Fri, 18 Oct 2019 14:52:29 -0400 [thread overview]
Message-ID: <08bffca3-462b-b754-07ba-98eb3c14f0b2@mrbrklyn.com> (raw)
In-Reply-To: <CAN19L9GO-e=CpBffAkR2jXj6Nb7M1py36ZSZ25cyJna1dmprpg@mail.gmail.com>
On 10/18/19 1:05 PM, Martin Galvan wrote:
> El vie., 18 oct. 2019 a las 14:02, Ruben Safir (<ruben@mrbrklyn.com>) escribió:
>> I don't think you really understand what is going on here. On the
>> kernel level you would never wrap up a process in another process in
>> order to catch a mistake, and then do error correction. That method of
>> programming is not appropriate for kernel level code where you are
>> running everything on the hardware.
>>
>> You can test for a condition before you run the code, and use GOTO if
>> you want, but you are not doing a Java like Catch and Throw.
>
> I'm not talking about running managed code in the kernel. I'm talking
> about whether there is a more general version of something like
> _ASM_EXTABLE, or maybe even doing something like what Windows does
> with its __try/__except machinery which uses stack unwinding
> information.
>
> From the responses here it's clear that there's no such thing in the
> kernel, at least that you guys know about. Thanks.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
https://code.woboq.org/linux/linux/arch/x86/include/asm/uaccess.h.html
it is for user space coding...
--
So many immigrant groups have swept through our town
that Brooklyn, like Atlantis, reaches mythological
proportions in the mind of the world - RI Safir 1998
http://www.mrbrklyn.com
DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002
http://www.nylxs.com - Leadership Development in Free Software
http://www.brooklyn-living.com
Being so tracked is for FARM ANIMALS and extermination camps,
but incompatible with living as a free human being. -RI Safir 2013
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-10-18 18:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 13:37 Try/catch for modules? Martin Galvan
[not found] ` <CAG=DERmX7AU8YkEAYnPLfPKCLD=1OugmD95R9wZ3CepXvqzd2Q@mail.gmail.com>
2019-10-17 13:42 ` Maria Neptune
2019-10-17 13:51 ` Ruben Safir
2019-10-17 22:12 ` Valdis Klētnieks
2019-10-18 15:43 ` Martin Galvan
2019-10-18 15:47 ` Anuz Pratap Singh Tomar
2019-10-18 15:48 ` Maria Neptune
2019-10-18 16:04 ` Bernd Petrovitsch
2019-10-18 16:11 ` Martin Galvan
2019-10-18 16:18 ` Bernd Petrovitsch
2019-10-18 17:02 ` Ruben Safir
2019-10-18 17:05 ` Martin Galvan
2019-10-18 18:52 ` Ruben Safir [this message]
2019-10-18 18:53 ` Ruben Safir
2019-10-18 19:08 ` Ruben Safir
2019-10-18 21:53 ` Valdis Klētnieks
2019-10-18 22:09 ` Martin Galvan
2019-10-18 22:28 ` Greg KH
2019-10-18 18:48 ` Ruben Safir
2019-10-18 21:24 ` Rik van Riel
2019-10-18 21:32 ` Ruben Safir
2019-10-18 21:37 ` Ruben Safir
2019-10-18 22:59 ` Valdis Klētnieks
2019-10-19 7:46 ` Bjørn Mork
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=08bffca3-462b-b754-07ba-98eb3c14f0b2@mrbrklyn.com \
--to=ruben@mrbrklyn.com \
--cc=kernelnewbies@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).