Hi there,
Probably it is already known problem, but it seems that any unprivileged
malicious user with 15-20 MB disk quota can bring either 3-STABLE or 4-CURRENT
system to its knees using relatively simple program.
#include
#include
#include
#include
#include
main()
{
int fd;
int i
Hi,
-current kernels from the past 48hrs or so lock up during boot on my SMP
box, as in:
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #50: Tue Oct 26 13:53:14
It seems Bob Bishop wrote:
> Hi,
>
> -current kernels from the past 48hrs or so lock up during boot on my SMP
> box, as in:
>
> ...and there it freezes. Total lockup, reset button or power cycle only.
> Apparently it's barfing either on one of the PCI netcard probes, or trying
> to initialise ed
Anyone running -current as of Oct 28, 1999 getting lockups in
device strategy routines?
I thought I'd be able to get a dump but it didn't work.
Specifically I'm running vinum in striping mode and the new ata-drivers.
10 Aug 1999 14:27:51.389915 stripe /dev/da0e /dev/da1e
A kernel from Wed Oc
Hello,
just another datapoint. I just installed two new IBM DPTA-343740
discs into my System at home. They are configured with striping in vinum.
Within a day I got two solid lockups with the new ata-drivers. After
that I switchied to the old wd-driver. Everythings works fine since then.
I do
On Thu, 28 Oct 1999, Marcel Moolenaar wrote:
> Peter Jeremy wrote:
> >
> > >(/me wonders how many MORE times we are going to have to say this because
> > >of the signal changes...)
> >
> > A very large number I suspect.
> >
> > IMHO, the correct solution is to for the entire make world process
On Mon, 25 Oct 1999, Peter Jeremy wrote:
> I've recently upgraded a system from 3.2-RELEASE to -CURRENT as of
> 30-Sept (just before the signal changes). I now find that when
> I try to do a CVS checkout, the system hangs, with cvs in `nbufkv'.
>
> The CVSROOT is on a filesystem with standard 8
Dear sporting friends,
We want to inform you that we will organize international football
tournaments in Sardinia, of which you will find more greater reports in
the enclosed news.
We like invite yours teams to these tournaments. When your team had
interested to the participation in one or more of
"Chris D. Faulhaber" wrote:
>
> On Thu, 28 Oct 1999, Marcel Moolenaar wrote:
>
> > Peter Jeremy wrote:
> > >
> > > IMHO, the correct solution is to for the entire make world process to
> > > be re-worked.
> >
> > That's what I'm currently doing. If I have a stripped down make process
> > ready f
I have been trying to figure out a sane method of stopping this one:
while(1) {
fork();
}
on a machine with no limits the load went to 290+ I tried fiddling with
limits and got it down to making the load 2-3 but the limits are ridiculous.
I didn't look in mail archives so sorry if this has been d
I seem to recall allowing a limit for max processes when I was looking at
fork bombs back in '95 ... ahh the memories.
- ( Adam Strohl ) -
- UNIX Operations/Systems http://www.digitalspark.net -
- adams (at) digitalspark.net
On Fri, 29 Oct 1999, Luke wrote:
> I have been trying to figure out a sane method of stopping this one:
> while(1) {
> fork();
> }
>
> on a machine with no limits the load went to 290+ I tried fiddling with
> limits and got it down to making the load 2-3 but the limits are ridiculous.
> I didn't
On Fri, 29 Oct 1999, #Michael Class wrote:
> Hello,
>
> just another datapoint. I just installed two new IBM DPTA-343740
> discs into my System at home. They are configured with striping in vinum.
> Within a day I got two solid lockups with the new ata-drivers. After
> that I switchied to the
Alfred Perlstein wrote:
> however if a limited
> user is able to take down a box we want to hear about it.
Take a look at my posting with "VM DOS attack" subject.
-Maxim
--
"We believe in the Power and the Might!"
(Manowar, 1996)
To Unsubscribe: send mail to [EMAIL
< said:
> ohci0: irq 9 at device 11.0 on pci0
> +ohci_waitintr: timeout
IRQ 9 is shared with the VGA controller. Perhaps calling the VESA
BIOS caused it to do something strange that interfered with the
delivery of this interrupt on your motherboard.
-GAWollman
--
Garrett A. Wollman | O Si
Matthew Dillon writes:
>
> Well, there was a bug in nfsrv_create() which caused the server to
> not reply to an NFS packet. This led to a general revamping of the
> server side code which may have fixed other rpc's at the same time.
> Whether fixing that bug solves the prob
On Thu, 28 Oct 1999, Randy Bush wrote:
> o so build -current binary for config
> o update kernel config file to -current
> o config a -current kernel
> o make a -current kernel
> o install -current kernel
> o reboot
> o crash in init after configuring network, but was too fast to c
On Thursday, 28 October 1999 at 10:52:30 -0400, Garrett Wollman wrote:
> <
>said:
>
> > The lsof functionality should in my opinion be added to the system,
> > and the necessary hooks should be added to the kernel using sysctl.
>
> fstat(1).
It doesn't quite have the functionality.
Greg
--
F
On Thu, 28 Oct 1999, Randy Bush wrote:
> trying to take a system from stable to current.
> o cvsup current
> o try makeworld but get
Bzzt! Read /usr/src/UPDATING. You need a new kernel first.
I still hate the way the signal change was handled.
Doug White| FreeBSD: T
On Friday, 29 October 1999 at 5:10:07 -0700, Alfred Perlstein wrote:
>
> Anyone running -current as of Oct 28, 1999 getting lockups in
> device strategy routines?
>
> I thought I'd be able to get a dump but it didn't work.
>
> Specifically I'm running vinum in striping mode and the new ata-driver
On Tuesday, 26 October 1999 at 11:26:47 +0100, Geoff Buckingham wrote:
> On Sun, Oct 24, 1999 at 09:58:11AM -0600, Greg Lehey wrote:
>>
>> Indeed. It's quite easy to put all cylinder groups on a single
>> spindle; I've seen reports of up to 80% degradation under these
>> circumstances.
>>
>>> Whe
On Sunday, 24 October 1999 at 8:53:28 -0700, Dennis Glatting wrote:
>
> I just want to document some strangeness I see with vinum, in case it
> has been noticed before but not identified, or someone knows a cure.
You should read vinum(4). It tells you what kind of information I
need for resolvi
On Fri, 29 Oct 1999, Doug White wrote:
> I still hate the way the signal change was handled.
How would you have done it differently? As I understand it, the pain
was more or less inevitable.
--
Ben Rosengart
UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.
To Unsubscribe: send
All,
rlogind has been broken for me (-current) for a couple of weeks -
is this a known problem ?
--atrens@churchill: /usr/home/andrew --
$ cat .rhosts
+ atrens
+ andrew
+ root
--atrens@churchill: /usr/home/andrew --
$ rlogin localhost
assword:asdfasfdasdfas
^C
--atrens@churchill: /usr/hom
All,
I recently moved from a K6-2 to a K6-III and my dmesg output appears to
have changed. In particular I'm not seeing messages about wrtalloc and
mtrr support anymore - are they not supported for the K6-III ?
FreeBSD 4.0-CURRENT #0: Fri Oct 29 01:59:19 EDT 1999
atrens@churchill:/usr/loca
Hi,
Ever since the libtermcap / libncurses consolidation, change emacs has
problems positioning the cursor and properly updating the screen for
character-only devices like the console. It also affects the display
in an xterm in non-X mode, i.e., when DISPLAY is *not* set.
This is emacs 20.4, by
|Hi,
|
|Ever since the libtermcap / libncurses consolidation, change emacs has
|problems positioning the cursor and properly updating the screen for
|character-only devices like the console. It also affects the display
|in an xterm in non-X mode, i.e., when DISPLAY is *not* set.
|
|This is emacs
The other day my machine was attacked with, what i believe is, a SYN
flood. tcpdump gave me this output (1.1.1.1 is me and 2.2.2.2 is him)
20:57:05.828276 2.2.2.2.4064 > 1.1.1.1.33948: S
1409055765:14090557
65(0) win 32120 (DF)
20:57:05.836343 2.2.2.2.4065 > 1.1.1.1.14060: S
1409337177:14093371
"Russell L. Carter" <[EMAIL PROTECTED]> writes:
> Yup! And also for 19.34b... I've searched all over for the
> source of this problem, glad to know I'm not alone. However,
> it only affects one of my three -current boxes, so apparently there is
> bit of cruft lying around, but I haven't bee
> Ever since the libtermcap / libncurses consolidation, change emacs has
> problems positioning the cursor and properly updating the screen for
> character-only devices like the console. It also affects the display
> in an xterm in non-X mode, i.e., when DISPLAY is *not* set.
>
> This is emacs 2
I would appreciate it if people running -current would run a "vmstat -s"
and tell me if they see a NON-ZERO value for copy-on-write optimized
faults. About six months ago, I implemented a simpler and more general
optimization at an earlier "fork in the road". (In effect, I avoid
the creation of
On Fri, Oct 29, 1999 at 02:47:43PM -0500, Alan Cox wrote:
> I would appreciate it if people running -current would run a "vmstat -s"
> and tell me if they see a NON-ZERO value for copy-on-write optimized
> faults. About six months ago, I implemented a simpler and more general
> optimization at an
On Fri, Oct 29, 1999 at 09:51:55PM +0200, Jesper Skriver wrote:
>
> Those "about six months" can you be more specific ?
>
Sorry for being imprecise. It was May 16th.
> $ uname -a
> FreeBSD pebbles.tele.dk 4.0-CURRENT FreeBSD 4.0-CURRENT #2: Thu Apr 22 11:52:50 CEST
>1999
> [EMAIL PROTECTED]:
|"Russell L. Carter" <[EMAIL PROTECTED]> writes:
|
|> Yup! And also for 19.34b... I've searched all over for the
|> source of this problem, glad to know I'm not alone. However,
|> it only affects one of my three -current boxes, so apparently there is
|> bit of cruft lying around, but I haven
I've had an ATAPI CDROM as master and an HP Colorado tape as slave set up
on my system for quite some time now. I recently migrated to 4.0 and
I'm using the new ATA drivers. Below is a snip from my kernel config:
controller ata0
device atadisk0
device atapicd0
device
According to Alan Cox:
> I would appreciate it if people running -current would run a "vmstat -s"
> and tell me if they see a NON-ZERO value for copy-on-write optimized
FreeBSD keltia.freenix.fr 4.0-CURRENT FreeBSD 4.0-CURRENT #74: Thu Sep 9 00:20:51
CEST 1999 [EMAIL PROTECTED]:/src/src/sys
On Fri, Oct 29, 1999 at 07:22:58AM -0700, Alfred Perlstein <[EMAIL PROTECTED]>
wrote:
> On Fri, 29 Oct 1999, #Michael Class wrote:
>
> > Hello,
> >
> > just another datapoint. I just installed two new IBM DPTA-343740
> > discs into my System at home. They are configured with striping in vinu
On Fri, Oct 29, 1999 at 02:47:43PM -0500, Alan Cox wrote:
> I would appreciate it if people running -current would run a "vmstat -s"
> and tell me if they see a NON-ZERO value for copy-on-write optimized
> faults. About six months ago, I implemented a simpler and more general
> optimization at an
vmstat -s reports these numbers on my computer:
3649151 copy-on-write faults
1 copy-on-write optimized faults
On 29-Oct-99 Alan Cox wrote:
> I would appreciate it if people running -current would run a "vmstat -s"
> and tell me if they see a NON-ZERO value for copy-on-write optimized
>
On Sat, Oct 30, 1999 at 12:47:40AM +0200, Bernd Walter wrote:
>
> 307625181 copy-on-write faults
>26 copy-on-write optimized faults
Thanks to Bernd and everyone else who has responded. Unless someone
reports a case where the old "optimization" gets applied more often
than 1 in ten millio
: > :
: > :Thanks,
: > :
: > :Drew
: >
: > There should be a response to the rpc either way so my guess is that
: > it is a server-side bug.
:
:It turns out that the user was in 17 groups (DU supports up to 32).
:After I removed him from 2 groups & got his group count down to 15,
:all w
Matthew Dillon writes:
>
> Ahhh... I'm glad you found it. I was beginning to scratch my head.
>
> NGROUPS_MAX is set to 16 (/usr/src/sys/sys/syslimits.h). You may
> be able to patch the kernel to up the number of groups by upping
> the value in that define and recompilin
:Matthew Dillon writes:
: >
: > Ahhh... I'm glad you found it. I was beginning to scratch my head.
: >
: > NGROUPS_MAX is set to 16 (/usr/src/sys/sys/syslimits.h). You may
: > be able to patch the kernel to up the number of groups by upping
: > the value in that define and rec
Matthew Dillon writes:
> :Eg, will I need to worry about uppting NGROUPS_MAX when I upgrade the
> :box to a more recent kernel?
> :
<..>
> I don't know, I don't have a non-FreeBSD box to test with. I would
> be interested in knowing the answer!
I'll let you know. It might be a w
I wasn't able to get a crashdump last time i locked up, but it was
defiently in the same spot, now i have a crashdump.
The panic is because I attempted to view a datastructure I shouldn't
have after it locked up, the lockup point I assume is at frame
11, 12 or 13.
Netscape seems to be able to t
On Fri, 29 Oct 1999, Ben Rosengart wrote:
> On Fri, 29 Oct 1999, Doug White wrote:
>
> > I still hate the way the signal change was handled.
>
> How would you have done it differently? As I understand it, the pain
> was more or less inevitable.
Perhaps, but there must be a way to keep gcc fr
On Fri, 29 Oct 1999, Doug White wrote:
> On Fri, 29 Oct 1999, Ben Rosengart wrote:
>
> > On Fri, 29 Oct 1999, Doug White wrote:
> >
> > > I still hate the way the signal change was handled.
> >
> > How would you have done it differently? As I understand it, the pain
> > was more or less inev
Hi,
I'm not real sure were to send this, though I'm sure someone
will tell me... but... In writing a few scripts which process
the INDEX file, I've come across the following entry which doesn't
look right...
ja-|/usr/ports/japanese/exmh2|/usr/local|X11/TK based mail reader front end to M
H fo
WARNING: / was not properly dismounted
start_init: trying /sbin/init
swapon: adding /dev/ad0b as swap device
Automatic reboot in progress...
/dev/rwd0s4a: 2199 files, 38154 used, 209893 free (277 frags, 26202
blocks, 0.1% fragmentation)
[HANGS...]
^Cfsck in free(): warning: page is already free.
This has nothing to do with blockdevs. It is an old standing bug in fsck
which only happens when you interrupt it. "Uncle Milt" from vicor has a
set of fsck patches in for review with Kirk where this should be fixed
as well.
In all likelyhood your fsck didn't hang but was working its way throu
On Sat, 30 Oct 1999, Poul-Henning Kamp wrote:
>
> This has nothing to do with blockdevs. It is an old standing bug in fsck
> which only happens when you interrupt it. "Uncle Milt" from vicor has a
> set of fsck patches in for review with Kirk where this should be fixed
> as well.
>
> In all
On Fri, 29 Oct 1999, Alan Cox wrote:
> Thanks to Bernd and everyone else who has responded. Unless someone
> reports a case where the old "optimization" gets applied more often
> than 1 in ten million copy-on-write faults, I'm going to remove
> the old code in a few days. At this frequency, the
I disabled (or asked Peter to, actually) the K6-2+ MTRR driver a while
back because with XFree86 3.9.16 (an alpha which uses MTRR support) it
would cause memory corruption. It's very strange, and something I
really haven't figured out... If you want to enable it, go ahead, but
be very wary; if yo
If you did a kldstat (in gdb. Use Greg Lehey's .gdbinit* from vinum) and
added the pertinent KLD as a symbol file correctly (also reference
the .gdbinit*), you would probably get more useful output. Try
that and let me know. FWIW, I have my CFLAGS + -g in the modules
just as I have my kernel -g
>>> great. then i have screwed up somehow. i do not think i changed anything
>>> from how it ran in 4.0-current, but i must have. but what?
>>> symptom is i can use it for a little while and then the system freezes.
>>> so the basic configuration is correct, i.e. i am driving the hardware.
>> I
On Sat, 30 Oct 1999, Brian Fundakowski Feldman wrote:
> If you did a kldstat (in gdb. Use Greg Lehey's .gdbinit* from vinum) and
> added the pertinent KLD as a symbol file correctly (also reference
> the .gdbinit*), you would probably get more useful output. Try
> that and let me know. FWIW, I
56 matches
Mail list logo
