Re: HEADS UP! bad bug in -current.
On Wed, May 02, 2001, Robert Watson wrote: > On Tue, 1 May 2001, Jordan Hubbard wrote: > > > > Say, FreeBSD is usually pretty safe, even in CURRENT. > > > Has something near this magnitude of Really Bad Stuffage snuck into the > > > codebase before? > > > > No, it's not common, and it generally takes a Dane swinging something > > sharp to inflict quite this much damage on our user base. ;-) > > Obviously I haven't been playing in the right bits of the system, I'll > have to start hacking the low-level stuff in FFS some more... I tend not > to cause permanent damage to file systems, sadly. > > I think we can all take lessons from phk here -- he achieves a level of > destructiveness that makes even the pro's marvel in wonder. *grin* Its ok. phk has just reminded us of what -current really is .. :-) Adrian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
On Fri, 4 May 2001, John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Robert Watson <[EMAIL PROTECTED]> wrote: > > > > I think we can all take lessons from phk here -- he achieves a level of > > destructiveness that makes even the pro's marvel in wonder. > > Your criticism is grossly unfair. Throughout the very long time he's > been active in this project, PHK's contribution/breakage ratio has been > unsurpassed. I think my sarcasm may have gotten lost in transit; please re-read the message with a big blinking "Sarcasm Follows" post-it note reattached. I have great respect for Poul-Henning's work, especially with regards to his expertise in the device and buffering mechanisms in FreeBSD. The degree to which this is the case will becomes more clear in the near future. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
In article <[EMAIL PROTECTED]> you wrote: > In article <[EMAIL PROTECTED]>, > Robert Watson <[EMAIL PROTECTED]> wrote: >> >> I think we can all take lessons from phk here -- he achieves a level of >> destructiveness that makes even the pro's marvel in wonder. > > Your criticism is grossly unfair. Too much snipping; that wasn't critizism. It was pure jealousy. 8-) He also said "obviously I haven't been playing in the right bits of the system, I'll have to start hacking the low-level stuff in FFS some more..." And - who knows - it might be that phk's real middle name is "Haegar" 8-))). (Am I the only one making back up copies before "make installkernel; make installworld"?) Achim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
John Polstra <[EMAIL PROTECTED]> wrote: > Your criticism is grossly unfair. Throughout the very long time he's > been active in this project, PHK's contribution/breakage ratio has > been unsurpassed. And btw., the recent stdio breakage wasn't all that bad either, and it completely happened in userland. I ended up in reinstalling a system from backup tapes, so the effect is not different to the specfs bug. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
In article <[EMAIL PROTECTED]>, Robert Watson <[EMAIL PROTECTED]> wrote: > > I think we can all take lessons from phk here -- he achieves a level of > destructiveness that makes even the pro's marvel in wonder. Your criticism is grossly unfair. Throughout the very long time he's been active in this project, PHK's contribution/breakage ratio has been unsurpassed. John -- John Polstra [EMAIL PROTECTED] John D. Polstra & Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
On Tue, 1 May 2001, Jordan Hubbard wrote: > > Say, FreeBSD is usually pretty safe, even in CURRENT. > > Has something near this magnitude of Really Bad Stuffage snuck into the > > codebase before? > > No, it's not common, and it generally takes a Dane swinging something > sharp to inflict quite this much damage on our user base. ;-) Obviously I haven't been playing in the right bits of the system, I'll have to start hacking the low-level stuff in FFS some more... I tend not to cause permanent damage to file systems, sadly. I think we can all take lessons from phk here -- he achieves a level of destructiveness that makes even the pro's marvel in wonder. Robert N M Watson FreeBSD Core Team, TrustedBSD Project [EMAIL PROTECTED] NAI Labs, Safeport Network Services To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
On Tue, 1 May 2001, Peter Wemm wrote: > Any -current kernel built over the weekend is a likely victim of this bug. > In a nutshell, it will eat your root filesystem at the very least, leaving > you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 > is should be avoided at all costs. > > BEWARE: there are some snapshots on current.freebsd.org with this bug. They > will self destruct after install. Too late - I'm just rebuilding one of my scratch machines right now :-( -- Doug Rabson Mail: [EMAIL PROTECTED] Phone: +44 20 8348 6160 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
On Tue, May 01, 2001 at 06:23:59PM -0500, GH wrote: > On Tue, May 01, 2001 at 12:15:34PM -0700, some SMTP stream spewed forth: > > Any -current kernel built over the weekend is a likely victim of this bug. > > In a nutshell, it will eat your root filesystem at the very least, leaving > > you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 > > is should be avoided at all costs. > > > > BEWARE: there are some snapshots on current.freebsd.org with this bug. They > > will self destruct after install. > > > > --- Forwarded Messages > *snip* > > Say, FreeBSD is usually pretty safe, even in CURRENT. > Has something near this magnitude of Really Bad Stuffage snuck into the > codebase before? > > (This is just for my personal knowledge. I don't remeber anything this > bad in recent times.) It happens from time to time. VM was really unstable for a period a few years ago (3.0-CURRENT timeframe) when John Dyson was dinking with it. This is why you need to be extra-careful when running -current on systems with data you care about :-) Kris PGP signature
Re: HEADS UP! bad bug in -current.
On 01-May-01 Jordan Hubbard wrote: >> Say, FreeBSD is usually pretty safe, even in CURRENT. >> Has something near this magnitude of Really Bad Stuffage snuck into the >> codebase before? > > No, it's not common, and it generally takes a Dane swinging something > sharp to inflict quite this much damage on our user base. ;-) > > - Jordan I dunno, certain Berkeley professors have pretty close as well. ;) -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
It was almost like that dirpref problem I ran into a few weeks ago, I upgraded from -stable to -current and I had to reinstall because of it, but this usually doesn't happen. - Original Message - From: "Jordan Hubbard" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, May 01, 2001 6:56 PM Subject: Re: HEADS UP! bad bug in -current. > > Say, FreeBSD is usually pretty safe, even in CURRENT. > > Has something near this magnitude of Really Bad Stuffage snuck into the > > codebase before? > > No, it's not common, and it generally takes a Dane swinging something > sharp to inflict quite this much damage on our user base. ;-) > > - Jordan > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
> Say, FreeBSD is usually pretty safe, even in CURRENT. > Has something near this magnitude of Really Bad Stuffage snuck into the > codebase before? No, it's not common, and it generally takes a Dane swinging something sharp to inflict quite this much damage on our user base. ;-) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP! bad bug in -current.
On Tue, May 01, 2001 at 12:15:34PM -0700, some SMTP stream spewed forth: > Any -current kernel built over the weekend is a likely victim of this bug. > In a nutshell, it will eat your root filesystem at the very least, leaving > you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 > is should be avoided at all costs. > > BEWARE: there are some snapshots on current.freebsd.org with this bug. They > will self destruct after install. > > --- Forwarded Messages *snip* Say, FreeBSD is usually pretty safe, even in CURRENT. Has something near this magnitude of Really Bad Stuffage snuck into the codebase before? (This is just for my personal knowledge. I don't remeber anything this bad in recent times.) gh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP! bad bug in -current.
Any -current kernel built over the weekend is a likely victim of this bug. In a nutshell, it will eat your root filesystem at the very least, leaving you with maybe one or two files in /lost+found. spec_vnops.c rev 1.156 is should be avoided at all costs. BEWARE: there are some snapshots on current.freebsd.org with this bug. They will self destruct after install. --- Forwarded Messages phk 2001/04/29 04:48:42 PDT Modified files: ...[other files in commit trimmed] sys/miscfs/specfsspec_vnops.c Log: Add a vop_stdbmap(), and make it part of the default vop vector. Make 7 filesystems which don't really know about VOP_BMAP rely on the default vector, rather than more or less complete local vop_nopbmap() implementations. Revision ChangesPath 1.156 +1 -2 src/sys/miscfs/specfs/spec_vnops.c --- Message 2 bde 2001/04/30 07:35:37 PDT Modified files: sys/miscfs/specfsspec_vnops.c Log: Backed out previous commit. It cause massive filesystem corruption, not to mention a compile-time warning about the critical function becoming unused, by replacing spec_bmap() with vop_stdbmap(). ntfs seems to have the same bug. The factor for converting specfs block numbers to physical block numbers is 1, but vop_stdbmap() uses the bogus factor btodb(ap->a_vp->v_mount->mnt_stat.f_iosize), which is 16 for ffs with the default block size of 8K. This factor is bogus even for vop_stdbmap() -- the correct factor is related to the filesystem blocksize which is not necessarily the same to the optimal i/o size. vop_stdbmap() was apparently cloned from nfs where these sizes happen to be the same. There may also be a problem with a_vp->v_mount being null. spec_bmap() still checks for this, but I think the checks in specfs are dead code which used to support block devices. Revision ChangesPath 1.157 +2 -1 src/sys/miscfs/specfs/spec_vnops.c --- End of Forwarded Messages To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
