[prev in list] [next in list] [prev in thread] [next in thread]
List: busybox
Subject: Re: Reboot implemention
From: Michael Conrad <mconrad () intellitree ! com>
Date: 2017-11-15 15:08:40
Message-ID: a4f70efb-1956-c2c5-a722-30cab67f8491 () intellitree ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On 11/13/2017 8:19 PM, Cathey, Jim wrote:
>
> >Is there a reason why BusyBox's [reboot] implementation is different,
> or is it a bug?
>
> The final fs cleanup, and the only one that really counts, is what the
> kernel does after init(8) exits.
>
Pretty sure if init exits it is an immediate PANIC, which is not how
most systems reboot. I think it all ends with the reboot syscall. I'm
not sure what the semantics are for that syscall, but it would seem that
sync() would be wise to execute first. Unless it's implied by reboot().
-Mike
[Attachment #5 (text/html)]
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/13/2017 8:19 PM, Cathey, Jim
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CY4PR04MB0425449685C9B2782FD56AE3BD280@CY4PR04MB0425.namprd04.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Times New Roman",serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal" style="margin-bottom:12.0pt">>Is there a
reason why BusyBox's [reboot] implementation is different, or
is it a bug?<o:p></o:p></p>
<p class="MsoNormal"><span
style="font-family:"Calibri",serif">The final fs
cleanup, and the only one that really counts, is what the
kernel does after init(8) exits.<o:p></o:p></span></p>
</div>
</blockquote>
<br>
Pretty sure if init exits it is an immediate PANIC, which is not how
most systems reboot. I think it all ends with the reboot syscall.
I'm not sure what the semantics are for that syscall, but it would
seem that sync() would be wise to execute first. Unless it's
implied by reboot().<br>
<br>
-Mike<br>
</body>
</html>
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic