Op 13-02-18 om 14:44 schreef Denys Vlasenko:
> Fixed in git, thanks.
As already signaled on the dash list, this introduces a new bug:
$ ./ash -c 'foo=a; echo "<${foo#[a\]]}>"'
Expected output: <>
- M.
___
busybox mailing list
busybox@busybox.net
On 11/24/2017 9:09 PM, Deb McLemore wrote:
+ while (1) {
+ fdrc = connect(fdBB2,
+ (struct sockaddr *)_addr2,
+ sizeof(sa_family_t) +
+
On 2/14/2018 12:53 PM, Deb McLemore wrote:
The only reproduction we were able to perform injected via a BMC soft poweroff
being triggered.
This then called into kernel/reboot.c (orderly_poweroff where the schedule_work
was performed) utilizing the
usermodehelper during the run_cmd
The only reproduction we were able to perform injected via a BMC soft poweroff
being triggered.
This then called into kernel/reboot.c (orderly_poweroff where the schedule_work
was performed) utilizing the
usermodehelper during the run_cmd /sbin/poweroff.
On 02/14/2018 09:44 AM, Laurent
On Wed, Feb 14, 2018 at 4:44 PM, Laurent Bercot
wrote:
>> When PID=0 in early kernel_init, PID=1 has a skeleton running, this
>> detection is not
>>
>> the Busybox /sbin/init, but a place holder for when the real Busybox
>> /sbin/init is do_execve'd
>
>
> Are you saying
When PID=0 in early kernel_init, PID=1 has a skeleton running, this
detection is not
the Busybox /sbin/init, but a place holder for when the real Busybox
/sbin/init is do_execve'd
Are you saying the kernel could spawn a /sbin/reboot process *before*
kernel_init execs into the userspace
On Wed, Feb 14, 2018 at 2:49 PM, Deb McLemore wrote:
> When PID=0 in early kernel_init, PID=1 has a skeleton running, this detection
> is not
>
> the Busybox /sbin/init, but a place holder for when the real Busybox
> /sbin/init is do_execve'd
>
> and then the kernel
When PID=0 in early kernel_init, PID=1 has a skeleton running, this detection
is not
the Busybox /sbin/init, but a place holder for when the real Busybox /sbin/init
is do_execve'd
and then the kernel flushes all the old process table information on the place
holder of PID=1,
then the real
Attaching an interface to a VRF is done by setting the interface's
master. Besides VRF, this can also be used for bridges.
function old new delta
set_master - 180+180
do_iplink
VRF interfaces have a mandatory table parameter, which needs to be
specified using a RTNL attribute.
function old new delta
do_add_or_delete12281340+112
.rodata
On Wed, Feb 14, 2018 at 4:29 AM, Deb McLemore wrote:
> On 02/13/2018 08:32 PM, Laurent Bercot wrote:
>>> Even when process=1 is started, it still leaves a window when the
>>> signal handler setup has not been completed.
>>
>> Yes, but you can still use kill(pid, 0) to
Greetings Denys,
> On Mon, Feb 12, 2018 at 4:38 PM, daggs wrote:
> > Greetings Denys,
> >
> > here is another test case that goes bad"
> > cat -n test.sh
> > 1 #!/bin/bash
> > 2
> > 3 echo "E${LINENO}"
> > 4 echo "$(readlink -f /proc/self/fd/2)" >
12 matches
Mail list logo