On Mon, Aug 25, 2014 at 10:39:59PM -0500, Vladimir Támara Patiño wrote:
Using tcpdump in a firewall with 5.5 (also happens with 5.4 and I guess with
current) and certain addres of the LAN I got always a segfault.
It is a bug within the function gethostbyaddr. It can be reproduced with
the
Op Wed, 27 Aug 2014 20:50:34 +0200 schreef Miod Vallat m...@online.fr:
Why not keep the softdep flag when updating rw-ro?
E.g. via mount -ur /usr/obj
fstab(5) already allows ro+softdep.
Because if we were to apply this diff, there would be no way to switch
from rw+softdep to rw.
That was
Because if we were to apply this diff, there would be no way to switch
from rw+softdep to rw.
That was already broken; rw-rw is not affected as per the enclosing
if-block.
Which is why the current way to remove softdep from a filesystem is a
rw+softdep - ro - rw transition, which would no
Op Thu, 28 Aug 2014 11:51:32 +0200 schreef Miod Vallat m...@online.fr:
Because if we were to apply this diff, there would be no way to switch
from rw+softdep to rw.
That was already broken; rw-rw is not affected as per the enclosing
if-block.
Which is why the current way to remove softdep
On 28 Aug 2014, at 3:02 am, Mike Belopuhov m...@belopuhov.com wrote:
On 27 August 2014 08:25, Brad Smith b...@comstyle.com wrote:
Looking for some testing of the following diff to add Jumbo support for the
BCM5714 / BCM5780 and BCM5717 / BCM5719 / BCM5720 / BCM57765 / BCM57766
chipsets.
Until we start to worry about Y2K1, does it really matter what the
NVRAM_CENTURY byte says?
--- /usr/src/sys/arch/i386/isa/clock.c.orig Mon May 6 02:15:11 2013
+++ /usr/src/sys/arch/i386/isa/clock.c Wed Aug 27 19:02:46 2014
@@ -502,85 +502,6 @@
static int timeset;
/*
- * check
On 28 August 2014 12:32, David Gwynne da...@gwynne.id.au wrote:
On 28 Aug 2014, at 3:02 am, Mike Belopuhov m...@belopuhov.com wrote:
On 27 August 2014 08:25, Brad Smith b...@comstyle.com wrote:
Looking for some testing of the following diff to add Jumbo support for the
BCM5714 / BCM5780 and
sysmerge hangs while fetching the SHA256.sig file when working with local sets,
ie.:
#export SM_PATH=/nas2/public/OpenBSD/snapshots/amd64
#cd $SM_PATH
#ls -l SHA256.sig xetc56.tgz
-rw-r--r-- 1 rd rd 1977 Aug 26 23:39 SHA256.sig
-rw-r--r-- 1 rd rd 69066 Aug 6 16:10 xetc56.tgz
#sysmerge -bd
The issue is the change in ld.so/library_subr.c rev 1.34. If you back that
change out, the crash disappears.
The problem is that no one makes changes to the linkages inside ld.so out
of boredom: there was some previous program that crashed without that
change, but the details weren't
Which is why the current way to remove softdep from a filesystem is a
rw+softdep - ro - rw transition, which would no longer work with your
diff.
It would work, but you'd have to explicitly disable softdep, as one might
expect to be required when removing softdep:
Oh, indeed.
Then it's a
Hi,
while debugging some problems on a virtio host that supports only few dma
segments per request, I noticed that the minphys function is not called in
all code paths. It is only used for physio but not for other (cached) disk
operations. An example trace is below.
Am I missing something or
On Thu, Aug 28, 2014 at 06:27:48PM +, Miod Vallat wrote:
| Which is why the current way to remove softdep from a filesystem is a
| rw+softdep - ro - rw transition, which would no longer work with your
| diff.
|
| It would work, but you'd have to explicitly disable softdep, as one might
|
On 08/28/14 23:06, Paul de Weerd wrote:
On Thu, Aug 28, 2014 at 06:27:48PM +, Miod Vallat wrote:
| Which is why the current way to remove softdep from a filesystem is a
| rw+softdep - ro - rw transition, which would no longer work with your
| diff.
|
| It would work, but you'd have to
On 28 Aug 2014, at 11:05 pm, Mike Belopuhov m...@belopuhov.com wrote:
On 28 August 2014 12:32, David Gwynne da...@gwynne.id.au wrote:
On 28 Aug 2014, at 3:02 am, Mike Belopuhov m...@belopuhov.com wrote:
On 27 August 2014 08:25, Brad Smith b...@comstyle.com wrote:
Looking for some testing
are you expecting minphys to appear in that backtrace?
On 29 Aug 2014, at 5:07, Stefan Fritsch s...@sfritsch.de wrote:
Hi,
while debugging some problems on a virtio host that supports only few dma
segments per request, I noticed that the minphys function is not called in
all code paths.
disklabel is not required for mount_mfs
Index: newfs.8
===
RCS file: /cvs/src/sbin/newfs/newfs.8,v
retrieving revision 1.70
diff -u -p -r1.70 newfs.8
--- newfs.8 23 May 2011 10:56:17 - 1.70
+++ newfs.8 29 Aug 2014
On Friday 29 August 2014 10:34:20, David Gwynne wrote:
are you expecting minphys to appear in that backtrace?
No. In that trace minphys should have limited the transfer size and I
had put an KASSERT() into vioblk_scsi_cmd() which verified that xs-
datalen is not larger than that limit. A call
17 matches
Mail list logo
