Hi,
Sometimes I see systems hanging in ddb(4) after panic(9) and the "boot reboot"
command doesn't work anymore, i.e. of filesystem or locking issues.
Bluhm@ suggested to me to use "call cpu_reset" in such situations.
I would like to introduce a command 'boot reset' to do this.
ok?
friehm
In
I've included different minor patches below as one patch. I haven't split into
separate patches since the changes are not complex and easy to audit.
Here's what it does:
Almost all functions in fuse.c do not check if the arguments are null. This
patch adds null checks where appropriate.
Some
On Thu, Oct 26, 2017 at 10:42:17AM +0200, Florian Riehm wrote:
> Hi,
>
> Sometimes I see systems hanging in ddb(4) after panic(9) and the "boot reboot"
> command doesn't work anymore, i.e. of filesystem or locking issues.
> Bluhm@ suggested to me to use "call cpu_reset" in such situations.
>
> I
On Wed, Oct 25, 2017 at 03:41:31PM +0200, Martin Pieuchot wrote:
> On 25/10/17(Wed) 15:37, Martin Pieuchot wrote:
> > Diff below moves the common code to add/remove multicast filters
> > to ieee80211_ioctl(9). Wireless drivers that do things slightly
> > differently are left untouched for the mome
On Wed, Oct 25, 2017 at 12:20:45PM +0200, Martin Pieuchot wrote:
> Diff below remove some more deprecated ioctl(2). The first group below
> correspond to features now deprecated by slaacd(8):
>
> SIOCSIFINFO_FLAGS, SIOCSNDFLUSH_IN6, SIOCSPFXFLUSH_IN6, SIOCSRTRFLUSH_IN6
>
> Removing those might
On 2017/10/26 10:42, Florian Riehm wrote:
> Hi,
>
> Sometimes I see systems hanging in ddb(4) after panic(9) and the "boot reboot"
> command doesn't work anymore, i.e. of filesystem or locking issues.
> Bluhm@ suggested to me to use "call cpu_reset" in such situations.
>
> I would like to introdu
On Thu, Oct 26, 2017 at 08:08:35PM +1100, Jonathan Gray wrote:
> No, cpu_reset() is MD this will break ddb on all non x86 archs besides
> landisk.
Would it make sense to implement a boot(RB_RESET) that works
everywhere?
Problem is that when adding MP locks to the kernel, ddb boot reboot
does not
On Thu, Oct 26, 2017 at 01:12:53PM +0200, Alexander Bluhm wrote:
> On Thu, Oct 26, 2017 at 08:08:35PM +1100, Jonathan Gray wrote:
> > No, cpu_reset() is MD this will break ddb on all non x86 archs besides
> > landisk.
>
> Would it make sense to implement a boot(RB_RESET) that works
> everywhere?
>
On Thu, Oct 26, 2017 at 10:32:42PM +1100, Jonathan Gray wrote:
> What specifically? Skip if_downall() if rebooting from ddb?
> That could perhaps even be done for RB_NOSYNC.
I thought of someting like a big hammer. Skip everything except
the final call in boot() that causes the machine to reset.
> Date: Thu, 26 Oct 2017 15:51:28 +1100
> From: Jonathan Gray
>
> Also add aliases for additional eabi calls clang emits.
I'm not certain the aliases are correct. So please hold off on that
for now.
The makefile changes more or less match what I had in my tree, but
your versions is better. Pl
> Date: Thu, 26 Oct 2017 15:15:34 +0200 (CEST)
> From: Mark Kettenis
>
> > Date: Thu, 26 Oct 2017 15:51:28 +1100
> > From: Jonathan Gray
> >
> > Also add aliases for additional eabi calls clang emits.
>
> I'm not certain the aliases are correct. So please hold off on that
> for now.
Seems ou
Similar to what we do on other architectures with .eh_frame. Reduces
the growth when compiling kernels with clang.
Index: arch/arm/conf/ldscript.tail
===
RCS file: /cvs/src/sys/arch/arm/conf/ldscript.tail,v
retrieving revision 1.4
di
I'm ready whenever you guys are. I have sets ready.
This is a better plan. All the architectures can adapt to this,
even those that have a tricky ROM-related dance.
> On Thu, Oct 26, 2017 at 10:32:42PM +1100, Jonathan Gray wrote:
> > What specifically? Skip if_downall() if rebooting from ddb?
> > That could perhaps even be done for RB_NOSYNC.
>
ok
2017-10-19 15:40 GMT+02:00 Patrick Wildt :
> Hi,
>
> so far, even if we look for our own cert, we only match the id against
> the first subjectAltName. This means we cannot use certificates where
> we actually need a different one. This diff changes the behaviour so
> that we check all subjec
ok
2017-10-24 16:25 GMT+02:00 Patrick Wildt :
> Hi,
>
> in the final RFC 5903 the computation for the DH shared secret changed.
> Instead of the full point, only the X point is included. Unfortunately
> this is a backwards incompatible change, so older ikeds won't be com-
> patible with this chan
Hi all,
First off, as always, I apologize if I'm wasting anyone's time because
I'm missing something obvious here.
So, I accidentally ran "ifconfig iwm0 mode 11g" as a regular user and
noticed it didn't throw an error. A quick look at the code and it seems
like the error was left out intentional
* Require interface name to be defined for switches in vm.conf
** Requires user to create bridge(4) beforehand
* Remove code to create bridges on the fly
* Add code to ensure bridge really exists
* Update manpage switch and example sections
diff --git usr.sbin/vmd/parse.y usr.sbin/vmd/parse.y
inde
This patch set changes the behavior of switches in vm.conf
by requiring an interface name to be defined (previously,
it was optional).
This change also removes the responsibility of creating the underlying
bridge from vmd to the user (i.e. doas ifconfig bridge0 create).
These changes allow vmctl
* Update regress tests for new requirement (interface name on switches)
* Add new test for interface name on switch
diff --git regress/usr.sbin/vmd/config/Makefile
regress/usr.sbin/vmd/config/Makefile
index 16a43066415..68b5c13323a 100644
--- regress/usr.sbin/vmd/config/Makefile
+++ regress/usr.s
libressl-2.6.2 is susceptible to an out-of-bounds read:
#include
int main(void) {
char salt[3] = {0xf8, 0xd0, 0x00};
char out[32];
DES_fcrypt("foo", salt, out);
}
Place in libressl's fcrypt.c:
x=ret[0]=((salt[0] == '\0')?'A':salt[0]);
Eswap0=con_salt[x]<<
On 26/10/17(Thu) 16:23, Carlos Cardenas wrote:
> * Require interface name to be defined for switches in vm.conf
> ** Requires user to create bridge(4) beforehand
> * Remove code to create bridges on the fly
> * Add code to ensure bridge really exists
> * Update manpage switch and example sections
On Fri, Oct 27, 2017 at 08:23:05AM +0200, Martin Pieuchot wrote:
> On 26/10/17(Thu) 16:23, Carlos Cardenas wrote:
> > * Require interface name to be defined for switches in vm.conf
> > ** Requires user to create bridge(4) beforehand
> > * Remove code to create bridges on the fly
> > * Add code to e
23 matches
Mail list logo
