local-user DoS because of the hard limit
values.
David
--
David Laight: da...@l8s.co.uk
by dlopen().
So __uselibcstub will get set to zero.
I also suspect thatthe pthread__errorfunc() calls rely on
pthread__diagnostic betin set - by pthread__init().
I think pthread_init() needs to be looking at some value that
libc set before calling main.
David
--
David Laight: da
to do
to get .ORDER working.
David
--
David Laight: da...@l8s.co.uk
characters be valid.
(Otherwise scripts become non-portable.)
OTOH (unsigned)(ch - '0') = 9 is probably the fastest isdigit()
on any modern cpu.
David
--
David Laight: da...@l8s.co.uk
in the kernel?
Since user pointers will be 64bit and kernel ones only 32.
David
--
David Laight: da...@l8s.co.uk
?
Make finds it much harder to parse empty().
David
--
David Laight: da...@l8s.co.uk
of the register area on the second pass is going to
lead to corrupt core files.
David
--
David Laight: da...@l8s.co.uk
into an x86
system the 'd' partition could be made available as wd0c!
David
--
David Laight: da...@l8s.co.uk
??
David
--
David Laight: da...@l8s.co.uk
--
David Laight: da...@l8s.co.uk
.
David
--
David Laight: da...@l8s.co.uk
to linux/types.h.
As far as I'm aware, these aliases are correct, and the type doesn't
actually have any effect on the byte order of reads and writes.
Correct - they are for the static analysis tools.
David
--
David Laight: da...@l8s.co.uk
variable in intel_panel.c.
Possibly adding a #define for max/min before/after including the
netbsd header that defines these as a function/define would solve
this in the wrapper headers?
David
--
David Laight: da...@l8s.co.uk
problem it makes them much, much, much
easier to read.
I remember changing some of the source files to split the strings.
David
--
David Laight: da...@l8s.co.uk
on the command line, exceptionally difficult to determine what
it did.
David
--
David Laight: da...@l8s.co.uk
for them?
I presume it would have to be USB2 mode??
I've access to an adapter.
David
--
David Laight: da...@l8s.co.uk
a separate
cache-line for the rwlock's reader counter.
You'd be much better off ordering the fields to avoid ping-pong
of data.
IIRC one of the new (big) ppc has 256 byte cache lines.
Cache line aligning data is then getting silly.
David
--
David Laight: da...@l8s.co.uk
inlined then the generated code will be
extremely horrid.
The 'always inline' was there for a reason.
David
--
David Laight: da...@l8s.co.uk
On Sat, Oct 19, 2013 at 01:19:03AM +, John Nemeth wrote:
Module Name: src
Committed By: jnemeth
Date: Sat Oct 19 01:19:03 UTC 2013
Modified Files:
src/sbin/gpt: gpt.8
Log Message:
type fix: accommodate. - accomodate.
Why? The correct spelling has two 'm's
At least in
an R_386_32 instead
of an R_386_16 relocation, which is truncated to fit. XXX: untested.
Broken - it would have to be moved to before the call to prot_to_real.
David
--
David Laight: da...@l8s.co.uk
On Sun, Oct 20, 2013 at 07:49:55PM +0100, David Laight wrote:
On Sat, Oct 19, 2013 at 08:16:16PM -0400, Christos Zoulas wrote:
Module Name:src
Committed By: christos
Date: Sun Oct 20 00:16:16 UTC 2013
Modified Files:
src/sys/arch/i386/stand/pxeboot
.
Does not expanding tabs actually make sense?
At a guess it would lead to tab characters being send to the terminal
and the display getting f**cked up.
I also suspect it will break applications that expect curses to
expand tabs.
David
--
David Laight: da...@l8s.co.uk
adapter.
The multicast filter doesn't appear to work, so put the chip in promisc
mode so that IPv6 NDP works.
Does it have a 'promiscuous for multicasts' option?
Possibly just setting all 1's in the filter will work.
David
--
David Laight: da...@l8s.co.uk
(and other be systems) it requires renaming of the symbol itself.
I presume such a rename was done when time_t was extended to 64bits?
David
--
David Laight: da...@l8s.co.uk
it).
David
--
David Laight: da...@l8s.co.uk
--
David Laight: da...@l8s.co.uk
) { \
reference_memory(s, 8); \
*(uint64_t *)(d) = *(uint64_t *)(s); \
reference_memory(d, 8); \
} else \
__memcpy(d, s, len) \
But my gnu asm is a bit weak!
David
--
David Laight: da...@l8s.co.uk
going to race with open or close though.
Disallowing unload completely would be a pain when developing drivers.
David
--
David Laight: da...@l8s.co.uk
on a single cpu system.
It isn't there on amd64, but really it does no harm.
Without it one process will have an indererminate fp state.
I can't say I've actuallly looked a xen.
Presumably we somewhere compile the hypervisor as part of a kernel?
David
--
David Laight: da...@l8s.co.uk
currently aren't, but
hopefully it is in the works.
Probably best to make fpuinit() xen-save then.
David
--
David Laight: da...@l8s.co.uk
On Sun, Feb 02, 2014 at 01:27:45PM +0100, Manuel Bouyer wrote:
On Sat, Feb 01, 2014 at 10:49:44PM +, David Laight wrote:
On Sat, Feb 01, 2014 at 08:07:07PM +, Manuel Bouyer wrote:
Module Name: src
Committed By: bouyer
Date: Sat Feb 1 20:07:07 UTC 2014
On Sun, Feb 02, 2014 at 08:41:29PM +0100, Manuel Bouyer wrote:
On Sun, Feb 02, 2014 at 06:53:55PM +, David Laight wrote:
Something needs to set the TS (task switched) flag when a new cpu
is added. Both amd64 and i386 'bare metal' have direct calls to
fpuinit() to do this.
If TS
, (PTRACE_TYPE_ARG3)1, sig);
You probably want to kill the comment from the last merge.
David
--
David Laight: da...@l8s.co.uk
On Wed, Feb 05, 2014 at 11:09:05PM +0100, Joerg Sonnenberger wrote:
On Wed, Feb 05, 2014 at 06:52:22PM +, David Laight wrote:
Module Name:src
Committed By: dsl
Date: Wed Feb 5 18:52:22 UTC 2014
Modified Files:
src/sys/arch/amd64/conf
= no-avx = no-fma = no-fma4
You either need all of them, and the one that the next sub-version
of the cpu/compiler add, or you assume that the first ones imply the
latter - at least to some degree.
David
--
David Laight: da...@l8s.co.uk
On Thu, Feb 13, 2014 at 08:22:32AM +0100, Christoph Egger wrote:
+ENTRY(fngetsw)
+ fnstsw %ax
+ ret
+
Not sure if you mean fngetsw here (copy paste) ?
No, I want to return the status word in %ax, rather that write
it to a memory location.
David
--
David Laight: da
need.
Separation in the kernel is even worse.
David
--
David Laight: da...@l8s.co.uk
On Sun, Feb 23, 2014 at 02:48:19PM -0800, John Nemeth wrote:
On Feb 23, 10:35pm, David Laight wrote:
}
} Module Name:src
} Committed By: dsl
} Date: Sun Feb 23 22:35:28 UTC 2014
}
} Modified Files:
} src/sys/arch/i386/i386: freebsd_machdep.c
the old style #define constants
instead of the new style (since 2005) CTL_CREATE idiom?
I certainly thought that no new 'fixed number' sysctls were supposed to
be added.
David
--
David Laight: da...@l8s.co.uk
On Sat, Mar 01, 2014 at 08:31:42AM +0200, Alan Barrett wrote:
On Thu, 27 Feb 2014, David Laight wrote:
Modified Files:
src/sys/kern: kern_sysctl.c
+case CTLTYPE_INT:
+/* Allow for 64bit read of 32bit value */
+if (*oldlenp == sizeof (uint64_t
will be quite happy with
either a 32bit of 64bit result.
David
--
David Laight: da...@l8s.co.uk
managed to get gcc 4.8 to optimise some fp loops to use the ymm
registers - the xsave/xrstor code seemed to worn an amd64.
But I don't have an i386 install on a new enough system.
David
--
David Laight: da...@l8s.co.uk
to remove the target file on failure.
Or maybe change the last line to:
${.TARGET}.tmp mv ${.TARGET}.tmp ${.TARGET}
David
--
David Laight: da...@l8s.co.uk
and then realise
that they are just longhand!
I don't normally compare bit masking against zero, just:
if (var BIT)
or
if (!(var BIT))
to me they read better that way.
David
--
David Laight: da...@l8s.co.uk
an interval in microseconds and bounded to less than
a second.
The code is doing:
long x = arc4random() % (1 * 100);
That really shouldn't generate a compiler warning.
David
--
David Laight: da...@l8s.co.uk
On Tue, Mar 18, 2014 at 08:21:19PM +, Christos Zoulas wrote:
In article 20140318201420.go20...@snowdrop.l8s.co.uk,
David Laight da...@l8s.co.uk wrote:
On Tue, Mar 18, 2014 at 03:30:09PM -0400, Christos Zoulas wrote:
Module Name: src
Committed By: christos
Date
++)
it can't matter that the comparison is unsigned because 'i' can be
assumed to be non-negative (even if 'sizeof foo' is greater than MAXINT).
David
--
David Laight: da...@l8s.co.uk
hadn't spotted that xtos had added a cast as well.
There is another cast that ought to be pointless two lines later.
David
--
David Laight: da...@l8s.co.uk
about for dumps?
Although I'm not at all sure what this particular file is for...
From the diff it looks like it needs for TLC in order to get sane
partition offsets.
David
--
David Laight: da...@l8s.co.uk
On Tue, Apr 01, 2014 at 07:16:18AM +, David Laight wrote:
Module Name: src
Committed By: dsl
Date: Tue Apr 1 07:16:18 UTC 2014
Modified Files:
src/sys/arch/x86/x86: x86_machdep.c
Log Message:
Revert most of the machdep sysctls to 32bit
I think I remember why I set
though that loading the kernel
from other than the root parition was needed for some non-raid
configurations - eg large disks.
David
--
David Laight: da...@l8s.co.uk
. A prefetch there could also fault.
David
--
David Laight: da...@l8s.co.uk
paging - so you could only run
OS that swap entire processes.
The '020 saves the mid-instruction state for some faults (as well as the
actual fault reason) so they can be recovered.
(Just don't continue on a cpu with a different mask level.)
David
--
David Laight: da...@l8s.co.uk
the
internal route statistics. Restore the old kmem route printing code that
was not just used for post-mortem displays. Reported by kardel@, test by
netstat -nrvf inet
That seems a large backwards step...
David
--
David Laight: da...@l8s.co.uk
that NFS clients would write to the wrong file in the wrong FS.
The 'impossible to get rid of' retries for hard mounts were something
up with which I had to put. (A preposition is something you should not
end a sentence with.)
David
--
David Laight: da...@l8s.co.uk
years ago...
David
--
David Laight: da...@l8s.co.uk
and lsof could use the
new define instead of _KERNEL.
MSDOSFS_MOUNT_USERLAND_DEFS or something.
or _KMEM_USER ?
David
--
David Laight: da...@l8s.co.uk
(if
available), fall back to . if not, or use build-in english otherwise.
Is that really the best order?
Wouldn't it be more useful to look in . first?
David
--
David Laight: da...@l8s.co.uk
space for sysinst to drop core.
Unless the system has very limited memory (in which case it really won't
run much) then adding a meg or two to the ramdisk size probably doen't
matter.
IIRC it is compressed in the install media.
David
--
David Laight: da...@l8s.co.uk
not to a reasonable amount of free space.
David
--
David Laight: da...@l8s.co.uk
that the underlying type differs between architectures.
There must be a gcc config switch somewhere.
I wonder what they are on other 32bit archs (they mut be 'long' on 64bit
ones).
David
--
David Laight: da...@l8s.co.uk
On Fri, Aug 15, 2014 at 08:14:06AM +0100, David Laight wrote:
On Thu, Aug 14, 2014 at 09:17:33AM +, Martin Husemann wrote:
Module Name:src
Committed By: martin
Date: Thu Aug 14 09:17:32 UTC 2014
Modified Files:
src/sys/arch/vax/include: int_fmtio.h
'strchr(s, 0)' is actually 's + strlen(s)'
David
--
David Laight: da...@l8s.co.uk
wrong.
Do we need to support any compilers that don't support __VA_ARGS__ ?
Even microsoft's compiler almost supports it.
David
--
David Laight: da...@l8s.co.uk
to be accurate to one or two counts on the lsb
of the mantissa.
David
--
David Laight: da...@l8s.co.uk
for it. However, this solves the problem I was having. And, given
that XEN being broken is pretty much a show-stopper for a release,
something needed to be done.
One option would be to detect the fault at runtime.
David
--
David Laight: da...@l8s.co.uk
involved - and apply the 'strict aliasing'
rules in the same way that is applied the 'alignment' ones.
David
--
David Laight: da...@l8s.co.uk
if the checksum is inlined
and any earlier writes to the sector itself are still 'pending'.
David
--
David Laight: da...@l8s.co.uk
On Tue, Dec 30, 2014 at 04:34:42PM -0600, Dennis Ferguson wrote:
On 30 Dec, 2014, at 12:52 , David Laight da...@l8s.co.uk wrote:
Is that the correct fix?
Unless the rdpr actually accesses memory (don't think it does) then
then problem is probably a missing 'volatile' instead
--
David Laight: da...@l8s.co.uk
On Wed, Dec 31, 2014 at 11:15:24AM +0100, Martin Husemann wrote:
On Wed, Dec 31, 2014 at 10:05:22AM +, David Laight wrote:
In this case I suspect removing __constfunc and making the
asm volatile will force correct sequencing.
Check the commit history.
Can we make only the hypverisor
?
David
--
David Laight: da...@l8s.co.uk
platforms
have 64-bit off_t.
Specifying uint32_t and ensuring that 64bit fields are 'aligned'
is good practice and does no harm.
David
--
David Laight: da...@l8s.co.uk
On Wed, Mar 11, 2015 at 06:12:32PM -0400, Greg Troxel wrote:
David Laight da...@l8s.co.uk writes:
I'm also not sure we need a new kernel config. It seems the systems of
interest are limited to 486 machines without PCI (and thus EISA
probably), and that's a pretty narrow window around
, and no pentium ones.
They probably need a 'small' kernel anyway.
More interesting might be the embedded 486-like systems
from soekris (etc). Not sure if any of those have graphics
but they will normally run a generic kernel.
David
--
David Laight: da...@l8s.co.uk
.
XXX: pullup-7
Maybe patch should stop ed from executing shell commands.
Setting SHELL=/bin/false might be enough.
David
--
David Laight: da...@l8s.co.uk
likely; but stranger things have
happened, and it doesn't help that regexp tools have a long-standing
culture of not complaining about invalid regexp syntax.
anyway it's a very minor point.
It is also less likely to go wrong when someone adds another character.
David
--
David Laight: da
.
Historically /tmp was likely to be small.
That is why /var/tmp exists, and is probably why the compiler defaults
to /var/tmp.
The system should probably clean 'turds' from both /tmp and /var/tmp.
David
--
David Laight: da...@l8s.co.uk
On Tue, Oct 13, 2015 at 09:28:35PM +, Robert Swindells wrote:
> Module Name: src
> Committed By: rjs
> Date: Tue Oct 13 21:28:35 UTC 2015
...
> Log Message:
> Add core networking support for SCTP.
As a matter of interest, where did this come from?
David
-
(for adds) so happening at a different stage in the pipeline and having
different result delay and/or concurrency rules - but I can't remember
which particular cpu that applied to.
David
--
David Laight: da...@l8s.co.uk
On Tue, Aug 11, 2015 at 10:26:43PM +0400, Alan Barrett wrote:
> On Tue, 11 Aug 2015, David Laight wrote:
> >The system should probably clean 'turds' from both /tmp and /var/tmp.
>
> That would be surprising, at least to me.
>
> I rely on /var/tmp/vi.recover being persiste
ource file
and (probably) makes it easier to have MI fallback sources.
David
--
David Laight: da...@l8s.co.uk
being in a .a
file was to allow builds on systems with short command line length
limits.
David
--
David Laight: da...@l8s.co.uk
> thought about it again and came to the conclusion that if I felt I
> needed to bump that number more than once in a day, it would mean that
> I'm not designing and/or developing correctly. I feel that conclusion
> still stands.
If desparate you can always use tomorrow...
David
--
David Laight: da...@l8s.co.uk
mes were the same (or for compat names) they are not copied and the array
> has NULL for them.
H
Isn't that going to be even more confusing since you won't know
whether a 'compat' (or old) system call is being used which might
have issues in the compatibility layer itself.
David
--
David Laight: da...@l8s.co.uk
the same effect and is about as
easy to debug.
Whether kmem_alloc(KM_SLEEP) can return NULL is another matter.
Seems wrong to me - maybe even for impossible allications.
ISTR a problem waiting for KVA and phys-mem being 'difficult'.
I know that the Linux equivalent will return NULL, not sure when.
It would be useful to define that allocation for non-huge
(maybe even several MB) amounts will always sleep.
David
--
David Laight: da...@l8s.co.uk
ough they are probably dup'ed back before
anything is run.
Personally I think it is the job of the scripts to close
any extra fd, not the shell.
David
--
David Laight: da...@l8s.co.uk
to be quite efficient, generating numbers at 10 MBps
> on a NetBSD VM running in Fusion hosted on Mac OS X.
Doesn't sound like anywhere near enough entropy.
If you start with 32 bits you'll get 'birthday paradox' duplicated
sequences after a relatively small number of boots.
David
--
David Laight: da...@l8s.co.uk
"0b" always came out
> as 0 before, but now it doesn't.
>
> that's a fairly major semantic change, i think i agree with joerg that
> it has a high chance of breaking existing usage.
Worse that that, some code might be relying on getting a pointer
to the 'b' and continuing to parse the buffer.
Not a good idea to change it.
David
--
David Laight: da...@l8s.co.uk
he pbr only the mbr (and shouldn't look at much of that).
OTOH, no point changing it.
David
--
David Laight: da...@l8s.co.uk
n non-compliaint, completely f*cked.
It reorders argv[] to move all 'options' before filenames.
So 'foo bar -baz' is changed to 'foo -baz bar' before being processed.
I've NFI of the justification for it.
Historically you could do 'rlogin host -l username' but I
don't know of any others.
David
--
David Laight: da...@l8s.co.uk
201 - 291 of 291 matches
Mail list logo