From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 12 00:20:15 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08CFF16A415 for ; Sun, 12 Nov 2006 00:20:14 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53D1643D46 for ; Sun, 12 Nov 2006 00:19:58 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 55E0646C9A; Sat, 11 Nov 2006 19:19:40 -0500 (EST) Date: Sun, 12 Nov 2006 00:19:40 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: trowa-4 In-Reply-To: <571883.4868.qm@web72011.mail.tp2.yahoo.com> Message-ID: <20061112001826.Y45016@fledge.watson.org> References: <571883.4868.qm@web72011.mail.tp2.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: Process Debugging questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 00:20:15 -0000 On Sun, 12 Nov 2006, trowa-4 wrote: > FreeBSD provides the ptrace system call for controlling and debugging the > execution of a process. > > An alternative to the ptrace system call is the /proc filesystem. The > functionality provided by the /proc filesystem is the same as that provided > by ptrace; if differs only in its interface. > > Are there having a better method or other method? Historically, procfs has been a major source of security vulnerabilities for all major UNIX platforms that have used it. Since it largely duplicates the functionality of ptrace(), it is now disabled by default. However, there is some functionality only present in procfs that leads people to enable it in some situations. My advice is to use ptrace() if you can do everything you need with it, but otherwise consider using procfs. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 11 19:13:31 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0A2B16A4C2 for ; Sat, 11 Nov 2006 19:13:31 +0000 (UTC) (envelope-from gergely.czuczy@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AA0E43D62 for ; Sat, 11 Nov 2006 19:13:22 +0000 (GMT) (envelope-from gergely.czuczy@harmless.hu) Received: from localhost (marvin-mail [192.168.0.2]) by marvin.harmless.hu (Postfix) with ESMTP id D67947C00BF; Sat, 11 Nov 2006 20:13:28 +0100 (CET) X-Virus-Scanned: amavisd-new at harmless.hu Received: from marvin.harmless.hu ([192.168.0.2]) by localhost (marvin.harmless.hu [192.168.0.2]) (amavisd-new, port 10024) with ESMTP id dPyBzsh7bDiw; Sat, 11 Nov 2006 20:13:23 +0100 (CET) Received: from marvin.harmless.hu (localhost [127.0.0.1]) by marvin.harmless.hu (Postfix) with ESMTP id 148C27C00B7; Sat, 11 Nov 2006 20:13:22 +0100 (CET) Date: Sat, 11 Nov 2006 20:13:22 +0100 From: Gergely CZUCZY To: Kris Kennaway Message-ID: <20061111191322.GA56870@harmless.hu> References: <20061111172731.GB39999@harmless.hu> <20061111183110.GA6975@xor.obsecurity.org> <20061111183432.GA41296@harmless.hu> <20061111184025.GA7128@xor.obsecurity.org> <20061111184625.GA41463@harmless.hu> <20061111185228.GA7338@xor.obsecurity.org> <20061111185747.GA56613@harmless.hu> <20061111190245.GA7577@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=x-unknown; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <20061111190245.GA7577@xor.obsecurity.org> User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Mailman-Approved-At: Sun, 12 Nov 2006 05:08:44 +0000 Cc: hackers@FreeBSD.org Subject: Re: system randomly freezes X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2006 19:13:31 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 11, 2006 at 02:02:46PM -0500, Kris Kennaway wrote: > On Sat, Nov 11, 2006 at 07:57:47PM +0100, Gergely CZUCZY wrote: >=20 > > > OK, seems weird to go through all the disruption of changing to a new > > > OS instead of a few minutes work at a console to give us what we need > > > to resolve the matter -- but whatever works for you. > > already done some stuff like these movings... i'm familiars with them. > > it's not about a few minutes work. it's about the few hours' downtime :) >=20 > It's a few minutes to perform the additional work at the serial > console when your system hangs, which is *required* for a developer to > help with your problem. If you're not willing to do this, there's not > much more we can do for you. i will see what can i do. a serial console may be accessable, but i'm not s= ure. i will have to visit the server hotel and talk with the techies there. we have two boxes there, and it may be somehow possible to connect their serial ports. the problem is, they are far away in the room from each other. the hotel only gives system console(VGA+ps2 keyboard) access if i ask. but this bloody box sometimes ain't even responses to that anyways, the LCD remains blank. i'd like to solve this, but the technical opportunities are limited here. we cannot have downtime, and if we have it have to be minimized. as you see clients won't accept a reasons like "sorry, we were debugging this OS we run at the server". the question will be that, when i have a serial link, and shit happens(tm), should i inspect it myself, or should i scream somewhere for a more decent person (maybe a developer) to check it? > > > > > > taking into account these facts, exactly what additional debugg= ing > > > > > > would you recommend? > > > > >=20 > > > > > Turn on all the usual debugging checks (WITNESS, INVARIANTS, > > > > > DEBUG_*_LOCKS, etc) and check whether anything turns up. > > > > i've found these in conf/NOTES and i386/conf/NOTES: > > > > options WITNESS > > > > options INVARIANTS > > > > options DEBUG_VFS_LOCKS > > > >=20 > > > > anything else? > > >=20 > > > Well, yeah...I'd hoped you'd be able to figure it out for yourself > > > though without me spelling it out :) Also add INVARIANT_SUPPORT and > > > DEBUG_LOCKS. > > good. i had some compiling errors :) > > sorry, but i'm not familiar with building a debug kernel > >=20 > > > First, try with just altq removed, in case that already fixes it. If > > > not, then proceed as above. > > okey. when 6.2 comes at, to that on the nearest sunday i will update > > the system anyways, and check it with this new configuration. i wouldn't > > make an unnessecary downtime if it's not required. >=20 > After 6.2 is release will of course be too late for you, again. If > the problem is not fixed by magic then you'll be in the same position > you are now. why too late? it usually go for a month with a reboot. and it should be released in a month. as i see, it fits into the time :) >=20 > I really suggest you get that serial console hooked up, read the > documentation I pointed you at, and then put in the trivial effort > required to let the FreeBSD team help you. >=20 > > BTW, currently' i'm not on the list, and these emails are not > > going to be posted there. > > would you be so kind and include the mailing list in your > > next reply's CC list? > > it would be nice if the mailing list could archive this > > discussion. >=20 > You were the one who dropped the list from the CC in your reply to > me ;-) err... the first letter i'd got from you didn't contained the list itself. i usually do a reply-to-all, and because it wasn't mentioned, i double-chec= ked it. nevermind, now it gets CC'd there. Bye, Gergely Czuczy mailto: gergely.czuczy@harmless.hu --=20 Weenies test. Geniuses solve problems that arise. --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) owF1V01vHUkVzWQEi0YIzQqNxKI0mxcn73WencQOL2OM4ziRlcGOxk6iGRZRdXf1 68LdVZ2qar90xA9gAShiywJWg5BAYsEPmM1sQeIv8AfYIXacW1Xdz5mZxJE/Xt+6 de+55557+833379y9YN//O3vP7/x69/9/r2//uCL7EbTOaeWs4abC6lmm/P55uzO 9t2d+ezHs808u71Z5Du3xO2cl+Wdw2fsXwdaOaHc7KxvxYI58crdbGsu1T2WV9xY 4XY7V87uJoPdA2lbbaWTWi2YVLVUYnx2ZriypTCzQ5XrQqrlgr3stBPFrDVSOZ7V IklOFDvlbsqO9QXb3Jyyrfl8m3HH5lsL/L+9/eRnbDa/M59P2WMjLXsslOIr3rOV gadF8hP2Tgc7izs7i9s7cHBjvkkOHgmzFHXPDj5/evD5Z6OH3a053NDXyeMps0I0 lq2ENAVzmi01c5XR3bJivK7xu2CFtKZrKWOmS4JFLZEbGXOmxGrwdQo4rBO8ICvO SrFijVSdE/CuzTmFyFmuldW18DfJC8E6PKzwZCXgShTRF54aATsYUAANd04YNpux rHPeXlzgb/JqWakN63WX+qO8NgigZ4VWglnd4JvrypLV8ty7snCmwYulTdOUyUnD St7IWqLSbCVdRTZNcCXdxDKlEXSmO/ctCaXBJDymMMmg0p2xE9y/Uk7i+sXGgPeR N37LC9JshUECjT/Pi8LzitcjYPSxFUbyGh4G7FaVUJSyYbYH4A2jitgpPpd5xcCZ 60a87KQRxXWPDmcF8Ko17sKVcFSJug3pei+t0WBmkzJ2VNInEyN84itZ17HQBbFC 4g4EZEQABo6aDhc2GvaoX84V2Y31kN4B8SuUmJ5LWKQIKOQ0ZtSA3xkAyHNhLbXJ 1Fea6kOB2N2kM2L0WPELT6ALiT4cICJCVOB3zbgCkXl9PhYUXZ1XkvCm4FPEmgQX K80y/Wp4MPUn4TFGQ/Sp9Iqh3a3MAmcRsBK5v1SaJGbRauNs6m+KULIIVc84sCk5 akAtLJU3MlqDdwbfBAd+mm5PE3oSEtAKPUvdYYcCR5yuPXu0f6O1W+xc9JnmptiI kDFZAlpuwUngllCpWFZrjU5Agj4TYiP4J9XEMbBBUYO1cBto6KhAXPWIMkTOPjl4 kBjR4AC54uoc8E+K2EiaDc1JiWaR/wSzkjkQ0S1h0inQmS4FBrVsJISQ+QokgS1U Wl+IoVtiBUpik38g3VhsFARtAy+vRQEGWeIYcSvJawntpZak1AiPlroVOmCRXgj4 I6uN6afkd4UA0A9ZtwwiRlBBusAJ06lLLQc+fZQmviovO2G9+nn2ZcKjNQ1tKEOA I6PRMOchDVv56NtWKHvNNRvTxEIcauRHOtkSi4hrvRV1OWVomvGxzRF846u2Irxi E/s+K0SObBO0MrJj10BV6pt1g294llYiP4f3vSTqaVRVfk4pYxJpwkl3ykVNLHnu UEjxCj/BPd+ul9QowLWb4PRbDlc+YCqEEbluGqGKvbXBeszQ11lnMD7UOFQ6242e KSofs2XXnh+dHR+enk7Z0fGz/U+P9o/PTqeX3Dw4vP/00YvrLz45OXgMI+HyDY92 SBlwUTMRk1FYKi9utaxr09GFnFwQoB2JhM8dTYn2Km8en5wdngYC3rq7fXP92WI8 q/0QtGz4F2N95/N1Cu80Cfk8e3gaMkq+BbsxGVFbEfFdP38u6nrKesErTLQjdGgF Gvii4HfiRlSuUi6hoUQ5GldRpA2Rb5i5lR/6JJpkQaOzFWEAxEOLDbZfW03MWKf2 4vTpkycnn54RcsnlGvl8Au5LKFHqW6UIQxlkaaV3LYzRmL00JmEY2/Sy9g/zOah5 1smaFitPeVAHSmiUoOF4CZKH0lj0pzN9OPSLzoLOtXsJmmL6i2Lqi86tiLoXl4ZS 0iyQzg/C6AsheD1UJO05NhSSHoz8CxFS05DiNEjBdrpFiZHg0ZkoqjpovhJQQYRh QTyaBEFLurbALpME+MWg9qMOr4kt3TDNIFfYuTxlqaKc6ETY+l6EAnpnDYfoYdx2 mFbWipybfr2S0KwYdpthUUiHLWW/pE2LUsFFRtSCUPKx0urnGeMVUGtWI/SBSIh1 iVExIPf2KAx1BLggZI/YljIPkBJJg6LGyWg54hvWa/ghaeF+G1lhaFT9eO8eIeIl hEalHhVSucBgPwAyrVHLONSjumbQ+ZBVQZfGM36gSBonU7ItJeaJl0k/1r62x9Fo oWstlItKSkEuhQvl/tpiU2kQpECdp3TKSw5cFDrvIJbOFw8OW43LQtN67vAgTuAc NUKAxhl5QZ5FiVypykPpiGm1CHProRHi/ukDTGLMD7/lhc146I37Z8+nLO+MweV1 PxmbLJK0lnZ9OwpN47+2sQIutnLcCDNfKIo6bFXJ2wPB708M86YIBVB53RXDNh9a n26j7EiH/GmFly+k1SIyyw4OvMFe3MWja7jFhuE5/A1XubfgBrteXE38Wby95B02 OLTJAMRnCNDvAeSD3hRWFVZcg60lpBP8+Q2N/kIoMcwQXViiQYp7s40EAkavEn7/ J92hWlAL0bK01NELIVJIak9ihkOnXL4IbIMM03o7MLrQnsC4a+b0jJPCE4oZOrmz XsRX3JI3YhEy85KGUx06bkaKsZsQ7SBliaJXJWxOsEAX0VFwleCdjJVL7vdimiTj 2+LrLn/dJ4St0wuY+4/T3H/8U7wUNzVEJa26JJnNCNDnQii/XqMbUrx0KtnRWhlW xCgDNkotXmlx46/23v/OFXr7Hl7dP7j63d9e+eNfdr+3eeveV3/60Ztm8p+rH35p /zz/8sofDv75m49/+MXH/3MffvXv9375ZuPVf+9l/wc= =govz -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 11 19:25:42 2006 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B21D316A412 for ; Sat, 11 Nov 2006 19:25:42 +0000 (UTC) (envelope-from gergely.czuczy@harmless.hu) Received: from marvin.harmless.hu (marvin.harmless.hu [195.56.55.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DF3543DF6 for ; Sat, 11 Nov 2006 19:24:07 +0000 (GMT) (envelope-from gergely.czuczy@harmless.hu) Received: from localhost (marvin-mail [192.168.0.2]) by marvin.harmless.hu (Postfix) with ESMTP id 105127C00C0; Sat, 11 Nov 2006 20:24:13 +0100 (CET) X-Virus-Scanned: amavisd-new at harmless.hu Received: from marvin.harmless.hu ([192.168.0.2]) by localhost (marvin.harmless.hu [192.168.0.2]) (amavisd-new, port 10024) with ESMTP id GFlgIisiMCmI; Sat, 11 Nov 2006 20:24:07 +0100 (CET) Received: from marvin.harmless.hu (localhost [127.0.0.1]) by marvin.harmless.hu (Postfix) with ESMTP id 4DDDC7C00B7; Sat, 11 Nov 2006 20:24:07 +0100 (CET) Date: Sat, 11 Nov 2006 20:24:06 +0100 From: Gergely CZUCZY To: Kris Kennaway Message-ID: <20061111192406.GA57162@harmless.hu> References: <20061111172731.GB39999@harmless.hu> <20061111183110.GA6975@xor.obsecurity.org> <20061111183432.GA41296@harmless.hu> <20061111184025.GA7128@xor.obsecurity.org> <20061111184625.GA41463@harmless.hu> <20061111185228.GA7338@xor.obsecurity.org> <20061111185747.GA56613@harmless.hu> <20061111190245.GA7577@xor.obsecurity.org> <20061111191322.GA56870@harmless.hu> <20061111191733.GB7930@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=x-unknown; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <20061111191733.GB7930@xor.obsecurity.org> User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Mailman-Approved-At: Sun, 12 Nov 2006 05:09:01 +0000 Cc: hackers@FreeBSD.org Subject: Re: system randomly freezes X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Nov 2006 19:25:42 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 11, 2006 at 02:17:33PM -0500, Kris Kennaway wrote: > On Sat, Nov 11, 2006 at 08:13:22PM +0100, Gergely CZUCZY wrote: > > On Sat, Nov 11, 2006 at 02:02:46PM -0500, Kris Kennaway wrote: > > > On Sat, Nov 11, 2006 at 07:57:47PM +0100, Gergely CZUCZY wrote: > > >=20 > > > > > OK, seems weird to go through all the disruption of changing to a= new > > > > > OS instead of a few minutes work at a console to give us what we = need > > > > > to resolve the matter -- but whatever works for you. > > > > already done some stuff like these movings... i'm familiars with th= em. > > > > it's not about a few minutes work. it's about the few hours' downti= me :) > > >=20 > > > It's a few minutes to perform the additional work at the serial > > > console when your system hangs, which is *required* for a developer to > > > help with your problem. If you're not willing to do this, there's not > > > much more we can do for you. > > i will see what can i do. a serial console may be accessable, but i'm n= ot sure. > > i will have to visit the server hotel and talk with the techies there. = we > > have two boxes there, and it may be somehow possible to connect their > > serial ports. the problem is, they are far away in the room from each o= ther. > > the hotel only gives system console(VGA+ps2 keyboard) access if i ask. = but > > this bloody box sometimes ain't even responses to that anyways, the LCD > > remains blank. >=20 > You can't even break to the debugger? well, no. currently the serial line is not configured nor connected, and the system c= onsole is not accessable. > > i'd like to solve this, but the technical opportunities are limited her= e. > > we cannot have downtime, and if we have it have to be minimized. as you= see > > clients won't accept a reasons like "sorry, we were debugging this OS we > > run at the server". > >=20 > > the question will be that, when i have a serial link, and shit happens(= tm), > > should i inspect it myself, or should i scream somewhere for a more dec= ent > > person (maybe a developer) to check it? >=20 > Did you read the developers handbook chapter I pointed you to, yet? may be. a while back i've read the developers' handbook. but yet, i haven't read that chapter, currently, i'm in a work, and have little time to share. > > > After 6.2 is release will of course be too late for you, again. If > > > the problem is not fixed by magic then you'll be in the same position > > > you are now. > > why too late? it usually go for a month with a reboot. and it should be > > released in a month. as i see, it fits into the time :) >=20 > Because (if it is a FreeBSD bug) then you'll have more work to do to > apply a patch to your system, and also it won't help anyone else who > might also be seeing the problem, until 6.3-RELEASE in ~6 months. probably you won't see this bug for a few weeks. it happens in 4-6 weeks' time usually. and till that, 6.2 comes out. And we will anyway update to 6.2-RELEASE after it come out. As i had stated, it's not an everyday issue, it just happens from time-to-time, irregularly, inpredictable. Bye, Gergely Czuczy mailto: gergely.czuczy@harmless.hu --=20 Weenies test. Geniuses solve problems that arise. --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) owGNV8+PHEcVNrZyaSlCPkRcSwFpvHZPM7Nr71oTrY29u0SWww/h4MiBS0336+nK dFe1q6q33T7kGiQ4RFxBiAtHJCTyNwQu5IaUv4QrfK+qe3YXJQHJWnm7qr5673vf +17tp2/euHb95hd/+ewXd37z2999689vLtd7Tee93swbac+Vni8Xi+X83tHycH9+ f76kA3nvMC+lXN7N7589/+7zE6M9aT9/f2hpJTy98t9va6n0OyKvpHXkjztfzu8n 075T5VrjlFdGr4TStdK0W3vfSu1KsvMznZtC6c1KvOyMp2LeWqW9XNeUJD/R4pn0 qfixORfLZSr2F4tDIb1Y7K+WR6uDg5/+SMwX9xaLVDy1yomnpLXs5SB6C6RV8kB8 LcD91fJgtb8PgDuLJQO8S3ZD9SBOPvz5yYcvLhC+AWN/hX93D/9nEN8IcrS6d7S6 e/T/BPLgeH8xwgXIp6lwRI0TPSlbCG/ExghfWdNtKiHrGv8nUShnu5ZLIEzJddIb kM2b5XEiNPWXEZ+hSs6TLHivFCX1olG684Q7jN1ywFLkRjtTU7hPnZPosFhhpSdx nGii4hIi9ljCbmzjYBrpPVkxn4t158MpOsfvjO1EaawYTJftjsvaIpRBFEaTcKbB D9+VpajVNsA5ABrIduOyLBNq1ohSNqpWkKLola+w5zih5gJQ+ZkT2iCJten8VySY xS1xmQPmDZXprJshil57dZwgjNXef9fjSTh2BQ+pt2SRVBOQZFGERpD1jkr+7Mgq WY8oE7N9RZqpsMINKEcjuGouxXeVVwIau23pZacsFbcDa1IU4LE2uA/XjmAV1W2k ISC11qClmkyIJyV/mVkKVPSqrkdBFKwehXsQmKVI1QjWdLi4MTiDKudS894r9VIB iPUYxcB7FHZlCC7muMuuQW+sQUiek3Pc52lQA9dPHycIyXWWrqBW8jzI7VzBTCba WDgVeqMWUkP8st5ORcdeyivFNeBEMsiyp4AXgXoj1ubVtJyG88Ad42KhVaYXcC6n 1lHnCF1THq5WNiCNObXGepeFO0eCxUjgICTYKiWqw2agdNhkjYFKLX6QBKPmOOEY YrK8HhMyGv3PveUmAYzc3Xr+7qM7rdsXWxrWRtpib6RRqBJkSbflZMHmCAiprGtj 0ENIOGTmVQNUePbMC2hGc3u2AI+C9Vw6qQdEHLMQ752cBixLDQ4xnNRbxBul/8J0 XOkJa41+3UYcGA+tu82G7EOQX9cpxJQleWctzB/ZXWhf8FhgUbMakWepNqh/gV/t xDsVsUjh0EgIlBIoScaTF3LKkqidWTE6hRGTA3Ft1mNrs0a0yhGAabmMnUZ/Mjco W60ahVvRQxYOEssThc9XBRVFO2gm+ZS8HhaU3+kVaoIbAOs1FWgEx+0C00WTBMS8 ViCDnYcZ5ARaNiWQ6JBbDP5tZ6wdUkbvIdaR1dCwXF049iht2+lLnoLmeDuEPVkU f3/ZkQuDIDTVmkK50+g2KgYtLxVlG1NzVciobUm7W9Brs5fGDoAv1sicR0bLzcEt NDiqy1SgdLtllyOhJoiv534bHSuYSUGoIzgIgHAv5C1uoQ/ZHi48bS+0YEX5Fnc8 nLR3qgrmk+kqRsGN+x37ZbE2ZsvzruWJ8wSdilcFxSPepGIgQMWWZ4+CtaLV15Lv mIGIr0Cd7WCzICIgpEIlzBvXbzzB3hcvTcVO7mlwN3iADOYfiQ2E18p79hgoKWGh 4h01CfiBeFRy7IfZPreHpRrCoFg8HuU8liiU0RhRY5ROjgz4DZo1WP2IdNWgQsOU 6hXoWA/wvY3KeUeYObMojdGvnMS4m95wIxYzKMP06MfOqIZdDA9ZBp3r8PwY+Dky FVvDmYM9s77Boc8m2x2Fsh5lHLMsIlnhXOgcxV2T8v5SoWVQy+gyTFyYx1EUjymX HVi5xX7oOVUpfmiJHj87Rc02e1fSDAWIQ40n8jgBeX5C7QhfilZ6uDQWLg3jWDxZ O8M3xN4Nsxa+yQ8VqrlIFcM0alP5uJUHC1Hs210pUtHBQ2pU+GD+s7P3zh49O+O8 Pz6Mibss4Y3wtCGQHu/iERudvduM9PKzoyfaukxc9Coj3Z0fxoVZEogaCxO59yo8 EdkCWGK54cmAh08mHmG1H5UWp4Ho2oIVBnawdxesDAJVPhwez7rgJfANL4NxXzy6 NE8JOxQ8Dp3rKE1w8qPOXYQcJiNHOvdmHt1VoYU2XS1t6CLdYjSo3I8+/3gASLJ7 Mb/u8tcDmlrV3qzEJn7O8vD5B+ispsaIyKouSeZz1ssHRDo8E+CLGR7eWnU8COO0 GGvkxqGIpz1u/NXDG29c4z+Fpr+ibl7//B/Xfv/t6y/+/dGX1ad/+s5njVJ/+PUn b/3zjWt//OuX73z+wb9ufu/jv18//eJvq5Mbt4tf/gc= =4pox -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 12 10:18:43 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA1BA16A407 for ; Sun, 12 Nov 2006 10:18:43 +0000 (UTC) (envelope-from thyes@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id E8B0043D5F for ; Sun, 12 Nov 2006 10:18:42 +0000 (GMT) (envelope-from thyes@gmx.net) Received: (qmail invoked by alias); 12 Nov 2006 10:18:39 -0000 Received: from port-212-202-73-168.dynamic.qsc.de (EHLO gator.homeunix.org) [212.202.73.168] by mail.gmx.net (mp040) with SMTP; 12 Nov 2006 11:18:39 +0100 X-Authenticated: #9364917 Received: from gator.mars (localhost [127.0.0.1]) by gator.homeunix.org (Postfix) with ESMTP id C31913B69 for ; Sun, 12 Nov 2006 11:18:38 +0100 (CET) Received: (from thyes@localhost) by gator.mars (8.13.6/8.13.1/Submit) id kACAIcI8007571 for freebsd-hackers@freebsd.org; Sun, 12 Nov 2006 11:18:38 +0100 (CET) (envelope-from thyes) Date: Sun, 12 Nov 2006 11:18:38 +0100 From: Frank Thyes Cc: freebsd-hackers@freebsd.org Message-ID: <20061112101838.GA7384@gator> References: <20061111172731.GB39999@harmless.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061111172731.GB39999@harmless.hu> User-Agent: Mutt/1.4.2.1i Priority: normal X-Y-GMX-Trusted: 0 Subject: Re: system randomly freezes X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 10:18:43 -0000 Hi Gergely, +++ Gergely CZUCZY [Sat, Nov 11, 2006 at 06:27:31PM CET]: > > I have sent this as a PR, but Remko Lodder suggested that > it should be discuessed here. I have seen several other > examples to very similar unstability issues in the mailing > lists previously. When i have posted this to -questions@ > there also was a person who said he has fimilar behaviours > sometimes. > > so, here it goes: > >Environment: > System: FreeBSD marvin.harmless.hu 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: Mon Oct 2 14:54:14 CEST 2006 root@marvin.harmless.hu:/usr/obj/usr/src/sys/MARVIN i386 I am experiencing the same problem on super micro boxes. The system simply stops responding. No ping, no crash dump, no entry in syslog. The solution was quiet easy. After replacing the dimms everthing was fine. Unfortunately the 5013C-MT did not have DMI event logging. Regards Frank -- mal doof in die runde gefragt. lese hier oft von brain 1.0 oder auch 2.8 wenn es um antivirusprogs geht. was is das? is das gut? kann mans kaufen? Paul Berner in d.c.s.m From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 12 11:07:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD65F16A417; Sun, 12 Nov 2006 11:07:17 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.t-hosting.hu (server.t-hosting.hu [217.20.133.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id D302F43D99; Sun, 12 Nov 2006 11:07:03 +0000 (GMT) (envelope-from gabor@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by server.t-hosting.hu (Postfix) with ESMTP id 13DB19A1B2C; Sun, 12 Nov 2006 12:07:01 +0100 (CET) X-Virus-Scanned: amavisd-new at t-hosting.hu Received: from server.t-hosting.hu ([127.0.0.1]) by localhost (server.t-hosting.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id UzntJhMFu2fP; Sun, 12 Nov 2006 12:06:55 +0100 (CET) Received: from [192.168.2.186] (catv-50635cb6.catv.broadband.hu [80.99.92.182]) by server.t-hosting.hu (Postfix) with ESMTP id 8B90A9A1B2E; Sun, 12 Nov 2006 12:06:55 +0100 (CET) Message-ID: <4557004A.5070105@FreeBSD.org> Date: Sun, 12 Nov 2006 12:06:50 +0100 From: =?UTF-8?B?R8OhYm9yIEvDtnZlc2TDoW4=?= User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Attilio Rao References: <1162993001.4305.37.camel@massimo.datacode.it> <4553A000.7070407@FreeBSD.org> <1163151468.4328.6.camel@massimo.datacode.it> <200611101459.20117.max@love2party.net> <3bbf2fe10611100747l386a624cpd72d04b62a0681e7@mail.gmail.com> <3bbf2fe10611100751i77e9c8afle0aed1e794062f4f@mail.gmail.com> <3bbf2fe10611101149y72f29285s517f5e40a5b8f3e0@mail.gmail.com> <3bbf2fe10611101157p13296002ic974d45c3fe95e09@mail.gmail.com> In-Reply-To: <3bbf2fe10611101157p13296002ic974d45c3fe95e09@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Max Laier , freebsd-net@freebsd.org, Massimo Lusetti , Florent Thoumie , freebsd-hackers@freebsd.org Subject: Re: New wpi driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 11:07:17 -0000 Attilio Rao wrote: >> First of all, WPI_PCI_BAR0 might not be defined in this way, but it >> should really use PCIR_BAR() macro. >> Then, probabilly, gabor's device I/O space is relative to another BAR, >> so simply try all 6 using PCIR_BAR(n) where n range is 0-6 until it >> does allocate. > > Sorry, n ranges 0-5... (as I said before 6 different address spaces). > Today it seems I'm absolutely sleeping... (probabilly I'm too angry to > have not parecipied at EuroBSDCon...). > > Attilio > > If I could understand your instructions correctly, I had to change the line sc->mem_rid = WPI_PCI_BAR0 to sc->mem_rid = PCIR_BAR(n) with all the possible n values from 0 to 5. I tried that but it lead nowhere, I still got the same output. If you can ping me on IRC this afternoon, too, I can give you ssh access if you want to take a look. -- Cheers, Gabor From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 12 07:29:19 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C5D416A407 for ; Sun, 12 Nov 2006 07:29:19 +0000 (UTC) (envelope-from trowa-4@yahoo.com.tw) Received: from web72002.mail.tp2.yahoo.com (web72002.mail.tp2.yahoo.com [203.188.200.32]) by mx1.FreeBSD.org (Postfix) with SMTP id 00C3643D46 for ; Sun, 12 Nov 2006 07:29:17 +0000 (GMT) (envelope-from trowa-4@yahoo.com.tw) Received: (qmail 48986 invoked by uid 60001); 12 Nov 2006 07:29:16 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.tw; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=ykgvaca8VtxoUe623LXW1ftgFSYi+75zYE4CBEzpXY0zXUJiaFpStGCtLqsj1qCjNWvr+3A/Sd+SqiIMJv/jbcTvFYcgbSdeo403KOXHC10R7R/TfNKARmUI7vWh5qXLEN0H4t0MV1y1i36BN6612JNM9UBwa+sPl1vgJ1H/ros=; X-YMail-OSG: wsW4JucVM1m1D7a82V_ma5xNE8lldgNdoWJc893hp94B5rgsk.7tGNo4OzZQg0qzKgBm8Cgko6yYnaaLj9E810TbpFX0dFNfBppZpK5shGL7a_7Vu5HmV6xIMECHz_FdqZi6rojAVfJTekUysRa6y.cAgqfnXXHcY9mwswo_N9K4DnqpeVW_F7mKYfzh Received: from [61.56.138.188] by web72002.mail.tp2.yahoo.com via HTTP; Sun, 12 Nov 2006 15:29:16 CST Date: Sun, 12 Nov 2006 15:29:16 +0800 (CST) From: "Wenyen, Shih" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit Message-ID: <546973.48245.qm@web72002.mail.tp2.yahoo.com> X-Mailman-Approved-At: Sun, 12 Nov 2006 12:39:04 +0000 Subject: signal design questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 07:29:19 -0000 Hi all, I have some questions. (1) I know how to delivery of a signal to a process. 1. The kernel places a signal context on the user's stack.(user level) 2. The kernel places a signal-handler frame on the user's stack.(kernel level) 3. The user's signal handler returns to the sigtramp() routine, which pops the signal-handler context from the user's stack.(user level) 4. The sigtramp() routine finishes by calling the sigreturn system call. But, why don't implement signal handler routine in kernel level? Are there having any ideas to implement signal handler routine in kernel level? (2) The system-call exit code first checks for a posted signal and check to see whether any process has a priority higher than that of the currently running process. But, I don't know the signal be checked when returning from kernel mode to user mode. Anyone have other methods to checked the signal in the other occasion ? Thanks, Wenyen ___________________________________________________ 您的生活即時通 － 溝通、娛樂、生活、工作一次搞定！ http://messenger.yahoo.com.tw/ From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 12 17:43:33 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B24AC16A403 for ; Sun, 12 Nov 2006 17:43:33 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from rwcrmhc15.comcast.net (rwcrmhc15.comcast.net [204.127.192.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C08943D60 for ; Sun, 12 Nov 2006 17:43:33 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from gimpy (c-24-118-173-219.hsd1.mn.comcast.net[24.118.173.219]) by comcast.net (rwcrmhc15) with ESMTP id <20061112174332m1500ap0f5e>; Sun, 12 Nov 2006 17:43:32 +0000 From: Josh Paetzel To: hackers@freebsd.org Date: Sun, 12 Nov 2006 12:43:22 -0500 User-Agent: KMail/1.9.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611121143.22391.josh@tcbug.org> Cc: Subject: Epic5-0.3.1 ruby support and FreeBSD AMD64 problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 17:43:33 -0000 I'm the port maintainer for irc/epic4 and irc/epic5 and try to liason with the developers as much as possible. I've received a request from the Epic developers that I can't really help with and I'm wondering if someone would be willing to be able to lend them a hand. Epic5-0.3.1 includes optional ruby support. When ruby support is compiled in on an AMD64 box attempting to use gdb on it spontainiously reboots the box, no panic, no hang, just a hard reset. The problem has been verified to occur on 5-STABLE and 6-STABLE on multiple machines. It does not occur if the gdb from devel/gdb6 is used. At the moment I'm dealing with the situation by keeping the port at 5.0.2.0 but I'm getting more and more requests to get 0.3.1 into the tree. Given the nature of the problem doing so at this point means either not having the ruby support in the port or marking it broken for AMD64, neither of which are particularly attractive. Any level of help would be appreciated, whether it's just a 'here's what I would look for first" all the way up to digging into some code. I'd rather not post email addresses to the list but if a kind soul wishes to get in contact with the epic team I can give contact info out privately. Another (possibly useful) data point that occurs to me is that it hasn't been tested on any sort of 64 bit linux at all, so it's really unknown if this is FBSD specific. -- Thanks, Josh Paetzel From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 12 21:12:52 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 825E516A494 for ; Sun, 12 Nov 2006 21:12:52 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id ED45843D53 for ; Sun, 12 Nov 2006 21:12:51 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 53653 invoked by uid 1001); 12 Nov 2006 21:13:56 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Sun, 12 Nov 2006 16:13:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17751.36500.33990.809115@bhuda.mired.org> Date: Sun, 12 Nov 2006 16:13:56 -0500 To: Josh Paetzel In-Reply-To: <200611121143.22391.josh@tcbug.org> References: <200611121143.22391.josh@tcbug.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: hackers@freebsd.org Subject: Re: Epic5-0.3.1 ruby support and FreeBSD AMD64 problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 21:12:52 -0000 In <200611121143.22391.josh@tcbug.org>, Josh Paetzel typed: > I'm the port maintainer for irc/epic4 and irc/epic5 and try to liason > with the developers as much as possible. I've received a request > from the Epic developers that I can't really help with and I'm > wondering if someone would be willing to be able to lend them a hand. > > Epic5-0.3.1 includes optional ruby support. When ruby support is > compiled in on an AMD64 box attempting to use gdb on it > spontainiously reboots the box, no panic, no hang, just a hard reset. > The problem has been verified to occur on 5-STABLE and 6-STABLE on > multiple machines. It does not occur if the gdb from devel/gdb6 is > used. > > At the moment I'm dealing with the situation by keeping the port at > 5.0.2.0 but I'm getting more and more requests to get 0.3.1 into the > tree. Given the nature of the problem doing so at this point means > either not having the ruby support in the port or marking it broken > for AMD64, neither of which are particularly attractive. Why not test for both conditions? I.e. - if ruby support is included (you did say it was optional) AND if you're on amd64, then mark the port as broken? Better yet, since using devel/gdb6 seems to fix the problem, use devel/gdb6 under those conditions. Or - to keep it simple - always use devel/gdb6. Note that getting this problem fixed won't meean you can ignore it. If you want to avoid building with the workaround (whatever that may be) on amd64 after the fix has been committed, you'll have to check the OS version, and optionally build with the workaround if someone is installing the fix on an earlier version of FreeBSD. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 12 22:03:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 797AD16A494 for ; Sun, 12 Nov 2006 22:03:38 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15AD443D5F for ; Sun, 12 Nov 2006 22:03:33 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from gimpy (c-24-118-173-219.hsd1.mn.comcast.net[24.118.173.219]) by comcast.net (rwcrmhc12) with ESMTP id <20061112220332m1200ksqm9e>; Sun, 12 Nov 2006 22:03:32 +0000 From: Josh Paetzel To: freebsd-hackers@freebsd.org Date: Sun, 12 Nov 2006 17:03:21 -0500 User-Agent: KMail/1.9.3 References: <200611121143.22391.josh@tcbug.org> <17751.36500.33990.809115@bhuda.mired.org> In-Reply-To: <17751.36500.33990.809115@bhuda.mired.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200611121603.22085.josh@tcbug.org> Cc: Mike Meyer Subject: Re: Epic5-0.3.1 ruby support and FreeBSD AMD64 problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Nov 2006 22:03:38 -0000 On Sunday 12 November 2006 15:13, Mike Meyer wrote: > In <200611121143.22391.josh@tcbug.org>, Josh Paetzel=20 typed: > > I'm the port maintainer for irc/epic4 and irc/epic5 and try to > > liason with the developers as much as possible. I've received a > > request from the Epic developers that I can't really help with > > and I'm wondering if someone would be willing to be able to lend > > them a hand. > > > > Epic5-0.3.1 includes optional ruby support. When ruby support is > > compiled in on an AMD64 box attempting to use gdb on it > > spontainiously reboots the box, no panic, no hang, just a hard > > reset. The problem has been verified to occur on 5-STABLE and > > 6-STABLE on multiple machines. It does not occur if the gdb from > > devel/gdb6 is used. > > > > At the moment I'm dealing with the situation by keeping the port > > at 5.0.2.0 but I'm getting more and more requests to get 0.3.1 > > into the tree. Given the nature of the problem doing so at this > > point means either not having the ruby support in the port or > > marking it broken for AMD64, neither of which are particularly > > attractive. > > Why not test for both conditions? I.e. - if ruby support is > included (you did say it was optional) AND if you're on amd64, then > mark the port as broken? Better yet, since using devel/gdb6 seems > to fix the problem, use devel/gdb6 under those conditions. Or - to > keep it simple - always use devel/gdb6. > > Note that getting this problem fixed won't meean you can ignore it. > If you want to avoid building with the workaround (whatever that > may be) on amd64 after the fix has been committed, you'll have to > check the OS version, and optionally build with the workaround if > someone is installing the fix on an earlier version of FreeBSD. > > X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC27E16AEA3 for ; Mon, 13 Nov 2006 09:29:15 +0000 (UTC) (envelope-from gonzalo.arana@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 612D943D67 for ; Mon, 13 Nov 2006 09:29:14 +0000 (GMT) (envelope-from gonzalo.arana@gmail.com) Received: by nf-out-0910.google.com with SMTP id l23so405769nfc for ; Mon, 13 Nov 2006 01:29:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZN/etSScpJ5Sv08aom2OXpn5nqkvnLuA7HnBZuxwLIkJ6wRgF2+4DdtkaC1N5aiW1kVEF5G9WQ5EY+iIthksTJ1hJwBeBmRxetmV/CXtUbT8np/DdhOoPc0nhnDCxfazaFfcDzkQpW7bCv1ej8Zh+Dio9PWbfTHY0aG5nSBQOKU= Received: by 10.82.152.16 with SMTP id z16mr592564bud.1163406779903; Mon, 13 Nov 2006 00:32:59 -0800 (PST) Received: by 10.82.165.13 with HTTP; Mon, 13 Nov 2006 00:32:59 -0800 (PST) Message-ID: Date: Mon, 13 Nov 2006 05:32:59 -0300 From: "Gonzalo Arana" To: freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Subject: Re: net/mpd causes a kernel freeze X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 09:29:15 -0000 Hi, Forgot to mention that I've already opened a problem report, but I was directed here by Remko Lodder. Any ideas on how to solve or tackle this issue? On 11/6/06, Gonzalo Arana wrote: > Hi, > > When I open a pptp tunnel with net/mpd, my PC freezes (numlock stops > responding, for instance). > > I am using 6.1-RELEASE with GENERIC kernel. I've recompiled removing > USB, SCSI/RAID controllers, with the same result. > > The freeze occurs right after the tunnel is up. > > Does anyone expierence the same problem? > > Here are the relevant configs: > > > /usr/local/etc/mpd/mpd.conf: > > > > default: > > load vpn > > > > vpn: > > new -i ng0 vpn vpn > > set iface disable on-demand > > set iface idle 0 > > # disconnect the client after 8 hours > > set iface session 28800 > > #set iface route 192.168.2.0/24 > > set bundle disable multilink > > set bundle authname my_username > > set bundle password my_password > > set link yes acfcomp protocomp > > set link no pap chap > > set link accept pap > > set link mtu 1460 > > # If remote machine is NT you need this.. > > # set link enable no-orig-auth > > set link keep-alive 10 75 > > set ipcp no vjcomp > > > > /usr/local/etc/mpd/mpd.links: > > vpn: > > set link type pptp > > set pptp self ZZZ > > set pptp peer YYY > > set pptp enable originate incoming outcall > > set pptp disable windowing > > > > > > where: > > ZZZ my ethernet IP address > > YYY ip address of TCP peer > > > > Thank you very much in advance, > > -- > Gonzalo A. Arana > -- Gonzalo A. Arana From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 13 15:35:03 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E8C9216A415 for ; Mon, 13 Nov 2006 15:35:03 +0000 (UTC) (envelope-from erik.u@dnainternet.net) Received: from isolokki.dnainternet.net (isolokki.dnainternet.net [212.149.75.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AFDF43D58 for ; Mon, 13 Nov 2006 15:35:03 +0000 (GMT) (envelope-from erik.u@dnainternet.net) Received: from [192.168.1.11] (host-212-149-187-177.kpylaajakaista.net [212.149.187.177]) by isolokki.dnainternet.net (Postfix) with ESMTP id BB08FD55A for ; Mon, 13 Nov 2006 17:35:01 +0200 (EET) Message-ID: <455890A5.7090506@dnainternet.net> Date: Mon, 13 Nov 2006 17:35:01 +0200 From: Erik Udo User-Agent: Thunderbird 1.5.0.7 (X11/20061024) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: unionfs in livecd? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 15:35:04 -0000 I was thinking of making a personal livecd for my own use. So, how is unionfs? I heard it's still buggy especially if you mount multiple memory devices. I found a link to a patch from the freesbie-projects website that somehow patches the current. http://people.freebsd.org/%7Edaichi/unionfs/ Should i use this? Can i mount one singe memory device on top of the root-directory? I'd want my whole system writeable. If not, then can aynone please tell me how i can have a stable, writeable livecd. I'm thinking of using FreeBSD 6.2 Thanks, Erik From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 13 17:04:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4821A16A40F for ; Mon, 13 Nov 2006 17:04:35 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E87243D62 for ; Mon, 13 Nov 2006 17:02:47 +0000 (GMT) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=hCx5L3RcPZ7YhCdpYdeW7FtU/lqFy+FzpYzLnaYDzMZu4YKxdKsjLO1XYE41RTBl3XghauYJr+qnwDgpybjZMGLD7bkRGTaV+3muT2cCUYQrF8djBRzqKETO1a3TZ5nhpN9fs/HYwws1KUEeMRUfs/wJ/cqJUQRGcJi2shaLg2I=; Received: from codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1GjfCb-000D3Y-FP; Mon, 13 Nov 2006 20:02:33 +0300 Date: Mon, 13 Nov 2006 20:02:26 +0300 From: Eygene Ryabinkin To: Erik Udo Message-ID: <20061113170226.GP1044@codelabs.ru> References: <455890A5.7090506@dnainternet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <455890A5.7090506@dnainternet.net> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.1 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_20 Cc: freebsd-hackers@freebsd.org Subject: Re: unionfs in livecd? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 17:04:35 -0000 Erik, good day! > So, how is unionfs? I heard it's still buggy especially if you mount multiple > memory devices. At least in 6.2-BETA the original unionfs leads to random locks for disk-based partitions. I can reproduce it in 15-30 minutes of using unionfs-mounted filesystem. > I found a link to a patch from the freesbie-projects website that somehow > patches the current. > http://people.freebsd.org/%7Edaichi/unionfs/ > Should i use this? The unionfs patchsets from Daichi Goto are very good, at least for me: I've not expirienced any lockups since 6.1. So, you probably should give it a try. My usage of unionfs-mounted filesystems is connected with sequentially serving large data transfers (about 2 Gb in a couple of minutes) to a moderate number of clients (aroung 100). These transfers are not frequent, but as they go they can produce a huge load spike to a server's filesystem. Such spikes are definitely locking up the filesystem with the original unionfs. -- Eygene From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 13 17:17:55 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6E5616A4E5 for ; Mon, 13 Nov 2006 17:17:55 +0000 (UTC) (envelope-from matteo@freebsd.org) Received: from vsmtp3.tin.it (vsmtp3alice.tin.it [212.216.176.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AF1743F38 for ; Mon, 13 Nov 2006 17:12:01 +0000 (GMT) (envelope-from matteo@freebsd.org) Received: from kaiser.sig11.org (87.4.189.48) by vsmtp3.tin.it (7.2.072.1) id 453F6B07006C9F1B; Mon, 13 Nov 2006 18:11:59 +0100 Received: from kaiser.sig11.org (rionda@localhost [127.0.0.1]) by kaiser.sig11.org (8.13.8/8.13.8) with ESMTP id kADHBwuX002472; Mon, 13 Nov 2006 18:11:58 +0100 (CET) (envelope-from matteo@freebsd.org) Received: (from rionda@localhost) by kaiser.sig11.org (8.13.8/8.13.8/Submit) id kADHBvUw002471; Mon, 13 Nov 2006 18:11:57 +0100 (CET) (envelope-from matteo@freebsd.org) X-Authentication-Warning: kaiser.sig11.org: rionda set sender to matteo@freebsd.org using -f Date: Mon, 13 Nov 2006 18:11:57 +0100 From: Matteo Riondato To: Erik Udo Message-ID: <20061113171157.GB2343@kaiser.sig11.org> Mail-Followup-To: Matteo Riondato , Erik Udo , freebsd-hackers@freebsd.org References: <455890A5.7090506@dnainternet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kXdP64Ggrk/fb43R" Content-Disposition: inline In-Reply-To: <455890A5.7090506@dnainternet.net> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org Subject: Re: unionfs in livecd? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 17:17:55 -0000 --kXdP64Ggrk/fb43R Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 13, 2006 at 05:35:01PM +0200, Erik Udo wrote: > I was thinking of making a personal livecd for my own use. >=20 > So, how is unionfs? I heard it's still buggy especially if you mount=20 > multiple memory devices. >=20 > I found a link to a patch from the freesbie-projects website that=20 > somehow patches the current. > http://people.freebsd.org/%7Edaichi/unionfs/ > Should i use this? >=20 > Can i mount one singe memory device on top of the root-directory? I'd=20 > want my whole system writeable. >=20 > If not, then can aynone please tell me how i can have a stable,=20 > writeable livecd. Use the FreeSBIE scripts to build it.=20 As a side note, in FreeSBIE 2.0-BETA we're not using unionfs at the moment so only some parts of the system are writable. Anyway it is possibile to build an ISO image that uses unionfs (and I'll probably release an ISO image with unionfs enabled in the near future.) Best Regards --=20 Matteo Riondato FreeBSD Committer (http://www.freebsd.org) G.U.F.I. Staff Member (http://www.gufi.org) FreeSBIE Developer (http://www.freesbie.org) --kXdP64Ggrk/fb43R Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFWKdd2Mp4pR7Fa+wRAjLxAJ4iks5cZVqQ3ggdqCu+BDyBu/JIbwCfZ6Bl B+0f7Zw+p1ydSUoIZ/zAnsY= =Y2wF -----END PGP SIGNATURE----- --kXdP64Ggrk/fb43R-- From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 13 18:54:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F193116A548 for ; Mon, 13 Nov 2006 18:54:52 +0000 (UTC) (envelope-from raymond@sundland.com) Received: from mail.omnimx.net (mail.omnimx.net [64.235.254.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91F4B43D77 for ; Mon, 13 Nov 2006 18:49:06 +0000 (GMT) (envelope-from raymond@sundland.com) Received: from P644RSI (mail [64.235.254.12]) by mail.omnimx.net (Postfix) with ESMTP id EB43617091 for ; Mon, 13 Nov 2006 10:48:40 -0800 (PST) From: "Raymond Sundland" To: , Date: Mon, 13 Nov 2006 13:48:39 -0500 Message-ID: <003401c70754$56a85c30$8478020a@medco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Thread-Index: AccHMuzD8J2Wck5cSk6AO3wS7cL3yAAIS2Lw Cc: Subject: FW: IPMI kernel module errors on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 18:54:53 -0000 I sent this to -questions earlier, but thought I would get a more complete response from either -hackers or -amd64. ... Hi Everyone, I purchased a new Supermicro Superserver SS6015B-T (motherboard is X7DBR-E) about 3 weeks ago with the IPMI module (part called SIMSO) and have had a hard time getting the IPMI functionality to work in RELENG_6. Particularly, when I attempt to 'kldload ipmi' I get the following output in dmesg: ipmi0: on isa0 ipmi0: KCS mode found at mem 0xca2 alignment 0x4 on isa ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: Timed out waiting for GET_DEVICE_ID >From the dmesg, it appears it's finding the IPMI device, but unable to interact with it. Meanwhile, no device shows up in /dev so ipmitool does not work, either. For reference, here is my uname: FreeBSD exodus 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #9: Fri Nov 10 10:56:39 PST 2006 root@exodus:/usr/obj/usr/src/sys/EXODUS amd64 This is a RELENG_6 build with a CVSUP done just before the compile date of the kernel. The SIMSO IPMI card itself works, I can access it via the web management console, I just can not get the kernel driver to work with it. Any help and/or references would be greatly appreciated. Thanks! _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 07:22:33 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFC2616A407 for ; Tue, 14 Nov 2006 07:22:33 +0000 (UTC) (envelope-from gurdiga@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FCF443D46 for ; Tue, 14 Nov 2006 07:22:22 +0000 (GMT) (envelope-from gurdiga@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1357133wxc for ; Mon, 13 Nov 2006 23:22:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=MrhEeIbPxWsL+BNlLtJb7zE3ORVRIvbt4fD5nD6MlTfHBcUSSOyzYoiRWCURL3Gn2PzSXaiH0wbBPJ6qzbohaQrogSHaWadlmLdQPIKWiBe/Ek1ndXWBtL/GSx/DW1MuQ2ZCqEMDo1sAfTVp7mEIbh+Q3K+22p+7dZIrr+c2Cis= Received: by 10.90.25.7 with SMTP id 7mr624594agy.1163488942439; Mon, 13 Nov 2006 23:22:22 -0800 (PST) Received: by 10.90.120.15 with HTTP; Mon, 13 Nov 2006 23:22:22 -0800 (PST) Message-ID: Date: Tue, 14 Nov 2006 09:22:22 +0200 From: "Vlad GURDIGA" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Tue, 14 Nov 2006 12:32:23 +0000 Subject: bpf kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 07:22:33 -0000 Hello, I posted the same question on freebsd-questions list but did not get an exact answer, so, I'm going on with my "research". :) I'm trying to keep very close touch with 6.1_STABLE cvsupping sources once a week or even more often. I'm thinking of removing as much as possible devices from the kernel loading them from /boot/loader.conf instead, so I could rebuild and install them without a whole kernel/world rebuild and reboot when sources change. I'm not sure this is a correct way, any piece of advice regarding this would be highly appreciated. :) So, I've successfully done that with sound and network card drivers, but did not succeed with removing bpf from the kernel. Booting a kernel with no bpf support, and with ng_bpf_load="YES" in my loader.conf [which, I found on the questions list that is not what I need], the pflogd fails to start with this error: Nov 11 20:22:33 uxterm pflogd[10251]: Failed to initialize: (no devices found) /dev/bpf0: No such file or directory Nov 11 20:22:33 uxterm pflogd[10251]: Exiting, init failure And, tcpdump also fails saying that "no suitable device found". Of course there is no /dev/bpf0. Is there any way to have the bpf0 device without booting a kernel with bpf device included? From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 09:27:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A7D616A407 for ; Tue, 14 Nov 2006 09:27:16 +0000 (UTC) (envelope-from Pradeep.Nallimelli@caviumnetworks.com) Received: from smtp2.caviumnetworks.com (smtp2.caviumnetworks.com [209.113.159.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDD6243D49 for ; Tue, 14 Nov 2006 09:27:15 +0000 (GMT) (envelope-from Pradeep.Nallimelli@caviumnetworks.com) Received: from exch4.caveonetworks.com (Not Verified[192.168.16.23]) by smtp2.caviumnetworks.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Tue, 14 Nov 2006 04:11:25 -0500 Received: from [192.168.190.50] ([202.63.105.146]) by exch4.caveonetworks.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Nov 2006 01:11:33 -0800 Message-ID: <45598914.9080009@caviumnetworks.com> Date: Tue, 14 Nov 2006 14:45:00 +0530 From: pnallimelli User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 14 Nov 2006 09:11:34.0164 (UTC) FILETIME=[E184AD40:01C707CC] X-Mailman-Approved-At: Tue, 14 Nov 2006 12:32:45 +0000 Subject: Need help in solving a crash when doing ping flood X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 09:27:16 -0000 Hi, When i m doing ping flood , i m getting crash after 15 mins. The debug messages are like this: NU gdb 5.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD at physical address 0x00579000 initial pcb at physical address 0x004a58a0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x50a10800 fault code = supervisor read, page not present instruction pointer = 0x8:0xc1b177a9 stack pointer = 0x10:0xcd6ccc64 frame pointer = 0x10:0xcd6ccccc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1088 (ping) interrupt mask = net tty trap number = 12 panic: page fault syncing disks... done Uptime: 10m15s dumping to dev #ad/0x20011, offset 1558871 #0 0xc023d9da in dumpsys () (kgdb) where #0 0xc023d9da in dumpsys () #1 0xc023d7ab in boot () #2 0xc023dbd0 in poweroff_wait () #3 0xc03addfa in trap_fatal () #4 0xc03adacd in trap_pfault () #5 0xc03ad68b in trap () #6 0xc1b177a9 in ?? () #7 0xc0283006 in ether_output_frame (ifp=0xc1b1a840, m=0xc0c03900) at ../../net/if_var.h:290 #8 0xc0282d36 in ether_output (ifp=0xc1b1a840, m=0xc0c03900, dst=0xcd07ff00, rt0=0xc1b1ee00) at ../../net/if_ethersubr.c:370 #9 0xc029769d in ip_output (m0=0xc0c03900, opt=0x0, ro=0xcd07fefc, flags=32, imo=0x0, inp=0xcd07fec0) at ../../netinet/ip_output.c:1004 #10 0xc0298f3a in rip_output (m=0xc0c03900, so=0xcca53340, dst=34212362) at ../../netinet/raw_ip.c:299 #11 0xc02993e3 in rip_send (so=0xcca53340, flags=0, m=0xc0c03900, nam=0xc134a770, control=0x0, p=0xcc04b220) at ../../netinet/raw_ip.c:630 #12 0xc025cc6b in sosend () #13 0xc026022f in sendit () #14 0xc0260332 in sendto () #15 0xc03ae0a9 in syscall2 () #16 0xc039f0c5 in Xint0x80_syscall () #17 0x80492e1 in ?? () I feel my start() function is having problem. Could anyone tell me the reason behind this?? Thanks, pradeep From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 13:02:57 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEE4B16A417 for ; Tue, 14 Nov 2006 13:02:57 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E20A243D46 for ; Tue, 14 Nov 2006 13:02:56 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 4413 invoked from network); 14 Nov 2006 12:55:37 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 14 Nov 2006 12:55:37 -0000 Message-ID: <4559BE7F.2070607@freebsd.org> Date: Tue, 14 Nov 2006 14:02:55 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: pnallimelli References: <45598914.9080009@caviumnetworks.com> In-Reply-To: <45598914.9080009@caviumnetworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Need help in solving a crash when doing ping flood X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 13:02:57 -0000 pnallimelli wrote: > Hi, > When i m doing ping flood , i m getting crash after 15 mins. > The debug messages are like this: > > NU gdb 5.18 (FreeBSD) > Copyright 1998 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-unknown-freebsd"... > IdlePTD at physical address 0x00579000 > initial pcb at physical address 0x004a58a0 > panicstr: page fault > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x50a10800 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc1b177a9 > stack pointer = 0x10:0xcd6ccc64 > frame pointer = 0x10:0xcd6ccccc > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 1088 (ping) > interrupt mask = net tty > trap number = 12 > panic: page fault > > syncing disks... > done > Uptime: 10m15s > dumping to dev #ad/0x20011, offset 1558871 > #0 0xc023d9da in dumpsys () > (kgdb) where > #0 0xc023d9da in dumpsys () > #1 0xc023d7ab in boot () > #2 0xc023dbd0 in poweroff_wait () > #3 0xc03addfa in trap_fatal () > #4 0xc03adacd in trap_pfault () > #5 0xc03ad68b in trap () > #6 0xc1b177a9 in ?? () > #7 0xc0283006 in ether_output_frame (ifp=0xc1b1a840, m=0xc0c03900) > at ../../net/if_var.h:290 > #8 0xc0282d36 in ether_output (ifp=0xc1b1a840, m=0xc0c03900, > dst=0xcd07ff00, > rt0=0xc1b1ee00) at ../../net/if_ethersubr.c:370 > #9 0xc029769d in ip_output (m0=0xc0c03900, opt=0x0, ro=0xcd07fefc, > flags=32, > imo=0x0, inp=0xcd07fec0) at ../../netinet/ip_output.c:1004 > #10 0xc0298f3a in rip_output (m=0xc0c03900, so=0xcca53340, dst=34212362) > at ../../netinet/raw_ip.c:299 > #11 0xc02993e3 in rip_send (so=0xcca53340, flags=0, m=0xc0c03900, > nam=0xc134a770, control=0x0, p=0xcc04b220) at ../../netinet/raw_ip.c:630 > #12 0xc025cc6b in sosend () > #13 0xc026022f in sendit () > #14 0xc0260332 in sendto () > #15 0xc03ae0a9 in syscall2 () > #16 0xc039f0c5 in Xint0x80_syscall () > #17 0x80492e1 in ?? () > > I feel my start() function is having problem. > Could anyone tell me the reason behind this?? My magic crystall ball tells me we'd have to look at your start() function to make any guess as to why it may be failing. -- Andre From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 14:44:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C447616A415 for ; Tue, 14 Nov 2006 14:44:53 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E50643D6A for ; Tue, 14 Nov 2006 14:44:52 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 28A4F48800; Tue, 14 Nov 2006 15:44:51 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 2C1AB487F3; Tue, 14 Nov 2006 15:44:37 +0100 (CET) Date: Tue, 14 Nov 2006 15:44:30 +0100 From: Pawel Jakub Dawidek To: Pedro F Giffuni Message-ID: <20061114144430.GI36814@garage.freebsd.pl> References: <20061108013836.77606.qmail@web32713.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LQ77YLfPrO/qF/pM" Content-Disposition: inline In-Reply-To: <20061108013836.77606.qmail@web32713.mail.mud.yahoo.com> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-hackers@freebsd.org Subject: Re: SEEK_HOLE and SEEK_DATA for sparse files any takers? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 14:44:53 -0000 --LQ77YLfPrO/qF/pM Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 08, 2006 at 02:38:36AM +0100, Pedro F Giffuni wrote: > Hi; >=20 > >From http://blogs.sun.com/bonwick/date/200512 >=20 > "At this writing, SEEK_HOLE and SEEK_DATA are Solaris-specific. I encoura= ge > (implore? beg?) other operating systems to adopt these lseek(2) extensions > verbatim (100% tax-free) so that sparse file navigation becomes a ubiquit= ous > feature that every backup and archiving program can rely on. It's long > overdue." >=20 > It should be mentioned that linux adopted them and they would help the ZFS > port. I've some starting code for this and I'm planning to implement them, at least for ZFS. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --LQ77YLfPrO/qF/pM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFFWdZOForvXbEpPzQRAtzAAJ90pB5Wtu8L0caLCbTpIH+l1TbitwCgiU9h dbbTbG025JaEHVi7ceoXZlA= =U9BA -----END PGP SIGNATURE----- --LQ77YLfPrO/qF/pM-- From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 16:20:24 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EA7716A494; Tue, 14 Nov 2006 16:20:24 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 853E943F70; Tue, 14 Nov 2006 16:09:19 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.186.21] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu5) with ESMTP (Nemesis), id 0ML25U-1Gk0qT1noA-0003As; Tue, 14 Nov 2006 17:09:09 +0100 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Tue, 14 Nov 2006 17:09:20 +0100 User-Agent: KMail/1.9.4 X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<%}*_BD U_or=\mOZf764&nYj=JYbR1PW0ud>|!~, , CPC.1-D$FG@0h3#'5"k{V]a~. X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-net@freebsd.org Subject: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 16:20:24 -0000 --nextPart1529959.aSOhg96bU6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, this one is something for people who know their math. Input: 2x128bit of address (lower ~80bit selectable by user) and 2x16bit=20 of ports (more or less selectable by user). Note that the "flow_id" is=20 not useable as several broken stack implementations do not set it=20 consistently - and it is user settable as well. Output: "int" hash value - by default we use the lower 8bit of it. Problems: Most of the input can be selected by a user meaning it is easy=20 to produce collisions. For legal connections, the lower 64bit are the=20 one with the highest entropy - in fact the upper 64bit might be the same=20 for many connections coming from/going to the same subnet. This function=20 will be used for every packet that is passed to a dynamic IPFW rule, so=20 efficiency is a concern. Any ideas? Any papers that deal with this problem? ref: sys/netinet/ip_fw2.c::hash_packet6 =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1529959.aSOhg96bU6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFWeo2XyyEoT62BG0RAv5YAJ99W3lFucWxtqwM2DffEMRd9B3DIgCdG5Nh 0cHxQBrsibVS6R+saGqA0mY= =l4Hy -----END PGP SIGNATURE----- --nextPart1529959.aSOhg96bU6-- From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 16:36:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C23C16A415 for ; Tue, 14 Nov 2006 16:36:35 +0000 (UTC) (envelope-from twohey@cs.stanford.edu) Received: from smtp3.stanford.edu (smtp3.Stanford.EDU [171.67.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6802343D67 for ; Tue, 14 Nov 2006 16:36:34 +0000 (GMT) (envelope-from twohey@cs.stanford.edu) Received: from smtp3.stanford.edu (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 33C4C4C44A; Tue, 14 Nov 2006 08:36:34 -0800 (PST) Received: from keeda.stanford.edu (keeda.Stanford.EDU [171.64.72.55]) by smtp3.stanford.edu (Postfix) with ESMTP id 161ED4C29E; Tue, 14 Nov 2006 08:36:34 -0800 (PST) Received: from twohey (helo=localhost) by keeda.stanford.edu with local-esmtp (Exim 4.63) (envelope-from ) id 1Gk1H0-0002jC-0y; Tue, 14 Nov 2006 08:36:34 -0800 Date: Tue, 14 Nov 2006 08:36:33 -0800 (PST) From: Paul Twohey X-X-Sender: twohey@keeda.stanford.edu To: Max Laier In-Reply-To: <200611141709.26644.max@love2party.net> Message-ID: References: <200611141709.26644.max@love2party.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 16:36:35 -0000 On Tue, 14 Nov 2006, Max Laier wrote: > this one is something for people who know their math. > > Input: 2x128bit of address (lower ~80bit selectable by user) and 2x16bit > of ports (more or less selectable by user). Note that the "flow_id" is > not useable as several broken stack implementations do not set it > consistently - and it is user settable as well. > Output: "int" hash value - by default we use the lower 8bit of it. > > Problems: Most of the input can be selected by a user meaning it is easy > to produce collisions. For legal connections, the lower 64bit are the > one with the highest entropy - in fact the upper 64bit might be the same > for many connections coming from/going to the same subnet. This function > will be used for every packet that is passed to a dynamic IPFW rule, so > efficiency is a concern. > > Any ideas? Any papers that deal with this problem? > > ref: sys/netinet/ip_fw2.c::hash_packet6 If you are worried about users controlling which values their packets hash to you might want to look at universal hashing. People who are worried about algorithmic denial of service attacks face similar problems. A good place to start would probably be: http://www.cs.rice.edu/~scrosby/hash Paul Twohey twohey@cs From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 16:40:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6BBF16A412 for ; Tue, 14 Nov 2006 16:40:10 +0000 (UTC) (envelope-from julian@elischer.org) Received: from customer-domains.icp-qv1-irony14.iinet.net.au (customer-domains.icp-qv1-irony14.iinet.net.au [203.59.1.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 051BB43D6B for ; Tue, 14 Nov 2006 16:40:09 +0000 (GMT) (envelope-from julian@elischer.org) Received: from 203-59-110-253.dyn.iinet.net.au (HELO [192.168.3.2]) ([203.59.110.253]) by iinet-mail.icp-qv1-irony14.iinet.net.au with ESMTP; 15 Nov 2006 00:39:48 +0800 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAALd/WUXLO279VWdsb2JhbAANjDUBKw X-IronPort-AV: i="4.09,421,1157299200"; d="scan'208"; a="29083112:sNHT18233532" Message-ID: <4559F12D.4040504@elischer.org> Date: Wed, 15 Nov 2006 00:39:09 +0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.5 (X11/20060804) MIME-Version: 1.0 To: Vlad GURDIGA References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: bpf kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 16:40:10 -0000 Vlad GURDIGA wrote: > Booting a > kernel with no bpf support, and with > ng_bpf_load="YES" in my loader.conf [which, I found on the questions > list that is not what I need], the pflogd fails to start with this > error: > ng_bpf is a netgraph node that uses bpf.. not what you need [...] > Is there any way to have the bpf0 device without booting a kernel with > bpf device included? there is no bpf module on my system. I don't think it has been separated out yet.. From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 14:36:02 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AD5E16A407 for ; Tue, 14 Nov 2006 14:36:02 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C98B43D7D for ; Tue, 14 Nov 2006 14:35:59 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (hobmtu@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAEEZrK1036309; Tue, 14 Nov 2006 15:35:58 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAEEZqFr036308; Tue, 14 Nov 2006 15:35:52 +0100 (CET) (envelope-from olli) Date: Tue, 14 Nov 2006 15:35:52 +0100 (CET) Message-Id: <200611141435.kAEEZqFr036308@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, gurdiga@gmail.com In-Reply-To: X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 14 Nov 2006 15:35:58 +0100 (CET) X-Mailman-Approved-At: Tue, 14 Nov 2006 17:49:10 +0000 Cc: Subject: Re: bpf kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, gurdiga@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 14:36:02 -0000 Vlad GURDIGA wrote: > I'm trying to keep very close touch with 6.1_STABLE cvsupping sources > once a week or even more often. You mean RELENG_6_1? I don't think that makes sense, because not many changes happen to that branch. You should only cvsup if necessary, i.e. when a security fix (or otherwise critical fix) has been committed to that branch. > I'm thinking of removing as much as > possible devices from the kernel loading them from /boot/loader.conf > instead, Personally I don't think it's worth the effort. I keep most stuff static inside a big kernel. > so I could rebuild and install them without a whole > kernel/world rebuild and reboot when sources change. I'm not sure this > is a correct way, any piece of advice regarding this would be highly > appreciated. :) When you update your sources, the recommended and official way is to rebuild everything (kernel, modules, world) and reboot. Omitting any of these steps _might_ work under certain circumstances, but it can also break in various ways (either horribly or subtly, whichever creates the most damage, according to Murphy's law). > So, I've successfully done that with sound and network card drivers, > but did not succeed with removing bpf from the kernel. Booting a > kernel with no bpf support, and with > ng_bpf_load="YES" in my loader.conf [which, I found on the questions > list that is not what I need], the pflogd fails to start with this > error: There's currently no kernel module for the bpf(4) device, so you have to put it statically in your kernel if you need it. ng_bpf is a netgraph node driver, it doesn't implement /dev/bpf* devices, so it's not what you're looking for. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "A language that doesn't have everything is actually easier to program in than some that do." -- Dennis M. Ritchie From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 14:40:15 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83CA916A415 for ; Tue, 14 Nov 2006 14:40:15 +0000 (UTC) (envelope-from gurdiga@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9514143D7B for ; Tue, 14 Nov 2006 14:40:14 +0000 (GMT) (envelope-from gurdiga@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so1455847wxc for ; Tue, 14 Nov 2006 06:40:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eG/fot+itkpIhMqfKgiGkv9OLYd2nYPP+Qex5WTe29YNLhfOuRuE63wpzkq0iKz8wp+QI+BauYhVZpALfu4oJEzE8TpjPFUS26iXtJeS5Sh0l3O4pq4kmfWqly7lbDmuvSSQ+xAmRdYgreTt9SLpOuzQsTt5CL32unIWmg/FyC4= Received: by 10.90.83.14 with SMTP id g14mr981282agb.1163515213836; Tue, 14 Nov 2006 06:40:13 -0800 (PST) Received: by 10.90.120.15 with HTTP; Tue, 14 Nov 2006 06:40:13 -0800 (PST) Message-ID: Date: Tue, 14 Nov 2006 16:40:13 +0200 From: "Vlad GURDIGA" To: freebsd-hackers@freebsd.org, gurdiga@gmail.com In-Reply-To: <200611141435.kAEEZqFr036308@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200611141435.kAEEZqFr036308@lurza.secnetix.de> X-Mailman-Approved-At: Tue, 14 Nov 2006 17:49:25 +0000 Cc: Subject: Re: bpf kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 14:40:15 -0000 Thanks for the exhaustive explanation! From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 16:20:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EF3016A538 for ; Tue, 14 Nov 2006 16:20:16 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32710.mail.mud.yahoo.com (web32710.mail.mud.yahoo.com [68.142.207.254]) by mx1.FreeBSD.org (Postfix) with SMTP id BE1C1441C2 for ; Tue, 14 Nov 2006 16:09:56 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 59348 invoked by uid 60001); 14 Nov 2006 16:09:52 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=bTTwOq/lPTqJ/TsIr01P4/+YPAbwCbrW1rRWhNNZX3EiJx8+MsCyNXZt7NayAv8oicQj+wEDsP28ohE5nuG7jpFpw0op/LsvInrbHuxw4pcKLCXBqQaPIqUzvZocH+iigR9cCXX954zUR5JyNWEEZd+/yNMqeRAUvF7tglIOAdM= ; Message-ID: <20061114160952.59346.qmail@web32710.mail.mud.yahoo.com> Received: from [200.118.71.46] by web32710.mail.mud.yahoo.com via HTTP; Tue, 14 Nov 2006 17:09:52 CET Date: Tue, 14 Nov 2006 17:09:52 +0100 (CET) From: To: Pawel Jakub Dawidek In-Reply-To: <20061114144430.GI36814@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailman-Approved-At: Tue, 14 Nov 2006 17:49:34 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: SEEK_HOLE and SEEK_DATA for sparse files any takers? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 16:20:16 -0000 --- Pawel Jakub Dawidek ha scritto: ... > > I've some starting code for this and I'm planning to implement them, at > least for ZFS. > Thanks! I recall from previous postings on this list that it's a feature desired on UFS + BSDtar too. Pedro. __________________________________________________ Do You Yahoo!? Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi http://mail.yahoo.it From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 18:44:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E9D716A4C2 for ; Tue, 14 Nov 2006 18:44:02 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DDA143D5D for ; Tue, 14 Nov 2006 18:44:00 +0000 (GMT) (envelope-from uspoerlein@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so1227399uge for ; Tue, 14 Nov 2006 10:44:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to; b=Citcjsz3W13jYt4vx5neZXPCgbpnSC7jxe7rnynZCHpepcaO1zW3viD/8+3/tp2+LbtzUfJV6hMehyX7PA+ByWi1hG9aSDBqVp4R0qnEDW86D5eFtzkDBrYB3zKv7EX+pm2N4lbXZ5GrPlD9RY2XifKca4uErlOw8DbBzoFjyIA= Received: by 10.67.97.18 with SMTP id z18mr1302525ugl.1163529838604; Tue, 14 Nov 2006 10:43:58 -0800 (PST) Received: from roadrunner.q.local ( [85.180.134.32]) by mx.google.com with ESMTP id b23sm7869136ugd.2006.11.14.10.43.57; Tue, 14 Nov 2006 10:43:58 -0800 (PST) Received: from roadrunner.q.local (localhost [127.0.0.1]) by roadrunner.q.local (8.13.8/8.13.8) with ESMTP id kAEIht5i002548; Tue, 14 Nov 2006 19:43:55 +0100 (CET) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner (8.13.8/8.13.8/Submit) id kABGXPPM001688; Sat, 11 Nov 2006 17:33:25 +0100 (CET) (envelope-from uspoerlein@gmail.com) Date: Sat, 11 Nov 2006 17:33:25 +0100 From: Ulrich Spoerlein To: Gonzalo Arana Message-ID: <20061111163325.GA1414@roadrunner.q.local> Mail-Followup-To: Gonzalo Arana , freebsd-hackers@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-hackers@freebsd.org Subject: Re: net/mpd causes a kernel freeze X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 18:44:02 -0000 Gonzalo Arana wrote: > Hi, > > When I open a pptp tunnel with net/mpd, my PC freezes (numlock stops > responding, for instance). > > I am using 6.1-RELEASE with GENERIC kernel. I've recompiled removing > USB, SCSI/RAID controllers, with the same result. > > The freeze occurs right after the tunnel is up. Hi, you should build a Kernel with debugging options turned on (DDB, KDB, WITNESS, INVARIANTS, etc. see the handbook). And then enter the debugger if the freeze occurs, refer again to the handbook about kernel debugging. It may also help to turn OFF PREEMPTION, ie. remove that line from your kernel conf. Ulrich Spoerlein -- A: Yes. >Q: Are you sure? > >A: Because it reverses the logical flow of conversation. > >>Q: Why is top posting frowned upon? From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 19:09:32 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB21516A403; Tue, 14 Nov 2006 19:09:32 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 08EFB43D46; Tue, 14 Nov 2006 19:09:31 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 14 Nov 2006 19:09:30 +0000 (GMT) Date: Tue, 14 Nov 2006 19:09:30 +0000 From: David Malone To: Max Laier Message-ID: <20061114190930.GA23096@walton.maths.tcd.ie> References: <200611141709.26644.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200611141709.26644.max@love2party.net> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 19:09:33 -0000 On Tue, Nov 14, 2006 at 05:09:20PM +0100, Max Laier wrote: > Any ideas? Any papers that deal with this problem? Assuming you don't want to use one of the standard cryptographic ones (which I can imagine being a bit slow for something done per-packet), then one option might be to use a simpler hash that is keyed. Choose the key at boot/module load time and make it hard to produce collisions unless you know the key. David. From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 19:20:20 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BC7416A47B for ; Tue, 14 Nov 2006 19:20:20 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DAE943D8F for ; Tue, 14 Nov 2006 19:19:25 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout5.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kAEJJBMQ012103 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 14 Nov 2006 11:19:11 -0800 X-Auth-Received: from [128.208.5.99] (nilakantha.cs.washington.edu [128.208.5.99]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kAEJJBH2010547 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Tue, 14 Nov 2006 11:19:11 -0800 Message-ID: <455A16AF.5040200@u.washington.edu> Date: Tue, 14 Nov 2006 11:19:11 -0800 From: Garrett Cooper User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG References: <200611141435.kAEEZqFr036308@lurza.secnetix.de> In-Reply-To: <200611141435.kAEEZqFr036308@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.2.2.285561, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2006.11.14.110432 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __PHISH_PHRASE11 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: Subject: Re: bpf kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 19:20:20 -0000 Oliver Fromme wrote: > Vlad GURDIGA wrote: > > I'm trying to keep very close touch with 6.1_STABLE cvsupping sources > > once a week or even more often. > > You mean RELENG_6_1? I don't think that makes sense, > because not many changes happen to that branch. You > should only cvsup if necessary, i.e. when a security > fix (or otherwise critical fix) has been committed to > that branch. > > > I'm thinking of removing as much as > > possible devices from the kernel loading them from /boot/loader.conf > > instead, > > Personally I don't think it's worth the effort. I keep > most stuff static inside a big kernel. > > > so I could rebuild and install them without a whole > > kernel/world rebuild and reboot when sources change. I'm not sure this > > is a correct way, any piece of advice regarding this would be highly > > appreciated. :) > > When you update your sources, the recommended and official > way is to rebuild everything (kernel, modules, world) and > reboot. Omitting any of these steps _might_ work under > certain circumstances, but it can also break in various > ways (either horribly or subtly, whichever creates the > most damage, according to Murphy's law). > > > So, I've successfully done that with sound and network card drivers, > > but did not succeed with removing bpf from the kernel. Booting a > > kernel with no bpf support, and with > > ng_bpf_load="YES" in my loader.conf [which, I found on the questions > > list that is not what I need], the pflogd fails to start with this > > error: > > There's currently no kernel module for the bpf(4) device, > so you have to put it statically in your kernel if you need > it. ng_bpf is a netgraph node driver, it doesn't implement > /dev/bpf* devices, so it's not what you're looking for. > > Best regards > Oliver Something else I should have mentioned. Statically building components into the kernel makes operation faster overall, but increases the required memory for your machine, whereas using modules is more expensive time-wise, but you can load portions of the kernel piece by piece, instead of load the entire kernel into main memory. As Oliver stated, it's best that you don't update your machine all the time, but instead wait for updates that may be beneficial in terms of operating your computer, or are important security updates, as always updating your machine is probably just a waste of time and resources on your machine. Resources that could be better used by you, other users, or upgrading ports from time to time :). -Garrett From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 19:21:23 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A568516A55D; Tue, 14 Nov 2006 19:21:23 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 221EE43D72; Tue, 14 Nov 2006 19:21:02 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.66.1.82] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis), id 0MKwpI-1Gk3q21VMO-0000gD; Tue, 14 Nov 2006 20:20:54 +0100 From: Max Laier Organization: FreeBSD To: David Malone Date: Tue, 14 Nov 2006 20:20:47 +0100 User-Agent: KMail/1.9.4 References: <200611141709.26644.max@love2party.net> <20061114190930.GA23096@walton.maths.tcd.ie> In-Reply-To: <20061114190930.GA23096@walton.maths.tcd.ie> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1347703.ze6erUDHTS"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200611142020.53178.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 19:21:23 -0000 --nextPart1347703.ze6erUDHTS Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 14 November 2006 20:09, David Malone wrote: > On Tue, Nov 14, 2006 at 05:09:20PM +0100, Max Laier wrote: > > Any ideas? Any papers that deal with this problem? > > Assuming you don't want to use one of the standard cryptographic > ones (which I can imagine being a bit slow for something done > per-packet), then one option might be to use a simpler hash that > is keyed. Choose the key at boot/module load time and make it hard > to produce collisions unless you know the key. That's exactly what I am looking for ... now I need someone[tm] - with=20 better Math-Knowledge than mine - to write such a thing down in a simple=20 formula :-) i.e. take those bits from there and there and XOR them with=20 your canary yada-yada-yada ... =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1347703.ze6erUDHTS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFWhcVXyyEoT62BG0RAjiKAJ9dSHkBUj3/uxRoU6aoJ3ZTJ0oF9ACfQXpp 7h8OmbXL25j6zXx34OEJYhU= =apir -----END PGP SIGNATURE----- --nextPart1347703.ze6erUDHTS-- From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 19:46:11 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65CCE16A416 for ; Tue, 14 Nov 2006 19:46:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E839843D67 for ; Tue, 14 Nov 2006 19:46:00 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kAEJjqQM024703; Tue, 14 Nov 2006 14:45:53 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 14 Nov 2006 12:28:22 -0500 User-Agent: KMail/1.9.1 References: <20061109124119.GB16100@hoeg.nl> <20061109193342.GC16100@hoeg.nl> In-Reply-To: <20061109193342.GC16100@hoeg.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200611141228.23195.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 14 Nov 2006 14:45:54 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2194/Tue Nov 14 12:26:01 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Ed Schouten Subject: Re: [Patch] sys/kern/kern_descrip.c: remove double limit check in fcntl() X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 19:46:11 -0000 On Thursday 09 November 2006 14:33, Ed Schouten wrote: > * Ed Schouten wrote: > > The patch below prevents this by performing this check by do_dup(). It > > will prevent fcntl() from PROC_LOCK()'ing twice. It also fixes the > > return value of fcntl(). The manual page states that it should return > > EMFILE when it exceeds its limit, though the actual code sets EINVAL. > > Woops - It looks like I wasn't awake when I was reading the fcntl() > manual page. fcntl() should return EINVAL when the minimum value is > higher than the limit and EMFILE when it can't find a free descriptor in > the range from the minimum value to the maximum. dup() generalizes this > to EMFILE. It cannot return EINVAL. > > I decided to change the patch that do_dup() can return EINVAL for the > fcntl() scenario and that the dup()/dup2() system calls readjust the > errno right before returning. Please use the patch below. I actually the resulting changes obfuscate the code more than the current code, so I'd prefer to just leave it as it is. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 20:37:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5FB316A494 for ; Tue, 14 Nov 2006 20:37:42 +0000 (UTC) (envelope-from dm3lla@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CF3E43F37 for ; Tue, 14 Nov 2006 20:32:10 +0000 (GMT) (envelope-from dm3lla@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so1256412uge for ; Tue, 14 Nov 2006 12:32:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=S1jQSnT9UnhTeMaporKfJUBRauhboaTibcHLiGE4Ji0hpqvm3JQrjWJPPbdHTtx4lkS+Hw145x6Uvikwre48AKGMfn3/SRCnZQN5nxnHLXrdL8SBHtWPKcNL8PTZfNRkUdo8g9gm97nqPj5KmwHRguY4AL25Qgm1bQxynWfS5l4= Received: by 10.78.146.11 with SMTP id t11mr1437136hud.1163536329453; Tue, 14 Nov 2006 12:32:09 -0800 (PST) Received: by 10.78.180.14 with HTTP; Tue, 14 Nov 2006 12:32:09 -0800 (PST) Message-ID: <60acff080611141232r1a60556coe6a1c7d99e7357a9@mail.gmail.com> Date: Tue, 14 Nov 2006 16:32:09 -0400 From: D.Mella To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD on DVD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 20:37:43 -0000 Good Afternoon, I'm new to freebsd, and I'm really excited about this whole new world. I've been reading, and looking on the internet, and I'm wondering why there isn't a freebsd downloadable version in DVD. -- David Mella dm3lla@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 21:32:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E353916A403 for ; Tue, 14 Nov 2006 21:32:21 +0000 (UTC) (envelope-from grodzix@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF27843D67 for ; Tue, 14 Nov 2006 21:32:12 +0000 (GMT) (envelope-from grodzix@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so1031192pyb for ; Tue, 14 Nov 2006 13:31:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PFwmkWGV7BM0LItTqJFKtgL790usV1gY12p4Tr0L/67Uj/Ok780j1YshwUmLmm3y6YKmOhrQgvrp04OvwnLSEbaAqN7jag/o/LYL6Ol27alGmRdGUEr3kmI3Hf+RNJHOtf8M1bBg0Cqaifi31FM1cePZwc8leav6iAh2FqEAATI= Received: by 10.35.17.12 with SMTP id u12mr1889479pyi.1163539898283; Tue, 14 Nov 2006 13:31:38 -0800 (PST) Received: by 10.35.95.9 with HTTP; Tue, 14 Nov 2006 13:31:38 -0800 (PST) Message-ID: <6ecb59da0611141331l31365819o25397c0a64e25922@mail.gmail.com> Date: Tue, 14 Nov 2006 21:31:38 +0000 From: grodzix To: freebsd-hackers@freebsd.org In-Reply-To: <6ecb59da0611141329yc450cc1w419162d9bc49699c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <60acff080611141232r1a60556coe6a1c7d99e7357a9@mail.gmail.com> <6ecb59da0611141329yc450cc1w419162d9bc49699c@mail.gmail.com> Subject: Fwd: FreeBSD on DVD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 21:32:22 -0000 Hello, I thought first about the same but I came to conclusion that there is no really need for it. As far as I know the aim is to provide you basic framework which you can customize as you like. The first CD is more than you need to have fully runable FreeBSD system and second is basically only KDE. There is problem with Linux for which downloading and installin some programs that need lots of dependencies is horrible, so they simply put everything on huge DVD to make it possible to use for average user. On FreeBSD installing programs is much easier, automatic and done for you if you use ports or packages. It should also be also easier to mainstain and release new versions of FreeBSD in two CD containging just the neccesery tools than taking care of few gigs of apps with each release, and theese releases are much more often than those of Linux. It' just my personal opinion so the official intention may be quite different. Regards, Rafal Grodzinski On 14/11/06, D. Mella wrote: > Good Afternoon, > > I'm new to freebsd, and I'm really excited about this whole new world. I've > been reading, and looking on the internet, and I'm wondering why there isn't > a freebsd downloadable version in DVD. > > -- > David Mella > dm3lla@gmail.com > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 14 21:44:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4972E16A415 for ; Tue, 14 Nov 2006 21:44:47 +0000 (UTC) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84A7C43D49 for ; Tue, 14 Nov 2006 21:44:46 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A4C61.dip.t-dialin.net [84.154.76.97]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id kAELifok059536; Tue, 14 Nov 2006 22:44:42 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.13.6/8.13.6) with ESMTP id kAELicCi006467; Tue, 14 Nov 2006 22:44:38 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id kAELicjP029163; Tue, 14 Nov 2006 22:44:38 +0100 (CET) (envelope-from jhs@fire.jhs.private) Message-Id: <200611142144.kAELicjP029163@fire.jhs.private> To: "D.Mella" In-reply-to: <60acff080611141232r1a60556coe6a1c7d99e7357a9@mail.gmail.com> References: <60acff080611141232r1a60556coe6a1c7d99e7357a9@mail.gmail.com> Comments: In-reply-to "D.Mella" message dated "Tue, 14 Nov 2006 16:32:09 -0400." Date: Tue, 14 Nov 2006 22:44:38 +0100 From: "Julian H. Stacey" Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD on DVD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2006 21:44:47 -0000 "D.Mella" wrote: > Good Afternoon, > > I'm new to freebsd, and I'm really excited about this whole new world. I've > been reading, and looking on the internet, and I'm wondering why there isn't > a freebsd downloadable version in DVD. Bandwidth costs money to net providers. Lots of a DVD would not be needed. Sponsors of BSD still hope to make some money selling DVDs & donating from profits - we hope. There's various 600M cdrom images for various releases & CPU architectures on all the many mirrors of ftp://ftp.freebsd.org One or two CDs is all you need to do a basic install, after that many use the net. PS simple questions are best posted to questions@freebsd.org please. -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. http://berklix.org/free-software From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 01:07:30 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 640BD16A407 for ; Wed, 15 Nov 2006 01:07:30 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD2CF43D58 for ; Wed, 15 Nov 2006 01:07:29 +0000 (GMT) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id C1D86140EC03; Wed, 15 Nov 2006 01:08:48 +0000 (GMT) Date: Wed, 15 Nov 2006 01:08:48 +0000 From: John Birrell To: "D. Mella" Message-ID: <20061115010848.GA86171@what-creek.com> References: <60acff080611141232r1a60556coe6a1c7d99e7357a9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <60acff080611141232r1a60556coe6a1c7d99e7357a9@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: FreeBSD on DVD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 01:07:30 -0000 On Tue, Nov 14, 2006 at 04:32:09PM -0400, D. Mella wrote: > I'm new to freebsd, and I'm really excited about this whole new world. I've > been reading, and looking on the internet, and I'm wondering why there isn't > a freebsd downloadable version in DVD. The FreeBSD release process doesn't build an ISO larger than a CD. For FreeBSD/sun4v I'm working on adding a live DVD as an optional addition to the things that the release build currently does. Whether DVD images will ever be available for download will most likely depend on one or more companies providing extra bandwidth and server space. I can't imagine the current mirrors wanting to host a sun4v DVD of 4 GB for the limited number of users. i386 may be a different story. -- John Birrell From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 07:05:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1271A16A415 for ; Wed, 15 Nov 2006 07:05:08 +0000 (UTC) (envelope-from aag.lists@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AC1343D5C for ; Wed, 15 Nov 2006 07:05:07 +0000 (GMT) (envelope-from aag.lists@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so63592pyh for ; Tue, 14 Nov 2006 23:05:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=TqPxOmTU2z5cyss5ipVfFo0XjnzMI+BBxlBDaiIUg18CSSDwIMI+kRmlkwoz3qYNLVqEFqaWC9cTVfnWIWz/mxVjeA9PCy6Twjz+QL4VEN1quBcd8Q7dvlmI0f9sNcIDNBWuWUzIcbYbEwYTfVhCWAhwIJOwymnwIwFwe56+t7s= Received: by 10.35.18.4 with SMTP id v4mr2668504pyi.1163574306580; Tue, 14 Nov 2006 23:05:06 -0800 (PST) Received: by 10.35.59.14 with HTTP; Tue, 14 Nov 2006 23:05:06 -0800 (PST) Message-ID: <2f3a439f0611142305n441d3adwf7738ae40f9103e3@mail.gmail.com> Date: Wed, 15 Nov 2006 12:35:06 +0530 From: "Aditya Godbole" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 07:05:08 -0000 Hi, Is there any ramdisk support in freebsd, as there is in netbsd? If there is no such functionality right now, is anyone working on it? What are the alternatives if I want to mount a root filesytem from ram? Thanks. -- aditya From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 07:37:36 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBE6716A412 for ; Wed, 15 Nov 2006 07:37:36 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8173A43D5E for ; Wed, 15 Nov 2006 07:37:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6391B1A3C19; Tue, 14 Nov 2006 23:37:36 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0153851315; Wed, 15 Nov 2006 02:37:24 -0500 (EST) Date: Wed, 15 Nov 2006 02:37:24 -0500 From: Kris Kennaway To: Aditya Godbole Message-ID: <20061115073724.GA99861@xor.obsecurity.org> References: <2f3a439f0611142305n441d3adwf7738ae40f9103e3@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <2f3a439f0611142305n441d3adwf7738ae40f9103e3@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 07:37:36 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Nov 15, 2006 at 12:35:06PM +0530, Aditya Godbole wrote: > Hi, > Is there any ramdisk support in freebsd, as there is in netbsd? If > there is no such functionality right now, is anyone working on it? > What are the alternatives if I want to mount a root filesytem from ram? man mdconfig Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFWsO0Wry0BWjoQKURAlGUAKCccl2tAMCe5q5ZowKAW500PZcywACcDOHm c6jjFk23MuBln3Tj+MZSeFk= =oTvv -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 08:05:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37C7716A40F for ; Wed, 15 Nov 2006 08:05:17 +0000 (UTC) (envelope-from aag.lists@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D71D43D5D for ; Wed, 15 Nov 2006 08:05:16 +0000 (GMT) (envelope-from aag.lists@gmail.com) Received: by py-out-1112.google.com with SMTP id d32so74232pye for ; Wed, 15 Nov 2006 00:05:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=IpzeUx6xWIjo4Xt0Wok35a6E2iE+t2M9QSd8VwQXn1OydHt/2QLqa4wbav8LD5MVY7aRVMAuN1h2Et9eirsyx+8fsKMdVgyvs4D4wAHK+KaQ4qND1uU5eEbRA8OevevsRQ535Rhj7Z3Ve6N/Q2iM+GHR/E+IN1t2FezxjBcdxy8= Received: by 10.35.103.1 with SMTP id f1mr2692881pym.1163577914127; Wed, 15 Nov 2006 00:05:14 -0800 (PST) Received: by 10.35.59.14 with HTTP; Wed, 15 Nov 2006 00:05:13 -0800 (PST) Message-ID: <2f3a439f0611150005k4561a5b6i4aa27d235c1b29ab@mail.gmail.com> Date: Wed, 15 Nov 2006 13:35:14 +0530 From: "Aditya Godbole" To: "Kris Kennaway" In-Reply-To: <20061115073724.GA99861@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2f3a439f0611142305n441d3adwf7738ae40f9103e3@mail.gmail.com> <20061115073724.GA99861@xor.obsecurity.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 08:05:17 -0000 On 11/15/06, Kris Kennaway wrote: > > What are the alternatives if I want to mount a root filesytem from ram? > > man mdconfig > I'm sorry, I couldn't quite get what I was looking for from the manpage. How do I use mdconfig to mount the root filesystem? -- aditya From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 08:13:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9234D16A417 for ; Wed, 15 Nov 2006 08:13:58 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E23EE43D5C for ; Wed, 15 Nov 2006 08:13:57 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C70F81A4D89; Wed, 15 Nov 2006 00:13:57 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 330B051341; Wed, 15 Nov 2006 03:13:46 -0500 (EST) Date: Wed, 15 Nov 2006 03:13:46 -0500 From: Kris Kennaway To: Aditya Godbole Message-ID: <20061115081345.GA541@xor.obsecurity.org> References: <2f3a439f0611142305n441d3adwf7738ae40f9103e3@mail.gmail.com> <20061115073724.GA99861@xor.obsecurity.org> <2f3a439f0611150005k4561a5b6i4aa27d235c1b29ab@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y0ulUmNC+osPPQO6" Content-Disposition: inline In-Reply-To: <2f3a439f0611150005k4561a5b6i4aa27d235c1b29ab@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org, Kris Kennaway Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 08:13:58 -0000 --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 15, 2006 at 01:35:14PM +0530, Aditya Godbole wrote: > On 11/15/06, Kris Kennaway wrote: >=20 > >> What are the alternatives if I want to mount a root filesytem from ram? > > > >man mdconfig > > >=20 > I'm sorry, I couldn't quite get what I was looking for from the > manpage. How do I use mdconfig to mount the root filesystem? See related documentation, e.g. md(4). Kris --y0ulUmNC+osPPQO6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFWsw5Wry0BWjoQKURAn5RAJ9Ld/qjskCYZ521uD9i47OqZvWTSACgtpgm re+oJBKapsVvF8I71CV5BsM= =azpy -----END PGP SIGNATURE----- --y0ulUmNC+osPPQO6-- From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 10:06:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13BC516A407 for ; Wed, 15 Nov 2006 10:06:06 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from s200aog11.obsmtp.com (s200aog11.obsmtp.com [207.126.144.125]) by mx1.FreeBSD.org (Postfix) with SMTP id 1854743D60 for ; Wed, 15 Nov 2006 10:06:00 +0000 (GMT) (envelope-from tom@tomjudge.com) Received: from source ([63.174.175.251]) by eu1sys200aob011.postini.com ([207.126.147.11]) with SMTP; Wed, 15 Nov 2006 10:05:55 UTC Received: from [0.0.0.0] (unknown [10.0.0.37]) by bbbx3.usdmm.com (Postfix) with ESMTP id 465335C71; Wed, 15 Nov 2006 04:05:53 -0600 (CST) Message-ID: <455AE63D.3080501@tomjudge.com> Date: Wed, 15 Nov 2006 10:04:45 +0000 From: Tom Judge User-Agent: Thunderbird 1.5.0.7 (X11/20060922) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: jthomson@mintel.com Subject: [patch] Path MTU Discovery when routing over IPSec connections X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 10:06:06 -0000 I have been looking into some problems with PMTU Discovery when routing packets over IPSec (gif) tunnels, I have submitted the details to the open PR kern/91412 but have had no response as to whether my patch is the correct solution to the problem. The problem occurs when sys/netinet/ip_input.c constructs the ICMP Host Unreachable message with an MTU hint. Triggered when a packet that is to be routed over the IPSec link is larger than the MTU on the link and has the Don't Fragment bit set. There is a block of code that is specific to IPSec (gif) MTU discovery which attempts to calculate the MTU size of the link by working out the size of the IPSec header and subtracting this from the MTU of the transmission interface and the gif IP header. However the code fails to retrieve a fully populated security policy which means that the code block designed to calculate the MTU never gets run. The code then breaks out of the case statement and transmits the ICMP packet with the MTU hint set to 0. If the break is removed from IPSec code the MTU calculation is carried out by the non IPSec code successfully. This begs the question whether the IPSec code is even needed as the normal code works fine? Network Layout: Box 1 --------- Router 2 --(Ipsec tunnel)-- Router 3 --(lan) --- Box 2 |(lan) |------ Router 1 Box 1: FreeBSD 5.4 Router [123]: FreeBSD 6.1 Box 2: Linux 2.6 Tests to reproduce the error: PING Test from box 1 to box 2 with do not fragment set and a packet larger than the path MTU: box1# ping -s 1280 -D box2 PING box2 (10.0.0.79): 1280 data bytes 36 bytes from router1 (172.17.3.5): Redirect Host(New addr: 172.17.3.6) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 051c b454 0 0000 40 01 c9fc 172.17.1.48 10.0.0.79 36 bytes from router2 (172.17.3.6): frag needed and DF set (MTU 0) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 1c05 b454 0 0000 3f 01 cafc 172.17.1.48 10.0.0.79 36 bytes from router1 (172.17.3.5): Redirect Host(New addr: 172.17.3.6) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 051c b45f 0 0000 40 01 c9f1 172.17.1.48 10.0.0.79 36 bytes from router2 (172.17.3.6): frag needed and DF set (MTU 0) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 1c05 b45f 0 0000 3f 01 caf1 172.17.1.48 10.0.0.79 ^C --- box2 ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss PING Test from box 1 to box 2 with do not fragment set and a packet smaller than the path MTU: box1# ping -s 1200 -D box2 PING box2 (10.0.0.79): 1200 data bytes 36 bytes from router1 (172.17.3.5): Redirect Host(New addr: 172.17.3.6) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 04cc b472 0 0000 40 01 ca2e 172.17.1.48 10.0.0.79 1208 bytes from 10.0.0.79: icmp_seq=0 ttl=61 time=111.017 ms 36 bytes from router1 (172.17.3.5): Redirect Host(New addr: 172.17.3.6) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 04cc b479 0 0000 40 01 ca27 172.17.1.48 10.0.0.79 1208 bytes from 10.0.0.79: icmp_seq=1 ttl=61 time=110.419 ms ^C --- box2 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 110.419/110.718/111.017/0.299 ms box1# Relevent interface configuration on box1 (from ifconfig): em0: flags=8843 mtu 1500 options=b inet 172.17.1.48 netmask 0xffff0000 broadcast 172.17.255.255 ether 00:0f:1f:fa:d1:b5 media: Ethernet autoselect (1000baseTX ) status: active Relevent interface configuration on router2 (from ifconfig): em0: flags=8943 mtu 1500 options=b inet 172.17.3.6 netmask 0xffff0000 broadcast 172.17.255.255 ether 00:c0:9f:12:13:1b media: Ethernet autoselect (1000baseTX ) status: active gif0: flags=8051 mtu 1280 tunnel inet 63.174.xxx.xxx --> 82.195.xxx.xxx inet 192.168.174.10 --> 192.168.174.9 netmask 0xfffffffc Patch: Index: sys/netinet/ip_input.c =================================================================== --- sys/netinet/ip_input.c (revision 24) +++ sys/netinet/ip_input.c (working copy) @@ -1990,8 +1990,8 @@ #else /* FAST_IPSEC */ KEY_FREESP(&sp); #endif - ipstat.ips_cantfrag++; - break; +// ipstat.ips_cantfrag++; +// break; } } #endif /*IPSEC || FAST_IPSEC*/ Tests after the patch has been applied: PING Test from box 1 to box 2 with do not fragment set and a packet larger than the path MTU: box1# ping -s 1280 -D box2 PING box2 (10.0.0.79): 1280 data bytes 36 bytes from router1 (172.17.3.5): Redirect Host(New addr: 172.17.3.6) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 051c b454 0 0000 40 01 c9fc 172.17.1.48 10.0.0.79 36 bytes from router2 (172.17.3.6): frag needed and DF set (MTU 1280) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 1c05 b454 0 0000 3f 01 cafc 172.17.1.48 10.0.0.79 36 bytes from router1 (172.17.3.5): Redirect Host(New addr: 172.17.3.6) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 051c b45f 0 0000 40 01 c9f1 172.17.1.48 10.0.0.79 36 bytes from router2 (172.17.3.6): frag needed and DF set (MTU 1280) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 1c05 b45f 0 0000 3f 01 caf1 172.17.1.48 10.0.0.79 Any comments suggestions on this would be greatly appreciated. Tom J From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 11:01:45 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8FC116A417 for ; Wed, 15 Nov 2006 11:01:45 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2AAF43D55 for ; Wed, 15 Nov 2006 11:01:44 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (czgzuv@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAFB1cZS089423; Wed, 15 Nov 2006 12:01:43 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAFB1c8a089422; Wed, 15 Nov 2006 12:01:38 +0100 (CET) (envelope-from olli) Date: Wed, 15 Nov 2006 12:01:38 +0100 (CET) Message-Id: <200611151101.kAFB1c8a089422@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, aag.lists@gmail.com In-Reply-To: <2f3a439f0611142305n441d3adwf7738ae40f9103e3@mail.gmail.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 15 Nov 2006 12:01:43 +0100 (CET) Cc: Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, aag.lists@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 11:01:45 -0000 Aditya Godbole wrote: > Is there any ramdisk support in freebsd, as there is in netbsd? Sure. To mount a 200 MB swap-backed memory filesystem on /tmp, add this lie to /etc/fstab: md /tmp mfs rw,async,nosuid,-s200m,-m0 0 0 > What are the alternatives if I want to mount a root filesytem from ram? You mean a diskless setup? I think there's a detailed description of diskless setups in the FreeBSD Handbook. You might also want to look at the diskless(8) manpage. Best regards Oliver PS: Such questions are more appropriate for the freebsd- questions list. They're not really "hacker" questions. -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "The scanf() function is a large and complex beast that often does something almost but not quite entirely unlike what you desired." -- Chris Torek From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 11:26:36 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E024116A40F for ; Wed, 15 Nov 2006 11:26:36 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6ABB043D69 for ; Wed, 15 Nov 2006 11:26:35 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ilclej@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAFBQSKP090633; Wed, 15 Nov 2006 12:26:34 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAFBQSQr090632; Wed, 15 Nov 2006 12:26:28 +0100 (CET) (envelope-from olli) Date: Wed, 15 Nov 2006 12:26:28 +0100 (CET) Message-Id: <200611151126.kAFBQSQr090632@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, max@love2party.net In-Reply-To: X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 15 Nov 2006 12:26:34 +0100 (CET) Cc: Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, max@love2party.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 11:26:37 -0000 Max Laier wrote: > David Malone wrote: > > Assuming you don't want to use one of the standard cryptographic > > ones (which I can imagine being a bit slow for something done > > per-packet), then one option might be to use a simpler hash that > > is keyed. Choose the key at boot/module load time and make it hard > > to produce collisions unless you know the key. > > That's exactly what I am looking for ... now I need someone[tm] - with > better Math-Knowledge than mine - to write such a thing down in a simple > formula :-) i.e. take those bits from there and there and XOR them with > your canary yada-yada-yada ... In that case, simply use crc32 (available from libkern.h) and xor with a random key generated at boot time. crc32 is fast to calculate and has the properties that you need. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Perl will consistently give you what you want, unless what you want is consistency." -- Larry Wall From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 11:55:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A027C16A407 for ; Wed, 15 Nov 2006 11:55:37 +0000 (UTC) (envelope-from aag.lists@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0542D43D45 for ; Wed, 15 Nov 2006 11:55:36 +0000 (GMT) (envelope-from aag.lists@gmail.com) Received: by py-out-1112.google.com with SMTP id f31so105416pyh for ; Wed, 15 Nov 2006 03:55:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Vjte+G1K60HA6hoidJ9qpOGIcahCDrNpSLt9ut7NoMSxZBgrjCW12e7eUo6IOBrGKL/aBG/7fPKfhuqfeU576zRET34oCcfHU+/Sex6CrrJMR/L+YU0zNgvxVytIGpYG36SX2eg6AWh5dRLycvTxgE+zvY1JeWiEGnpsJIk3Nqw= Received: by 10.35.21.9 with SMTP id y9mr2828271pyi.1163591736163; Wed, 15 Nov 2006 03:55:36 -0800 (PST) Received: by 10.35.59.14 with HTTP; Wed, 15 Nov 2006 03:55:36 -0800 (PST) Message-ID: <2f3a439f0611150355n3dd81845ydbeb0a7b597fb087@mail.gmail.com> Date: Wed, 15 Nov 2006 17:25:36 +0530 From: "Aditya Godbole" To: freebsd-hackers@freebsd.org In-Reply-To: <200611151101.kAFB1c8a089422@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2f3a439f0611142305n441d3adwf7738ae40f9103e3@mail.gmail.com> <200611151101.kAFB1c8a089422@lurza.secnetix.de> Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 11:55:37 -0000 On 11/15/06, Oliver Fromme wrote: > Aditya Godbole wrote: > > Is there any ramdisk support in freebsd, as there is in netbsd? > > What are the alternatives if I want to mount a root filesytem from ram? > > You mean a diskless setup? I think there's a detailed > description of diskless setups in the FreeBSD Handbook. > You might also want to look at the diskless(8) manpage. > Hi, I was looking for something like initrd support of Linux or the mdsetimage of NetBSD. I have no disc or network card support for my hardware at the moment. -- aditya From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 06:33:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 692BF16A40F for ; Wed, 15 Nov 2006 06:33:25 +0000 (UTC) (envelope-from ralph@zitz.dk) Received: from camilla.zitz.dk (ip30.ds1-od.adsl.cybercity.dk [217.157.208.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B90343D49 for ; Wed, 15 Nov 2006 06:33:21 +0000 (GMT) (envelope-from ralph@zitz.dk) Received: from localhost (localhost.zitz.dk [127.0.0.1]) by camilla.zitz.dk (8.13.8/8.13.6) with ESMTP id kAF6XJYL092272 for ; Wed, 15 Nov 2006 07:33:19 +0100 (CET) (envelope-from ralph@zitz.dk) X-Virus-Scanned: amavisd-new at zitz.dk Received: from camilla.zitz.dk ([127.0.0.1]) by localhost (camilla.zitz.dk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HQ2yjfDGdODM for ; Wed, 15 Nov 2006 07:33:12 +0100 (CET) Received: from [10.0.0.3] (mobile.zitz.dk [10.0.0.3]) (authenticated bits=0) by camilla.zitz.dk (8.13.8/8.13.6) with ESMTP id kAF6X7uf092268 for ; Wed, 15 Nov 2006 07:33:08 +0100 (CET) (envelope-from ralph@zitz.dk) Message-ID: <455AB4A2.6050809@zitz.dk> Date: Wed, 15 Nov 2006 07:33:06 +0100 From: Ralph Zitz User-Agent: Thunderbird 1.5.0.8 (X11/20061110) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 15 Nov 2006 12:38:12 +0000 Subject: FreeBSD on DVD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 06:33:25 -0000 Hello, In case you really want a DVD with FreeBSD you can make one yourself using this guide: http://www.pa.msu.edu/~tigner/bsddvd.html Which worked fine when I tried it a while back. Cheers, Ralph. From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 11:47:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2EE216A412 for ; Wed, 15 Nov 2006 11:47:38 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 684E443D6A for ; Wed, 15 Nov 2006 11:47:37 +0000 (GMT) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A5F174.dip.t-dialin.net [84.165.241.116]) by redbull.bpaserver.net (Postfix) with ESMTP id A90632E14F; Wed, 15 Nov 2006 12:47:31 +0100 (CET) Received: from webmail.leidinger.net (webmail.Leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 59D645B4C35; Wed, 15 Nov 2006 12:47:30 +0100 (CET) Received: (from www@localhost) by webmail.leidinger.net (8.13.8/8.13.8/Submit) id kAFBlUP6034724; Wed, 15 Nov 2006 12:47:30 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Wed, 15 Nov 2006 12:47:29 +0100 Message-ID: <20061115124729.e4alqrgs0o8kow8w@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Wed, 15 Nov 2006 12:47:29 +0100 From: Alexander Leidinger To: Garrett Cooper References: <200611141435.kAEEZqFr036308@lurza.secnetix.de> <455A16AF.5040200@u.washington.edu> In-Reply-To: <455A16AF.5040200@u.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.1.3) / FreeBSD-7.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.787, required 6, autolearn=not spam, BAYES_00 -15.00, DK_POLICY_SIGNSOME 0.00, FORGED_RCVD_HELO 0.14, TW_BP 0.08) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Wed, 15 Nov 2006 12:38:22 +0000 Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: bpf kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 11:47:38 -0000 Quoting Garrett Cooper (from Tue, 14 Nov 2006 11:19:11 -0800): > Something else I should have mentioned. Statically building components > into the kernel makes operation faster overall, but increases the > required memory for your machine, whereas using modules is more > expensive time-wise, but you can load portions of the kernel piece by > piece, instead of load the entire kernel into main memory. As Oliver How did you measure/tested this and what are the numbers? Bye, Alexander. -- Each of us bears his own Hell. -- Publius Vergilius Maro (Virgil) http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 12:53:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5739916A403 for ; Wed, 15 Nov 2006 12:53:21 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B8FB43D55 for ; Wed, 15 Nov 2006 12:53:19 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.187.200] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis), id 0MKxQS-1GkKGU0RZA-0004Zb; Wed, 15 Nov 2006 13:53:18 +0100 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Wed, 15 Nov 2006 13:53:12 +0100 User-Agent: KMail/1.9.4 References: <200611151126.kAFBQSQr090632@lurza.secnetix.de> In-Reply-To: <200611151126.kAFBQSQr090632@lurza.secnetix.de> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2097590.e4QkgR1fiN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200611151353.17417.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 12:53:21 -0000 --nextPart2097590.e4QkgR1fiN Content-Type: multipart/mixed; boundary="Boundary-01=_52wWFS911yltzsZ" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_52wWFS911yltzsZ Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 15 November 2006 12:26, Oliver Fromme wrote: > Max Laier wrote: > > David Malone wrote: > > > Assuming you don't want to use one of the standard cryptographic > > > ones (which I can imagine being a bit slow for something done > > > per-packet), then one option might be to use a simpler hash that > > > is keyed. Choose the key at boot/module load time and make it hard > > > to produce collisions unless you know the key. > > > > That's exactly what I am looking for ... now I need someone[tm] - > > with better Math-Knowledge than mine - to write such a thing down in > > a simple formula :-) i.e. take those bits from there and there and > > XOR them with your canary yada-yada-yada ... > > In that case, simply use crc32 (available from libkern.h) > and xor with a random key generated at boot time. crc32 > is fast to calculate and has the properties that you need. Oops, I missed one requirement: /* * IMPORTANT: the hash function for dynamic rules must be commutative * in source and destination (ip,port), because rules are bidirectional * and we want to find both in the same bucket. */ AFAICT, the attached has this property, but I have no idea if it adds=20 sufficient entropy to the result - it looks like it, though. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-01=_52wWFS911yltzsZ Content-Type: text/x-diff; charset="iso-8859-6"; name="ipfw.crchash.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="ipfw.crchash.diff" Index: ip_fw2.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/store/mlaier/fcvs/src/sys/netinet/ip_fw2.c,v retrieving revision 1.153 diff -u -r1.153 ip_fw2.c =2D-- ip_fw2.c 6 Nov 2006 13:42:04 -0000 1.153 +++ ip_fw2.c 15 Nov 2006 12:36:34 -0000 @@ -230,6 +230,7 @@ static ipfw_dyn_rule **ipfw_dyn_v =3D NULL; static u_int32_t dyn_buckets =3D 256; /* must be power of 2 */ static u_int32_t curr_dyn_buckets =3D 256; /* must be power of 2 */ +static u_int32_t hash_nonce =3D 0; =20 static struct mtx ipfw_dyn_mtx; /* mutex guarding dynamic rules */ #define IPFW_DYN_LOCK_INIT() \ @@ -642,12 +643,19 @@ hash_packet6(struct ipfw_flow_id *id) { u_int32_t i; =2D i =3D (id->dst_ip6.__u6_addr.__u6_addr32[2]) ^ + + i =3D (id->dst_ip6.__u6_addr.__u6_addr32[0]) ^ + (id->dst_ip6.__u6_addr.__u6_addr32[1]) ^ + (id->dst_ip6.__u6_addr.__u6_addr32[2]) ^ (id->dst_ip6.__u6_addr.__u6_addr32[3]) ^ + (id->src_ip6.__u6_addr.__u6_addr32[0]) ^ + (id->src_ip6.__u6_addr.__u6_addr32[1]) ^ (id->src_ip6.__u6_addr.__u6_addr32[2]) ^ (id->src_ip6.__u6_addr.__u6_addr32[3]) ^ (id->dst_port) ^ (id->src_port); =2D return i; + i =3D crc32_raw(&i, sizeof(i), hash_nonce); + + return (i); } =20 static int @@ -4360,6 +4368,7 @@ uma_zdestroy(ipfw_dyn_rule_zone); return (error); } + hash_nonce =3D arc4random(); ip_fw_ctl_ptr =3D ipfw_ctl; ip_fw_chk_ptr =3D ipfw_chk; callout_reset(&ipfw_timeout, hz, ipfw_tick, NULL); --Boundary-01=_52wWFS911yltzsZ-- --nextPart2097590.e4QkgR1fiN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFWw29XyyEoT62BG0RAgw7AJ9Qpvif6ztViclOL197hWYCF4GTowCcDQdN zemXAd+9ypxtz04+UUFXKtY= =3+wU -----END PGP SIGNATURE----- --nextPart2097590.e4QkgR1fiN-- From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 13:01:36 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A28E516A47B; Wed, 15 Nov 2006 13:01:36 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE0EF43D6E; Wed, 15 Nov 2006 13:01:22 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (uzyroz@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAFD1GmS095075; Wed, 15 Nov 2006 14:01:21 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAFD1G9d095074; Wed, 15 Nov 2006 14:01:16 +0100 (CET) (envelope-from olli) Date: Wed, 15 Nov 2006 14:01:16 +0100 (CET) Message-Id: <200611151301.kAFD1G9d095074@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, max@love2party.net In-Reply-To: <200611151126.kAFBQSQr090632@lurza.secnetix.de> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 15 Nov 2006 14:01:21 +0100 (CET) Cc: Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG, max@love2party.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 13:01:36 -0000 Oliver Fromme wrote: > Max Laier wrote: > > David Malone wrote: > > > Assuming you don't want to use one of the standard cryptographic > > > ones (which I can imagine being a bit slow for something done > > > per-packet), then one option might be to use a simpler hash that > > > is keyed. Choose the key at boot/module load time and make it hard > > > to produce collisions unless you know the key. > > > > That's exactly what I am looking for ... now I need someone[tm] - with > > better Math-Knowledge than mine - to write such a thing down in a simple > > formula :-) i.e. take those bits from there and there and XOR them with > > your canary yada-yada-yada ... > > In that case, simply use crc32 (available from libkern.h) > and xor with a random key generated at boot time. crc32 > is fast to calculate and has the properties that you need. Uhm, sorry, after reading that sentence again and thinking about it, it seems to be misleading. You have to xor with a random key _first_, and _then_ calculate the crc32 value. If you did it the other way, the random key would not prevent from collisions at all, because: same_crc ^ same_key == same_hash. ;-) Suppose a malicious user is able to create two different sets of connections parameters (P1 and P2) which have the same CRC32 value (without using a key): P1 != P2 crc32(P1) == crc32(P2) If you xor (or add) the random key K to the parameters, it will change the outcome of the crc32 calculation in different ways: crc32(P1 ^ K) != crc32(P2 ^ K) Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I made up the term 'object-oriented', and I can tell you I didn't have C++ in mind." -- Alan Kay, OOPSLA '97 From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 13:35:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C17116A412 for ; Wed, 15 Nov 2006 13:35:17 +0000 (UTC) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (relay0.rambler.ru [81.19.66.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1EAA43D7B for ; Wed, 15 Nov 2006 13:35:08 +0000 (GMT) (envelope-from ru@rambler-co.ru) Received: from relay0.rambler.ru (localhost [127.0.0.1]) by relay0.rambler.ru (Postfix) with ESMTP id 1D2805F61; Wed, 15 Nov 2006 16:35:07 +0300 (MSK) Received: from edoofus.park.rambler.ru (unknown [81.19.65.108]) by relay0.rambler.ru (Postfix) with ESMTP id EF1BD5F54; Wed, 15 Nov 2006 16:35:06 +0300 (MSK) Received: (from ru@localhost) by edoofus.park.rambler.ru (8.13.8/8.13.8) id kAFDZ7am037795; Wed, 15 Nov 2006 16:35:07 +0300 (MSK) (envelope-from ru) Date: Wed, 15 Nov 2006 16:35:07 +0300 From: Ruslan Ermilov To: Aditya Godbole Message-ID: <20061115133507.GE19881@rambler-co.ru> References: <2f3a439f0611142305n441d3adwf7738ae40f9103e3@mail.gmail.com> <200611151101.kAFB1c8a089422@lurza.secnetix.de> <2f3a439f0611150355n3dd81845ydbeb0a7b597fb087@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TeJTyD9hb8KJN2Jy" Content-Disposition: inline In-Reply-To: <2f3a439f0611150355n3dd81845ydbeb0a7b597fb087@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: No virus found Cc: freebsd-hackers@freebsd.org Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 13:35:17 -0000 --TeJTyD9hb8KJN2Jy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 15, 2006 at 05:25:36PM +0530, Aditya Godbole wrote: > On 11/15/06, Oliver Fromme wrote: > >Aditya Godbole wrote: > > > Is there any ramdisk support in freebsd, as there is in netbsd? > > > What are the alternatives if I want to mount a root filesytem from ra= m? > > > >You mean a diskless setup? I think there's a detailed > >description of diskless setups in the FreeBSD Handbook. > >You might also want to look at the diskless(8) manpage. > > >=20 > Hi, >=20 > I was looking for something like initrd support of Linux or the > mdsetimage of NetBSD. > I have no disc or network card support for my hardware at the moment. >=20 Well, how are you going to boot your system without a disk and network then? We support disk booting, and diskless (network) booting, also support CD-ROM and floppy booting. What of these do you need? Like others have said, we can load kernels with an embedded root filesystem image; the image can either be read-write or read-only; in the latter case, it can also be compressed with geom_uzip(4). Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --TeJTyD9hb8KJN2Jy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFWxeKqRfpzJluFF4RAnFVAJ9QnSiGxAf6QwmKc83PeIMWsCxzOQCeOoqN uCXs+DwZltNmNyc/0R4zaAw= =GVOX -----END PGP SIGNATURE----- --TeJTyD9hb8KJN2Jy-- From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 13:44:42 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E72AE16A412 for ; Wed, 15 Nov 2006 13:44:42 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 461FB43D46 for ; Wed, 15 Nov 2006 13:44:42 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (tytmli@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAFDiZpq097518; Wed, 15 Nov 2006 14:44:40 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAFDiZmh097517; Wed, 15 Nov 2006 14:44:35 +0100 (CET) (envelope-from olli) Date: Wed, 15 Nov 2006 14:44:35 +0100 (CET) Message-Id: <200611151344.kAFDiZmh097517@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, aag.lists@gmail.com In-Reply-To: <2f3a439f0611150355n3dd81845ydbeb0a7b597fb087@mail.gmail.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 15 Nov 2006 14:44:41 +0100 (CET) Cc: Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, aag.lists@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 13:44:43 -0000 Aditya Godbole wrote: > Oliver Fromme wrote: > > Aditya Godbole wrote: > > > Is there any ramdisk support in freebsd, as there is in netbsd? > > > What are the alternatives if I want to mount a root filesytem from ram? > > > > You mean a diskless setup? I think there's a detailed > > description of diskless setups in the FreeBSD Handbook. > > You might also want to look at the diskless(8) manpage. > > I was looking for something like initrd support of Linux or the > mdsetimage of NetBSD. The boot loader can pre-load the root filesystem image as an md(4) device, similar to loading a splash screen. The kernel option to enable that feature is called MD_ROOT, and I think it's even enabled by default in the GENERIC kernel. You can also put the image of the root file system into the kernel itself, so it doesn't have to be loaded separately. The kernel option to allocate appropriate space is called MD_ROOT_SIZE. > I have no disc or network card support for my hardware at the moment. Then where are you booting from? At least your kernel has to come from somewhere, i.e. you need either networking or some kind of media (disk, USB stick or similar). Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "I have stopped reading Stephen King novels. Now I just read C code instead." -- Richard A. O'Keefe From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 13:56:54 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B889316A417 for ; Wed, 15 Nov 2006 13:56:54 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1864243D62 for ; Wed, 15 Nov 2006 13:56:39 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (xeryjg@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAFDuPNf098267; Wed, 15 Nov 2006 14:56:31 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAFDuOXE098265; Wed, 15 Nov 2006 14:56:24 +0100 (CET) (envelope-from olli) Date: Wed, 15 Nov 2006 14:56:24 +0100 (CET) Message-Id: <200611151356.kAFDuOXE098265@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, youshi10@u.washington.edu In-Reply-To: <455A16AF.5040200@u.washington.edu> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 15 Nov 2006 14:56:31 +0100 (CET) Cc: Subject: Re: bpf kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, youshi10@u.washington.edu List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 13:56:54 -0000 Garrett Cooper wrote: > Something else I should have mentioned. Statically building components > into the kernel makes operation faster overall, I don't think there's a measurable difference in speed. > but increases the > required memory for your machine, whereas using modules is more > expensive time-wise, but you can load portions of the kernel piece by > piece, instead of load the entire kernel into main memory. In the case discussed here (bpf), memory is not an issue, because the bpf module -- if it existed -- would have to be loaded permanently anyway, or otherwise pflogd wouldn't work. In fact, a kernel module requires a small amount of additional memory, compared to the same code compiled statically into the kernel. It's not a big deal, though. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Being really good at C++ is like being really good at using rocks to sharpen sticks." -- Thant Tessman From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 14:35:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C75B416A416 for ; Wed, 15 Nov 2006 14:35:38 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from antivirus.uni-rostock.de (mailrelay1.uni-rostock.de [139.30.8.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65EC743D76 for ; Wed, 15 Nov 2006 14:27:59 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from antivirus.exch.rz.uni-rostock.de ([127.0.0.1]) by antivirus.uni-rostock.de with Microsoft SMTPSVC(6.0.3790.1830); Wed, 15 Nov 2006 15:27:44 +0100 Received: from antivirus.uni-rostock.de (unverified) by antivirus.exch.rz.uni-rostock.de (Clearswift SMTPRS 5.2.5) with ESMTP id for ; Wed, 15 Nov 2006 15:22:03 +0100 Received: from mail pickup service by antivirus.uni-rostock.de with Microsoft SMTPSVC; Wed, 15 Nov 2006 15:22:03 +0100 X-SCL: 4 62.43% Received: from mail.uni-rostock.de ([139.30.8.11]) by antivirus.uni-rostock.de with Microsoft SMTPSVC(6.0.3790.1830); Wed, 15 Nov 2006 15:21:59 +0100 Received: from britannica.bec.de (storm.stura.uni-rostock.de [139.30.252.72]) by mail2.uni-rostock.de (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0J8R00BBOZWMDX@mail.uni-rostock.de> for freebsd-hackers@freebsd.org; Wed, 15 Nov 2006 15:21:58 +0100 (MET) Received: by britannica.bec.de (Postfix, from userid 1000) id BAFAC41D1; Wed, 15 Nov 2006 15:21:54 +0100 (CET) Date: Wed, 15 Nov 2006 15:21:53 +0100 From: Joerg Sonnenberger In-reply-to: <200611151353.17417.max@love2party.net> To: freebsd-hackers@freebsd.org Mail-followup-to: freebsd-hackers@freebsd.org Message-id: <20061115142153.GB7039@britannica.bec.de> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) References: <200611151126.kAFBQSQr090632@lurza.secnetix.de> <200611151353.17417.max@love2party.net> X-OriginalArrivalTime: 15 Nov 2006 14:21:59.0450 (UTC) FILETIME=[697787A0:01C708C1] Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 14:35:38 -0000 On Wed, Nov 15, 2006 at 01:53:12PM +0100, Max Laier wrote: > AFAICT, the attached has this property, but I have no idea if it adds > sufficient entropy to the result - it looks like it, though. You should do at least some bit shifting on the arguments as typical ipv6 addresses are by default MAC based and larger shipments of the same hardware often have similiar enough MACs to create collisions. I think what Olliver meant was more to use an input of 128bit for crc32, after xoring src, dst and secret. Joerg From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 15:21:37 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D18B16A40F for ; Wed, 15 Nov 2006 15:21:37 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41C8843D5E for ; Wed, 15 Nov 2006 15:21:35 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (tmlifo@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAFFLT7r003406; Wed, 15 Nov 2006 16:21:34 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAFFLT6V003405; Wed, 15 Nov 2006 16:21:29 +0100 (CET) (envelope-from olli) Date: Wed, 15 Nov 2006 16:21:29 +0100 (CET) Message-Id: <200611151521.kAFFLT6V003405@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, max@love2party.net In-Reply-To: <200611151353.17417.max@love2party.net> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 15 Nov 2006 16:21:34 +0100 (CET) Cc: Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, max@love2party.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 15:21:37 -0000 Max Laier wrote: > Oops, I missed one requirement: > /* > * IMPORTANT: the hash function for dynamic rules must be commutative > * in source and destination (ip,port), because rules are bidirectional > * and we want to find both in the same bucket. > */ OK, then you have to perform a commutative operation on source and destination ("xor" or "add"), then run crc32 on the result. > AFAICT, the attached has this property, but I have no idea if it adds > sufficient entropy to the result - it looks like it, though. It's not exactly what I had in mind. You are xor'ing all components with each other first, which makes it easier for an attacker to construct a collision: He just has to generate one 32bit part (e.g. the lower 32 bits of his address) so that the result of the xor stays the same. It's trivial to do that. Then the result of the crc32 will also be the same, of course. You should xor source and destination as a whole, i.e. create an artifical (ip,port) struct that contains the xor'ed source and destination, then call crc32 on the 20 bytes of that struct. The random key can be used as initialization vector for crc32_raw(), like you did in your patch. However, there's still a problem: If the attacker can guess our port number, he can set his port number in a way that it will result in the same xor value. If his and our IP address are also the same, the total result will be the same again. A simple solution is to multiply the port numbers (with a 32bit result) instead of xor'ing them. Multiplication is commutative, but in most cases the attacker won't be able to generate an integer port number P2 in a way that P2 * P1 will equal a certain number, because in most cases that number won't be evenly divisible by P1. Of course there are a few cases left where it is possible to generate such an integer number P2. To defeat the attackers for those few cases, too, you should add another random key to both port numbers before multiplication. OK, to summarize: 1. Calculate src_ip xor dst_ip [result is 16 bytes]. 2. Calculate (src_port + pkey) * (dst_port + pkey) [result is 4 bytes, using 32bit modulo arithmetics]. 3. Run crc32_raw on the resulting 20 bytes, using ckey as initialization vector. pkey and ckey are two different 32bit random values that are generated once at boot. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. C++: "an octopus made by nailing extra legs onto a dog" -- Steve Taylor, 1998 From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 19:19:29 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3B5F16A416 for ; Wed, 15 Nov 2006 19:19:29 +0000 (UTC) (envelope-from listas@itm.net.br) Received: from venom.itm.net.br (venom.itm.net.br [201.30.187.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8107B43D72 for ; Wed, 15 Nov 2006 19:19:24 +0000 (GMT) (envelope-from listas@itm.net.br) Received: (qmail 8642 invoked by uid 89); 15 Nov 2006 19:19:22 -0000 Received: by simscan 1.2.0 ppid: 8633, pid: 8634, t: 5.2046s scanners: attach: 1.2.0 clamav: 0.88.5/m:41/d:2161 spam: 3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on venom.itm.net.br X-Spam-Level: X-Spam-Status: No, score=-0.7 required=7.0 tests=AWL,BAYES_50, RCVD_IN_SORBS_DUL autolearn=no version=3.1.3 Received: from 201-20-160-70.itm.net.br (HELO IRONMAN) (201.20.160.70) by venom.itm.net.br with SMTP; 15 Nov 2006 19:19:17 -0000 Message-ID: <035c01c708d1$ccd5a8d0$46a014c9@IRONMAN> From: "Cesar Fazan" To: Date: Wed, 15 Nov 2006 16:19:17 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Subject: Multipath support for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 19:19:29 -0000 Hello, Is there any patch to a kernel level multipath solution for FreeBSD 6 out there? Or does anyone think in implement that in a near future? So far as I know, there is an old patch for FreeBSD 4.8 ... for FreeBSD 6 I can simulate a multipath with ipfw prob or with pf load-balancing, but its not exactly what Im looking for. OpenBSD 4.0 has now support for equal-cost multipath by default, but I needed an unequal-cost multipath solution, like linux can do (iproute2 weight based multipath). Any help/clues for a FreeBSD solution? Thanks. From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 20:37:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66A6516A407 for ; Wed, 15 Nov 2006 20:37:27 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 101FB43D79 for ; Wed, 15 Nov 2006 20:37:26 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 15 Nov 2006 12:34:43 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id kAFKbQsx009367; Wed, 15 Nov 2006 12:37:26 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id kAFKbHOL009356; Wed, 15 Nov 2006 12:37:17 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200611152037.kAFKbHOL009356@ambrisko.com> In-Reply-To: <003401c70754$56a85c30$8478020a@medco.com> To: Raymond Sundland Date: Wed, 15 Nov 2006 12:37:17 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: freebsd-hackers@freebsd.org Subject: Re: FW: IPMI kernel module errors on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 20:37:27 -0000 Raymond Sundland writes: | I purchased a new Supermicro Superserver SS6015B-T (motherboard is X7DBR-E) | about 3 weeks ago with the IPMI module (part called SIMSO) and have had a | hard time getting the IPMI functionality to work in RELENG_6. | | Particularly, when I attempt to 'kldload ipmi' I get the following output in | dmesg: | | ipmi0: on isa0 | ipmi0: KCS mode found at mem 0xca2 alignment 0x4 on isa | ipmi0: KCS: Failed to start write | ipmi0: KCS Error retry exhausted | ipmi0: KCS: Failed to start write | ipmi0: KCS Error retry exhausted | ipmi0: KCS: Failed to start write | ipmi0: KCS Error retry exhausted | ipmi0: Timed out waiting for GET_DEVICE_ID | | >From the dmesg, it appears it's finding the IPMI device, but unable to | interact with it. Meanwhile, no device shows up in /dev so ipmitool does | not work, either. | | For reference, here is my uname: | | FreeBSD exodus 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #9: Fri Nov 10 10:56:39 | PST 2006 root@exodus:/usr/obj/usr/src/sys/EXODUS amd64 | | This is a RELENG_6 build with a CVSUP done just before the compile date of | the kernel. | | The SIMSO IPMI card itself works, I can access it via the web management | console, I just can not get the kernel driver to work with it. Any help | and/or references would be greatly appreciated. Could you try it static in the kernel and then with and without ACPI enabled? Doug A. From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 21:15:45 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF0AF16A47B for ; Wed, 15 Nov 2006 21:15:45 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3674E43D8C for ; Wed, 15 Nov 2006 21:15:15 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 956521FFD8E; Wed, 15 Nov 2006 22:15:10 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id E03501FFD7C; Wed, 15 Nov 2006 22:15:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id BD3D0444885; Wed, 15 Nov 2006 21:14:31 +0000 (UTC) Date: Wed, 15 Nov 2006 21:14:31 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Tom Judge In-Reply-To: <455AE63D.3080501@tomjudge.com> Message-ID: <20061115210720.D18512@maildrop.int.zabbadoz.net> References: <455AE63D.3080501@tomjudge.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-hackers@freebsd.org, jthomson@mintel.com Subject: Re: [patch] Path MTU Discovery when routing over IPSec connections X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 21:15:46 -0000 On Wed, 15 Nov 2006, Tom Judge wrote: Hi, > I have been looking into some problems with PMTU Discovery when routing > packets over IPSec (gif) tunnels, I have submitted the details to the open PR I'll handle this. >From your patch I assume you are on RELENG_6. In HEAD that part had been re-written already. I have to check if the entire code path could be MFCed or just your change needs to be applied but it'll has to wait until after 6.2-RELEASE. I do not want to break any other (edge) case there just before the release and I guess re@ wouldn't want me to either;) /bz -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 21:49:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA52716A403 for ; Wed, 15 Nov 2006 21:49:35 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEF4A43DA5 for ; Wed, 15 Nov 2006 21:49:07 +0000 (GMT) (envelope-from tom@tomjudge.com) Received: from [172.23.170.141] (helo=anti-virus02-08) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1GkSd0-0005eg-9L; Wed, 15 Nov 2006 21:49:06 +0000 Received: from [82.43.34.109] (helo=[192.168.0.2]) by asmtp-out5.blueyonder.co.uk with esmtp (Exim 4.52) id 1GkScz-0008OK-MC; Wed, 15 Nov 2006 21:49:05 +0000 Message-ID: <455B8CC0.9060607@tomjudge.com> Date: Wed, 15 Nov 2006 21:55:12 +0000 From: Tom Judge User-Agent: Thunderbird 1.5.0.7 (X11/20060922) MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <455AE63D.3080501@tomjudge.com> <20061115210720.D18512@maildrop.int.zabbadoz.net> In-Reply-To: <20061115210720.D18512@maildrop.int.zabbadoz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, jthomson@mintel.com Subject: Re: [patch] Path MTU Discovery when routing over IPSec connections X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 21:49:36 -0000 Bjoern A. Zeeb wrote: > On Wed, 15 Nov 2006, Tom Judge wrote: > > I'll handle this. > >> From your patch I assume you are on RELENG_6. In HEAD that part had > been re-written already. > I have to check if the entire code path could be MFCed or just your > change needs to be applied but it'll has to wait until after > 6.2-RELEASE. I do not want to break any other (edge) case there just > before the release and I guess re@ wouldn't want me to either;) > > /bz > Thanks for dealing with this. The patch is indeed against RELENG_6, I may be able to setup a test network to test any patches if this would be helpful. Regards Tom From owner-freebsd-hackers@FreeBSD.ORG Wed Nov 15 22:29:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE52A16A417 for ; Wed, 15 Nov 2006 22:29:41 +0000 (UTC) (envelope-from raymond@sundland.com) Received: from mail.omnimx.net (mail.omnimx.net [64.235.254.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9E9C43D79 for ; Wed, 15 Nov 2006 22:29:37 +0000 (GMT) (envelope-from raymond@sundland.com) Received: from [10.0.1.35] (pool-70-111-119-142.nwrk.east.verizon.net [70.111.119.142]) by mail.omnimx.net (Postfix) with ESMTP id BE2DE17100; Wed, 15 Nov 2006 14:29:23 -0800 (PST) Message-ID: <455B94B3.2030308@sundland.com> Date: Wed, 15 Nov 2006 17:29:07 -0500 From: "Raymond T. Sundland" User-Agent: Mail/News 3.0a1 (Macintosh/20060315) MIME-Version: 1.0 To: Doug Ambrisko References: <200611152037.kAFKbHOL009356@ambrisko.com> In-Reply-To: <200611152037.kAFKbHOL009356@ambrisko.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: FW: IPMI kernel module errors on 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Nov 2006 22:29:41 -0000 Hi Doug, I added 'device ipmi' added to kernel config file Output (ACPI enabled) ipmi0: on isa0 ipmi0: KCS mode found at mem 0xca2 alignment 0x4 on isa ipmi0: KCS: initial state: 00 ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: Failed GET_DEVICE_ID: 5 Output (ACPI disabled) ipmi0: on isa0 ipmi0: KCS mode found at mem 0xca2 alignment 0x4 on isa ipmi0: KCS: initial state: 00 ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: KCS: Failed to start write ipmi0: KCS Error retry exhausted ipmi0: Failed GET_DEVICE_ID: 5 The two look the same, but there is a definite change on the last line of the initial and new output. Doug Ambrisko wrote: > Raymond Sundland writes: > | I purchased a new Supermicro Superserver SS6015B-T (motherboard is X7DBR-E) > | about 3 weeks ago with the IPMI module (part called SIMSO) and have had a > | hard time getting the IPMI functionality to work in RELENG_6. > | > | Particularly, when I attempt to 'kldload ipmi' I get the following output in > | dmesg: > | > | ipmi0: on isa0 > | ipmi0: KCS mode found at mem 0xca2 alignment 0x4 on isa > | ipmi0: KCS: Failed to start write > | ipmi0: KCS Error retry exhausted > | ipmi0: KCS: Failed to start write > | ipmi0: KCS Error retry exhausted > | ipmi0: KCS: Failed to start write > | ipmi0: KCS Error retry exhausted > | ipmi0: Timed out waiting for GET_DEVICE_ID > | > | >From the dmesg, it appears it's finding the IPMI device, but unable to > | interact with it. Meanwhile, no device shows up in /dev so ipmitool does > | not work, either. > | > | For reference, here is my uname: > | > | FreeBSD exodus 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #9: Fri Nov 10 10:56:39 > | PST 2006 root@exodus:/usr/obj/usr/src/sys/EXODUS amd64 > | > | This is a RELENG_6 build with a CVSUP done just before the compile date of > | the kernel. > | > | The SIMSO IPMI card itself works, I can access it via the web management > | console, I just can not get the kernel driver to work with it. Any help > | and/or references would be greatly appreciated. > > Could you try it static in the kernel and then with and without ACPI > enabled? > > Doug A. > > From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 08:38:43 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 920CF16A417 for ; Thu, 16 Nov 2006 08:38:43 +0000 (UTC) (envelope-from aag.lists@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EA643D60 for ; Thu, 16 Nov 2006 08:38:42 +0000 (GMT) (envelope-from aag.lists@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so235589nzh for ; Thu, 16 Nov 2006 00:38:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=se+Dg1vLGqp7M3VRKmfxLrzbuOFN2o5JG0B9tk+k9yRcOjpf5Eq3KYosid00hDpyAHhFtb0ONtstZEPQ/MNSNJ0zessA+sYiIGT6sWYF5WjspUVBHaqgp92xdjwhA8FUwRJeryuC7fQnX0HW4XosCGJQ8hzpqUcLu5IYcrUEspY= Received: by 10.35.115.18 with SMTP id s18mr304780pym.1163666322235; Thu, 16 Nov 2006 00:38:42 -0800 (PST) Received: by 10.35.59.14 with HTTP; Thu, 16 Nov 2006 00:38:42 -0800 (PST) Message-ID: <2f3a439f0611160038g5349f25bn8a1970120bc52b0@mail.gmail.com> Date: Thu, 16 Nov 2006 14:08:42 +0530 From: "Aditya Godbole" To: freebsd-hackers@freebsd.org In-Reply-To: <200611151344.kAFDiZmh097517@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2f3a439f0611150355n3dd81845ydbeb0a7b597fb087@mail.gmail.com> <200611151344.kAFDiZmh097517@lurza.secnetix.de> Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 08:38:43 -0000 On 11/15/06, Oliver Fromme wrote: > > You can also put the image of the root file system into the > kernel itself, so it doesn't have to be loaded separately. > The kernel option to allocate appropriate space is called > MD_ROOT_SIZE. Thanks. I'm investigating this option. How do I specify the filesystem image that should be put into the kernel? > Then where are you booting from? At least your kernel has > to come from somewhere, i.e. you need either networking or > some kind of media (disk, USB stick or similar). Currently I'm using u-boot to get the kernel image from the network and boot it. Since I'm using u-boot, I proabably need to do something in my kernel bootstrap code that the loader would do otherwise. -- aditya From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 08:52:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A681116A415; Thu, 16 Nov 2006 08:52:35 +0000 (UTC) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE70843D5D; Thu, 16 Nov 2006 08:52:34 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from impact.jinmei.org (unknown [2001:200:1b1:1010:20e:7bff:fedd:fe03]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 84D9515218; Thu, 16 Nov 2006 17:52:32 +0900 (JST) Date: Thu, 16 Nov 2006 17:52:32 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: Max Laier In-Reply-To: <200611142020.53178.max@love2party.net> References: <200611141709.26644.max@love2party.net> <20061114190930.GA23096@walton.maths.tcd.ie> <200611142020.53178.max@love2party.net> User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Thu, 16 Nov 2006 12:39:02 +0000 Cc: David Malone , freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 08:52:35 -0000 >>>>> On Tue, 14 Nov 2006 20:20:47 +0100, >>>>> Max Laier said: >> > Any ideas? Any papers that deal with this problem? >> >> Assuming you don't want to use one of the standard cryptographic >> ones (which I can imagine being a bit slow for something done >> per-packet), then one option might be to use a simpler hash that >> is keyed. Choose the key at boot/module load time and make it hard >> to produce collisions unless you know the key. > That's exactly what I am looking for ... now I need someone[tm] - with > better Math-Knowledge than mine - to write such a thing down in a simple > formula :-) i.e. take those bits from there and there and XOR them with > your canary yada-yada-yada ... If you want something whose behavior is mathematically guaranteed, I'd recommend universal hashing as already suggested in this thread. One example implementation is given below, assuming the hash key is source and destination IPv6 addresses and transport layer ports(*). As shown in the implementation, it's pretty simple and should run reasonably fast. Also, as long as the random values are reasonably unpredictable, the expected probability of producing the same hash value for arbitrarily-chosen two different keys is 1/65537. In general, for any prime number p as the value of LARGE_PRIME, this probability is 1/p (so if 65537 is too large, we can use a smaller number, e.g., 1009, depending on the desired balance between collision risk and memory footprint for hash buckets). (*)Technically, using in6_addr to represent an IPv6 address may not be enough; we may want to take into account zone indices (sin6_scope_id) as part of hash keys. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp #define HASHKEYLEN 38 /* sizeof(in6_addr) * 2 + sizeof(in_port_t) * 2 */ #define LARGE_PRIME 65537 /* * This should be filled with unpredictable random values between 0 * and LARGE_PRIME-1 at startup time. */ u_int32_t random_parameters[HASHKEYLEN]; u_int32_t hash(struct in6_addr *saddr, struct in6_addr *daddr, in_port_t sport, in_port_t dport) { int i, j = 0; u_int32_t accumulated = 0; u_char *cp; for (i = 0; i < sizeof(*saddr); i++) accumulated += saddr->s6_addr[i] * random_parameters[j++]; for (i = 0; i < sizeof(*saddr); i++) accumulated += daddr->s6_addr[i] * random_parameters[j++]; cp = (u_char *)&sport; for (i = 0; i < sizeof(sport); i++) accumulated += cp[i] * random_parameters[j++]; cp = (u_char *)&dport; for (i = 0; i < sizeof(dport); i++) accumulated += cp[i] * random_parameters[j++]; return (accumulated % LARGE_PRIME); } From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 13:35:28 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77F2D16A407 for ; Thu, 16 Nov 2006 13:35:28 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3C4643D45 for ; Thu, 16 Nov 2006 13:35:27 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (zuvqlw@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAGDZLlN063974; Thu, 16 Nov 2006 14:35:26 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAGDZKH4063973; Thu, 16 Nov 2006 14:35:20 +0100 (CET) (envelope-from olli) Date: Thu, 16 Nov 2006 14:35:20 +0100 (CET) Message-Id: <200611161335.kAGDZKH4063973@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, aag.lists@gmail.com In-Reply-To: <2f3a439f0611160038g5349f25bn8a1970120bc52b0@mail.gmail.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 16 Nov 2006 14:35:26 +0100 (CET) Cc: Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, aag.lists@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 13:35:28 -0000 Aditya Godbole wrote: > Oliver Fromme wrote: > > You can also put the image of the root file system into the > > kernel itself, so it doesn't have to be loaded separately. > > The kernel option to allocate appropriate space is called > > MD_ROOT_SIZE. > > Thanks. I'm investigating this option. How do I specify the filesystem > image that should be put into the kernel? You don't. It's not necessary. MD_ROOT_SIZE only reserves space in the kernel image. Then you can use strings(1) to find the offset in the kernel image, and then write your image into the reserved space with standard shell tools. For example, suposse your root FS image is 5 MB: # ls -l rootfs.img -rw------- 1 root wheel 5242880 Nov 9 15:34 rootfs.img Then add these lines to your kernel configuration: options MD_ROOT options MD_ROOT_SIZE=5120 # number of KBytes Build the kernel as usual. It will now contain 5 MB of free space, and you can find the offset with strings(1): # strings -td kernel | grep "MFS Filesystem" 4505376 MFS Filesystem goes here 9748256 MFS Filesystem had better STOP here The first number is the start offset, the second is the end offset. The difference should be exactly 5 MB in this case (5252880 bytes), which is the size of our root FS image. Now construct a new kernel binary that contains the root FS image at the right place. You can use dd(1), but it is probably easier to use head+cat+tail: # head -c 4505376 kernel > kernel.new # cat rootfs.img >> kernel.new # tail -c +9748257 kernel >> kernel.new Note that the tail(1) number must be one more than the end offset, because tail(1) starts numbering bytes with 1, not with 0. Verify that the resulting "kernel.new" file has exactly the same size as the original kernel. Of course, you can automate the whole process easily with a shell script. That's all. If you're going to mount the root FS read-only, you can also compress the image with mkuzip(8) (requires geom_uzip(4) to be present in the kernel), to save space. > > Then where are you booting from? At least your kernel has > > to come from somewhere, i.e. you need either networking or > > some kind of media (disk, USB stick or similar). > > Currently I'm using u-boot to get the kernel image from the network > and boot it. Since I'm using u-boot, I proabably need to do something > in my kernel bootstrap code that the loader would do otherwise. I don't know u-boot. What is that? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "File names are infinite in length, where infinity is set to 255 characters." -- Peter Collinson, "The Unix File System" From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 13:54:58 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CCC216A415 for ; Thu, 16 Nov 2006 13:54:58 +0000 (UTC) (envelope-from V.Haisman@sh.cvut.cz) Received: from service2.sh.cvut.cz (service2.sh.cvut.cz [147.32.127.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E39643D49 for ; Thu, 16 Nov 2006 13:54:56 +0000 (GMT) (envelope-from V.Haisman@sh.cvut.cz) Received: from localhost (localhost [127.0.0.1]) by service2.sh.cvut.cz (Postfix) with ESMTP id 9F3BA13776B; Thu, 16 Nov 2006 14:54:55 +0100 (CET) Received: from service2.sh.cvut.cz ([127.0.0.1]) by localhost (service2.sh.cvut.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05986-09; Thu, 16 Nov 2006 14:54:46 +0100 (CET) Received: from logout.sh.cvut.cz (logout.sh.cvut.cz [147.32.127.203]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by service2.sh.cvut.cz (Postfix) with ESMTP id C6D9913795A; Thu, 16 Nov 2006 14:54:46 +0100 (CET) Received: from [192.168.1.2] (localhost [127.0.0.1]) by logout.sh.cvut.cz (Postfix) with ESMTP id 5CD6461C21; Thu, 16 Nov 2006 14:54:44 +0100 (CET) Message-ID: <455C6DA1.7080303@sh.cvut.cz> Date: Thu, 16 Nov 2006 14:54:41 +0100 From: =?UTF-8?B?VsOhY2xhdiBIYWlzbWFu?= User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Cesar Fazan References: <035c01c708d1$ccd5a8d0$46a014c9@IRONMAN> In-Reply-To: <035c01c708d1$ccd5a8d0$46a014c9@IRONMAN> X-Enigmail-Version: 0.94.1.2 OpenPGP: id=733031B4 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUnMzWJm5S+0864pn5r blp/hnW2up7X7uqftbNRVUrW1LGBdGfHwJqPi3ScoYtBQzhDxGEwAAAAB3RJTUUH1QoQDDgyQtx8 HQAAAkNJREFUeJzFU0toU0EUPYu66CpGdCUUmoUJkpUDQUoNBVEUrBJsq1Ki2EIKIUZ8mydBhYi0 wVUXJVCLCrFN4DIEQdxIqdBIFsMkWD9YJClCRGKjJaviynjfe8RPogtXPcObuXPOPXd+PHj+Aeyo QNmobGLXVeANGM+GsP0B2yqHHNVoCD2LwLglVGZx7yXSlADR0uZu9C4Bpy3hUxPvH/cuUw6UoPCL h64I8KAJuMpwRU8uUMJy0OIpHVeXmulZoCc/t0LlTbJLEY1EudPRcnVjgAP5Osdl4K5HVP4+2bAI okaUA0Iq6Q59+Zy2eMWN6EpFTsa3+uD1+JKj4TPHuYTSMaLScLAaqk94YJqG4ds30hojOVgYoNJc NTztNU2TBYbhu9Aafnq08ORja37da1NwBrN/b7NVEc+b8yecuYkp08vNvLYneVZRaSH1vS0UnfHm OUPzWaZufHPmCWSdWrfeGVQQKmcsO4If8pAdXJ/xF4QQAeOVY1AQQcfirwkLUWeWVTgi6vaGt2xe BGzBEIMQorru8RxgPqY1V6uxYnwVBRZEI1ytCm3dE8mC2DgcbzCJGHdBEVDKuWDSwsrSGoqzJmNt 2jJpNueIH0qS8/0JrDKnVBdvOzIsdVr4zaX9dn9xcLLKdCtQGfutVacLE9Ja+yfbDvO4aMWrklfK /JYv15C8Kw9S10kup5Bys0N1bLdcn4HvTl/Xlh6Fpllwj5/XpH9BUXn/ym0Dvv7Rt2MywojpYiSi i7Hsscaa19zZ//y/hR+BT/ns80nmJAAAAABJRU5ErkJggg== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF303EC116F9F2391C94B3B39" X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at service2.sh.cvut.cz X-Spam-Status: No, hits=-2.6 tagged_above=-255.0 required=5.0 tests=ALL_TRUSTED, AWL, TW_PF X-Spam-Level: Cc: freebsd-hackers@freebsd.org Subject: Re: Multipath support for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 13:54:58 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF303EC116F9F2391C94B3B39 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cesar Fazan wrote, On 15.11.2006 17:19: > Hello, >=20 > Is there any patch to a kernel level multipath solution for FreeBSD 6 > out there? Or does anyone think in implement that in a near future? > So far as I know, there is an old patch for FreeBSD 4.8 ... for FreeBS= D > 6 I can simulate a multipath with ipfw prob or with pf load-balancing, > but its not exactly what Im looking for. >=20 > OpenBSD 4.0 has now support for equal-cost multipath by default, but I > needed an unequal-cost multipath solution, like linux can do (iproute2 > weight based multipath). >=20 > Any help/clues for a FreeBSD solution? >=20 > Thanks. ng_one2many or ng_hub? -- VH --------------enigF303EC116F9F2391C94B3B39 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBRVxtp0NOZDESBK8FAQKN8Qf9GC2EaEk+rZHhxp1al28Qy/FzZMysLLJU CgA/ymJ+WN4UDeKCMUCi4bMNth8bNYykUB96B0Q0gQ0QWNXl4m464C8nkuR8+aHj mlEWd5J1LRzgFxjTw1k6Ru+2PVnC/GiCrUlU2Y2EJFmbujj+UBqHAh9FV8RNqvzt dbP1fWUOLcm+YqnpiEGKGtdPxYnEm3HPEumlifvJ0LWpgHne++GWMnmhYznMmlcp 8N1u952UcqvbAIalvWrLcA+Pmum+tTxtOk6gQWClc+HOd9S+fBzJKNlXrRHNtejO WbWb4+JKcrgO4Aroov4nuSCFSktBbLjzZ1egpSp5rRME8GNiWbQBEQ== =6oj7 -----END PGP SIGNATURE----- --------------enigF303EC116F9F2391C94B3B39-- From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 13:56:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6123C16A47B for ; Thu, 16 Nov 2006 13:56:26 +0000 (UTC) (envelope-from aag.lists@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52C0143D5D for ; Thu, 16 Nov 2006 13:56:24 +0000 (GMT) (envelope-from aag.lists@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so288103nzh for ; Thu, 16 Nov 2006 05:56:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gk9AdjtvT4z/OqctHP3/MnYKVEszz60OAWZ1iBJdKhMMkjs23yxCMEXHFWUh1dO9Ex0ZguJhrrnRjJaCHMzz3lTtIluvrtBDvlCrcXYhzeJZ1oy3uTQgLnPoTUUjYS2hUa4cyYq4O9t4NbIPBhbLKsbaAHJUblwAeH8Q4XwQAUw= Received: by 10.35.103.12 with SMTP id f12mr819126pym.1163685383879; Thu, 16 Nov 2006 05:56:23 -0800 (PST) Received: by 10.35.59.14 with HTTP; Thu, 16 Nov 2006 05:56:23 -0800 (PST) Message-ID: <2f3a439f0611160556o6e643561sf45bccab2ad769ad@mail.gmail.com> Date: Thu, 16 Nov 2006 19:26:23 +0530 From: "Aditya Godbole" To: freebsd-hackers@freebsd.org In-Reply-To: <200611161335.kAGDZKH4063973@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2f3a439f0611160038g5349f25bn8a1970120bc52b0@mail.gmail.com> <200611161335.kAGDZKH4063973@lurza.secnetix.de> Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 13:56:26 -0000 On 11/16/06, Oliver Fromme wrote: > > You don't. It's not necessary. MD_ROOT_SIZE only reserves > space in the kernel image. Then you can use strings(1) to > find the offset in the kernel image, and then write your > image into the reserved space with standard shell tools. > Thanks a lot for the elaborate explanation. > > I don't know u-boot. What is that? > u-boot is a bootloader popular in embedded systems. Its often used with Linux. Regards, aditya From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 14:35:22 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 257C716A417 for ; Thu, 16 Nov 2006 14:35:22 +0000 (UTC) (envelope-from listas@itm.net.br) Received: from venom.itm.net.br (venom.itm.net.br [201.30.187.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49EE243D8E for ; Thu, 16 Nov 2006 14:34:48 +0000 (GMT) (envelope-from listas@itm.net.br) Received: (qmail 26552 invoked by uid 89); 16 Nov 2006 14:34:43 -0000 Received: by simscan 1.2.0 ppid: 26490, pid: 26491, t: 8.8826s scanners: attach: 1.2.0 clamav: 0.88.5/m:41/d:2161 spam: 3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on venom.itm.net.br X-Spam-Level: X-Spam-Status: No, score=-0.6 required=7.0 tests=AWL,BAYES_00, DATE_IN_PAST_03_06,RCVD_IN_SORBS_DUL autolearn=no version=3.1.3 Received: from 201-20-160-70.itm.net.br (HELO IRONMAN) (201.20.160.70) by venom.itm.net.br with SMTP; 16 Nov 2006 14:34:34 -0000 Message-ID: <04f001c70973$30179790$46a014c9@IRONMAN> From: "Cesar Fazan" To: =?utf-8?Q?V=C3=A1clav_Haisman?= References: <035c01c708d1$ccd5a8d0$46a014c9@IRONMAN> <455C6DA1.7080303@sh.cvut.cz> Date: Thu, 16 Nov 2006 11:34:33 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="utf-8"; reply-type=original Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Cc: freebsd-hackers@freebsd.org Subject: Re: Multipath support for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 14:35:22 -0000 Hi, I dont think ng_one2many and ng_hub is a multipath solution. I mean multipath as having two gateways on the routing table for the same destination. http://www.openbsd.org/faq/faq6.html#Multipath Thanks. ----- Original Message ----- From: "V獺clav Haisman" To: "Cesar Fazan" Cc: Sent: Thursday, November 16, 2006 1:54 PM Subject: Re: Multipath support for FreeBSD From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 14:57:59 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CD3E16A5C5 for ; Thu, 16 Nov 2006 14:57:59 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDDC543D5F for ; Thu, 16 Nov 2006 14:57:58 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (bmtuhk@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id kAGEvpgC068252; Thu, 16 Nov 2006 15:57:57 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id kAGEvp3F068251; Thu, 16 Nov 2006 15:57:51 +0100 (CET) (envelope-from olli) Date: Thu, 16 Nov 2006 15:57:51 +0100 (CET) Message-Id: <200611161457.kAGEvp3F068251@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, aag.lists@gmail.com In-Reply-To: <2f3a439f0611160556o6e643561sf45bccab2ad769ad@mail.gmail.com> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Thu, 16 Nov 2006 15:57:57 +0100 (CET) Cc: Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, aag.lists@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 14:57:59 -0000 Aditya Godbole wrote: > Oliver Fromme wrote: > > I don't know u-boot. What is that? > > u-boot is a bootloader popular in embedded systems. > Its often used with Linux. I see. Is it PXE-compliant? If so, you can use FreeBSD's PXE bootloader (/boot/pxeboot) for loading the kernel. In that case you can also load the root FS image as a separate file, so there is no need to hack it into the kernel binary. As far as I know, there is no official support for loading a FreeBSD kernel directly, without using the FreeBSD boot loader. By the way, why don't you simply mount the root FS via NFS? Is the NIC not supported? What NIC is it? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "FreeBSD is Yoda, Linux is Luke Skywalker" -- Daniel C. Sobral From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 16:36:45 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11D9916A415 for ; Thu, 16 Nov 2006 16:36:45 +0000 (UTC) (envelope-from aag.lists@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47DBE43D5F for ; Thu, 16 Nov 2006 16:36:44 +0000 (GMT) (envelope-from aag.lists@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so324438nzh for ; Thu, 16 Nov 2006 08:36:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=I71sFVmc9cWf8oTTS/qiMWEHl2mN8FEMox/dB0qcNDO9HETNJW/LjPGKmhLNFi3RLRYkaAFCPeBnAZi4SIxQhq1RU4OhbfP3ZjF/51f/JhyR/Mpocezqb87z2HTWpWxZUmqIDCLvJ/Oay7tGfSbr2R7/H9W9azdNkR/NarWAHik= Received: by 10.35.8.13 with SMTP id l13mr1112714pyi.1163695001644; Thu, 16 Nov 2006 08:36:41 -0800 (PST) Received: by 10.35.59.14 with HTTP; Thu, 16 Nov 2006 08:36:41 -0800 (PST) Message-ID: <2f3a439f0611160836r3c88c3f4ja9cc5a5f4b78a244@mail.gmail.com> Date: Thu, 16 Nov 2006 22:06:41 +0530 From: "Aditya Godbole" To: freebsd-hackers@freebsd.org In-Reply-To: <200611161457.kAGEvp3F068251@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2f3a439f0611160556o6e643561sf45bccab2ad769ad@mail.gmail.com> <200611161457.kAGEvp3F068251@lurza.secnetix.de> Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 16:36:45 -0000 On 11/16/06, Oliver Fromme wrote: > > I see. Is it PXE-compliant? If so, you can use FreeBSD's > PXE bootloader (/boot/pxeboot) for loading the kernel. In > that case you can also load the root FS image as a separate > file, so there is no need to hack it into the kernel binary. > u-boot is not PXE compliant. I have never come across anyone trying to use it to boot FreeBSD before. Unfortunately, that is the only bootloader that I know of that works on the architecture I'm working on. > As far as I know, there is no official support for loading > a FreeBSD kernel directly, without using the FreeBSD boot > loader. > Yes. However for putting FreeBSD on embedded systems, I have to make tweaks to allow it to boot using other bootloaders. I'm working on putting FreeBSD on the MPC8555 e500-PPC based board, which is not supported at all. > By the way, why don't you simply mount the root FS via NFS? > Is the NIC not supported? What NIC is it? > Quite a bit of the hardware is not supported in FreeBSD right now. Probably this discussion should go on the embedded mailing list, but I thought I would get a better response here for my original specific question. (Can't say I was wrong). Cheers. -- aditya From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 18:06:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7204716A40F for ; Thu, 16 Nov 2006 18:06:14 +0000 (UTC) (envelope-from garyj@jennejohn.org) Received: from mail08b.verio.de (mail08b.verio.de [213.198.55.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 13A1843D6A for ; Thu, 16 Nov 2006 18:06:07 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mx106.stngva01.us.mxservers.net (198.173.112.43) by mail08b.verio.de (RS ver 1.0.95vs) with SMTP id 4-079842364; Thu, 16 Nov 2006 19:06:06 +0100 (CET) Received: from www.jennejohn.org [213.198.5.174] (EHLO peedub.jennejohn.org) by mx106.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id d78ac554.11821.344.mx106.stngva01.us.mxservers.net; Thu, 16 Nov 2006 13:05:49 -0500 (EST) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.8/8.11.6) with ESMTP id kAGI5w9b013112; Thu, 16 Nov 2006 19:05:58 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200611161805.kAGI5w9b013112@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: "Aditya Godbole" In-reply-to: Your message of "Thu, 16 Nov 2006 22:06:41 +0530." <2f3a439f0611160836r3c88c3f4ja9cc5a5f4b78a244@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Nov 2006 19:05:58 +0100 From: Gary Jennejohn X-Spam: [F=0.0100000000; heur=0.500(-19800); stat=0.010; spamtraq-heur=0.500(2006111518)] X-MAIL-FROM: X-SOURCE-IP: [213.198.5.174] X-Loop-Detect: 1 X-DistLoop-Detect: 1 Cc: freebsd-hackers@freebsd.org Subject: Re: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gary Jennejohn List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 18:06:14 -0000 "Aditya Godbole" writes: > On 11/16/06, Oliver Fromme wrote: > > > > I see. Is it PXE-compliant? If so, you can use FreeBSD's > > PXE bootloader (/boot/pxeboot) for loading the kernel. In > > that case you can also load the root FS image as a separate > > file, so there is no need to hack it into the kernel binary. > > > > u-boot is not PXE compliant. I have never come across anyone trying to > use it to boot FreeBSD before. Unfortunately, that is the only > bootloader that I know of that works on the architecture I'm working > on. > > > As far as I know, there is no official support for loading > > a FreeBSD kernel directly, without using the FreeBSD boot > > loader. > > > > Yes. However for putting FreeBSD on embedded systems, I have to make > tweaks to allow it to boot using other bootloaders. I'm working on > putting FreeBSD on the MPC8555 e500-PPC based board, which is not > supported at all. > u-boot is unfortuately extremely Linux-centric. I work closely with the person who "invented" u-boot, Wolfgang Denk, and know that he'd just love to see the *BSD support improved. Unfortunately, u-boot makes heavy use of Linux' support for rootdev, etc., which AFAIK is missing in FreeBSD. It heavily depends on passing lots of necessary information in the Linux command line to influence the boot process. BTW do you have any patches which you could contribute, or have you already done that? --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 18:35:36 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A52D16A4B3 for ; Thu, 16 Nov 2006 18:35:36 +0000 (UTC) (envelope-from raj@semihalf.com) Received: from mail.semihalf.com (mail.semihalf.com [62.233.211.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61D9D43D45 for ; Thu, 16 Nov 2006 18:35:35 +0000 (GMT) (envelope-from raj@semihalf.com) Received: from localhost (localhost [127.0.0.1]) by mail.semihalf.com (Postfix) with ESMTP id 03ED614361; Thu, 16 Nov 2006 19:35:33 +0100 (CET) Received: from mail.semihalf.com ([127.0.0.1]) by localhost (mail.semihalf.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12686-01; Thu, 16 Nov 2006 19:35:31 +0100 (CET) Message-ID: <455CAF73.9060808@semihalf.com> Date: Thu, 16 Nov 2006 19:35:31 +0100 From: Rafal Jaworowski MIME-Version: 1.0 To: Gary Jennejohn References: <200611161805.kAGI5w9b013112@peedub.jennejohn.org> In-Reply-To: <200611161805.kAGI5w9b013112@peedub.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at semihalf.com Cc: Aditya Godbole , freebsd-hackers@freebsd.org Subject: FreeBSD and U-Boot -- was: Ramdisk support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 18:35:36 -0000 Gary Jennejohn wrote: > > u-boot is unfortuately extremely Linux-centric. I work closely with the > person who "invented" u-boot, Wolfgang Denk, and know that he'd just love > to see the *BSD support improved. > > Unfortunately, u-boot makes heavy use of Linux' support for rootdev, etc., > which AFAIK is missing in FreeBSD. It heavily depends on passing lots of > necessary information in the Linux command line to influence the boot > process. > Hi Gary, we have working patches for U-Boot that extend 'bootm' to recognize and handle parsing FreeBSD/powerpc ELF image and passing control to it; among others these compose FreeBSD-style metadata, the goal is aldo to convert some U-Boot env vars to FreeBSD kenv equivalents etc. but it's not fully supported yet. On a related note - we are having a discussion on freebsd-ppc list towards setting the common convention for registers' usage etc. so we can handle booting PowerPC kernel from different bootloaders (it's strictly OF/Mac oriented now). Once this is agreed and prototyped/tested the changes will by contributed to U-Boot (I'm sure, too, Wolfgang will be glad to see those;) kind regards, Rafal From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 20:01:10 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5446B16A412 for ; Thu, 16 Nov 2006 20:01:10 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF12743D6B for ; Thu, 16 Nov 2006 20:01:09 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141]) by mxout4.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kAGK19Yc001988 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 16 Nov 2006 12:01:09 -0800 X-Auth-Received: from [128.208.4.96] (dzihan.cs.washington.edu [128.208.4.96]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kAGK19ed018054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Thu, 16 Nov 2006 12:01:09 -0800 Message-ID: <455CC385.10309@u.washington.edu> Date: Thu, 16 Nov 2006 12:01:09 -0800 From: Garrett Cooper User-Agent: Thunderbird 1.5.0.8 (X11/20061108) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <200611141709.26644.max@love2party.net> <20061114190930.GA23096@walton.maths.tcd.ie> <200611142020.53178.max@love2party.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.2.2.285561, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2006.11.16.114932 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 20:01:10 -0000 JINMEI Tatuya / ???? wrote: >>>>>> On Tue, 14 Nov 2006 20:20:47 +0100, >>>>>> Max Laier said: >>>>>> > > >>>> Any ideas? Any papers that deal with this problem? >>>> >>> Assuming you don't want to use one of the standard cryptographic >>> ones (which I can imagine being a bit slow for something done >>> per-packet), then one option might be to use a simpler hash that >>> is keyed. Choose the key at boot/module load time and make it hard >>> to produce collisions unless you know the key. >>> > > >> That's exactly what I am looking for ... now I need someone[tm] - with >> better Math-Knowledge than mine - to write such a thing down in a simple >> formula :-) i.e. take those bits from there and there and XOR them with >> your canary yada-yada-yada ... >> > > If you want something whose behavior is mathematically guaranteed, I'd > recommend universal hashing as already suggested in this thread. > > One example implementation is given below, assuming the hash key is > source and destination IPv6 addresses and transport layer ports(*). > As shown in the implementation, it's pretty simple and should run > reasonably fast. Also, as long as the random values are reasonably > unpredictable, the expected probability of producing the same hash > value for arbitrarily-chosen two different keys is 1/65537. In > general, for any prime number p as the value of LARGE_PRIME, this > probability is 1/p (so if 65537 is too large, we can use a smaller > number, e.g., 1009, depending on the desired balance between collision > risk and memory footprint for hash buckets). > > (*)Technically, using in6_addr to represent an IPv6 address may not be > enough; we may want to take into account zone indices (sin6_scope_id) > as part of hash keys. > > JINMEI, Tatuya > Communication Platform Lab. > Corporate R&D Center, Toshiba Corp. > jinmei@isl.rdc.toshiba.co.jp > > #define HASHKEYLEN 38 /* sizeof(in6_addr) * 2 + sizeof(in_port_t) * 2 */ > #define LARGE_PRIME 65537 > > /* > * This should be filled with unpredictable random values between 0 > * and LARGE_PRIME-1 at startup time. > */ > u_int32_t random_parameters[HASHKEYLEN]; > > u_int32_t > hash(struct in6_addr *saddr, struct in6_addr *daddr, > in_port_t sport, in_port_t dport) > { > int i, j = 0; > u_int32_t accumulated = 0; > u_char *cp; > > for (i = 0; i < sizeof(*saddr); i++) > accumulated += saddr->s6_addr[i] * random_parameters[j++]; > for (i = 0; i < sizeof(*saddr); i++) > accumulated += daddr->s6_addr[i] * random_parameters[j++]; > cp = (u_char *)&sport; > for (i = 0; i < sizeof(sport); i++) > accumulated += cp[i] * random_parameters[j++]; > cp = (u_char *)&dport; > for (i = 0; i < sizeof(dport); i++) > accumulated += cp[i] * random_parameters[j++]; > > return (accumulated % LARGE_PRIME); > } Jinmei, Wouldn't you get some overflow if (pardon my set notation) "INT_MAX < {saddr,daddr}->s6_addr[i] * random_parameters[j++]", which would implicitly introduce collision into your algorithm. Or is the overall set size sufficiently large not to worry about this particular issue? -Garrett From owner-freebsd-hackers@FreeBSD.ORG Thu Nov 16 21:16:26 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62FA416A51F; Thu, 16 Nov 2006 21:16:26 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 50B2043D79; Thu, 16 Nov 2006 21:16:19 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 16 Nov 2006 21:16:18 +0000 (GMT) Date: Thu, 16 Nov 2006 21:16:17 +0000 From: David Malone To: "JINMEI Tatuya / ?$B?@L@C#:H" Message-ID: <20061116211617.GA86177@walton.maths.tcd.ie> References: <200611141709.26644.max@love2party.net> <20061114190930.GA23096@walton.maths.tcd.ie> <200611142020.53178.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: Max Laier , freebsd-net@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: ipv6 connection hash function wanted ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2006 21:16:26 -0000 On Thu, Nov 16, 2006 at 05:52:32PM +0900, JINMEI Tatuya / ?$B?@L@C#:H wrote: > If you want something whose behavior is mathematically guaranteed, I'd > recommend universal hashing as already suggested in this thread. Yep - I agree. I'll try and sort something out for Max - it may need some careful tweaks if it is to be symetric in src/dst ports and ips. David. From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 17 03:20:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21C6F16A416 for ; Fri, 17 Nov 2006 03:20:31 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [80.237.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7375243D49 for ; Fri, 17 Nov 2006 03:20:28 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: (qmail 29605 invoked by uid 0); 17 Nov 2006 03:20:18 -0000 Received: from fnord.cryptophone.de (HELO ?10.1.1.71?) (erdgeist@erdgeist.org@62.220.7.20) by elektropost.org with AES256-SHA encrypted SMTP; 17 Nov 2006 03:20:18 -0000 Message-ID: <455D2A7A.90109@erdgeist.org> Date: Fri, 17 Nov 2006 04:20:26 +0100 From: Dirk Engling User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Phantom Jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2006 03:20:31 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rumors went around and tales were told about jails magically booing around in prison list, even after they deceased. Most people consider this a rather aesthetical issue, however if you run your jails from directories that need to be unmounted (e.g. from md-images, on external drives, from gbde or geli images) those phantom jails become rather annoying, since you cannot umount their roots. Investigations have shown, that 1) sockets hold a lock on (increase reference counter in) the ucred structure of the calling process 2) This ucred structure in turn keeps a lock on (increases reference counter in) the prison struct representing the jail this process belongs to 3) The prison struct in turn keeps a handle to jails root directory. If a process holding a tcp connection is killed, the connection is being inherited by the kernel. It waits there for tcp tear down or tcp time out to occur. Only then socket's lock on ucred is released, which releases ucreds lock on prison struct (thus terminating phantom jails) which may, if it is the last ucred referencing the prison, release the prison and its handle to the root directory (solving my un-umount-able images). There were kinds of phantom jails being sighted, that did not vanish after tcp timeout, that might be deadlocked by open files or mmaped regions. However the above case happens regularly with my mail server jail that holds hundreds of imap-connections, one disconnected dsl-user can prevent tcp tear down to happen successfully thus forcing me to force umount the mail server. My suggestion would be (I will provide a patch, if discussion produces no major disagreement) to release ucred structs held by sockets as soon as the process dies. They are being used for accounting purposes only, anyway. The same may apply to the other types of phantom jails, as well. I could not create those deliberately and therefore can not exactly spot the proper location to fix. Comments? erdgeist P.S.: if you want to reproduce a phantom jail try the following: 1) create and start a jail 2) Start a ssh/web/whatever server within the jail 3) Connect to that server from the host system. 4) Keep this connection open while you kill the jail 5) Do a 'jls' and compare its output to "ps axuu | grep J" 6) Kill the process that connected to the service. 7) Do a 'jls' again. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFFXSp5ImmQdUyYEgkRAtOAAJ4iSzyu2LOf+RBNArvYAk1Tv8cssACfRxJa 12OGEwWugcIDhlGGTHJrz0o= =gXK8 -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 17 06:35:14 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 602D716A403 for ; Fri, 17 Nov 2006 06:35:14 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E594D43D53 for ; Fri, 17 Nov 2006 06:35:13 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 800211FFE00; Fri, 17 Nov 2006 07:35:11 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 6499C1FFE6C; Fri, 17 Nov 2006 07:35:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id B3F39444889; Fri, 17 Nov 2006 06:33:34 +0000 (UTC) Date: Fri, 17 Nov 2006 06:33:34 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Dirk Engling In-Reply-To: <455D2A7A.90109@erdgeist.org> Message-ID: <20061117062952.H18512@maildrop.int.zabbadoz.net> References: <455D2A7A.90109@erdgeist.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-hackers@freebsd.org Subject: Re: Phantom Jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2006 06:35:14 -0000 On Fri, 17 Nov 2006, Dirk Engling wrote: Hi, > Rumors went around and tales were told about jails magically booing > around in prison list, even after they deceased. ... > My suggestion would be (I will provide a patch, if discussion produces > no major disagreement) to release ucred structs held by sockets as soon > as the process dies. They are being used for accounting purposes only, > anyway. The same may apply to the other types of phantom jails, as well. > I could not create those deliberately and therefore can not exactly spot > the proper location to fix. > > Comments? > > P.S.: if you want to reproduce a phantom jail try the following: > 1) create and start a jail > 2) Start a ssh/web/whatever server within the jail > 3) Connect to that server from the host system. > 4) Keep this connection open while you kill the jail > 5) Do a 'jls' and compare its output to "ps axuu | grep J" > 6) Kill the process that connected to the service. > 7) Do a 'jls' again. while this works you can also reproduce it if you log out of the jail wait for the sockets to go away entirely and then stop the jail because what keeps the jail up is not a socket but is related to devfs and ?tys. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89528 -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 17 19:26:47 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 067FF16A407 for ; Fri, 17 Nov 2006 19:26:47 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [80.237.196.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4086243D6A for ; Fri, 17 Nov 2006 19:26:40 +0000 (GMT) (envelope-from erdgeist@erdgeist.org) Received: (qmail 69096 invoked by uid 0); 17 Nov 2006 19:26:29 -0000 Received: from i577b070c.versanet.de (HELO ?10.1.1.103?) (erdgeist@erdgeist.org@87.123.7.12) by elektropost.org with AES256-SHA encrypted SMTP; 17 Nov 2006 19:26:29 -0000 Message-ID: <455E0CEE.9010304@erdgeist.org> Date: Fri, 17 Nov 2006 20:26:38 +0100 From: Dirk Engling User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 CC: freebsd-hackers@freebsd.org References: <455D2A7A.90109@erdgeist.org> <20061117062952.H18512@maildrop.int.zabbadoz.net> In-Reply-To: <20061117062952.H18512@maildrop.int.zabbadoz.net> X-Enigmail-Version: 0.94.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Phantom Jails X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2006 19:26:47 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bjoern A. Zeeb wrote: > while this works you can also reproduce it if you log out of the jail > wait for the sockets to go away entirely and then stop the jail > because what keeps the jail up is not a socket but is related to devfs > and ?tys. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/89528 So you're implying, that releasing the ucreds, that in this case obviously prevent prisons from disappearing, won't work due to stuff that "is releated to devfs and ttys"? Or was that a kind request to have a look into potential ucred leaks in tty and devfs code, as well? :) What unwanted effects could an early release of ucred structures cause? Maybe it was the wrong list to put that question on, after all, which would be appropriate? Regards erdgeist -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) iD8DBQFFXgztImmQdUyYEgkRArfGAJ0VzR2klSbK/39KSfIGiumrp9ET4ACdHEW5 Hg1YMGukSTzh44TxRHFkGpE= =60Hb -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 17 18:56:05 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 754AF16A403 for ; Fri, 17 Nov 2006 18:56:05 +0000 (UTC) (envelope-from phirerunner@comcast.net) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9897D43D80 for ; Fri, 17 Nov 2006 18:55:59 +0000 (GMT) (envelope-from phirerunner@comcast.net) Received: from localhost.my.domain (c-67-165-107-143.hsd1.pa.comcast.net[67.165.107.143]) by comcast.net (rwcrmhc12) with SMTP id <20061117185556m1200m3he4e>; Fri, 17 Nov 2006 18:55:57 +0000 Date: Fri, 17 Nov 2006 13:55:53 -0500 From: Jared Yanovich To: freebsd-hackers@freebsd.org Message-Id: <20061117135553.14cfdaa1.phirerunner@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 17 Nov 2006 20:58:38 +0000 Subject: save process exit status in kevent NOTE_EXIT X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2006 18:56:05 -0000 Any reason why this may be a bad idea? I think it'd be useful for a pwait(1)-like utility (from Solaris). Index: lib/libc/sys/kqueue.2 =================================================================== RCS file: /home/ncvs/src/lib/libc/sys/kqueue.2,v retrieving revision 1.44 diff -u -p -r1.44 kqueue.2 --- lib/libc/sys/kqueue.2 17 Sep 2006 21:27:34 -0000 1.44 +++ lib/libc/sys/kqueue.2 17 Nov 2006 18:50:48 -0000 @@ -364,6 +364,8 @@ The events to monitor are: .Bl -tag -width XXNOTE_TRACKERR .It NOTE_EXIT The process has exited. +The exit status will be stored in +.Va data . .It NOTE_FORK The process has called .Fn fork . Index: sys/kern/kern_event.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_event.c,v retrieving revision 1.106 diff -u -p -r1.106 kern_event.c --- sys/kern/kern_event.c 25 Sep 2006 01:29:48 -0000 1.106 +++ sys/kern/kern_event.c 17 Nov 2006 18:50:49 -0000 @@ -396,6 +396,7 @@ filt_proc(struct knote *kn, long hint) if (!(kn->kn_status & KN_DETACHED)) knlist_remove_inevent(&p->p_klist, kn); kn->kn_flags |= (EV_EOF | EV_ONESHOT); + kn->kn_data = kn->kn_ptr.p_proc->p_xstat; kn->kn_ptr.p_proc = NULL; return (1); } From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 17 19:32:21 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABC8516A403 for ; Fri, 17 Nov 2006 19:32:21 +0000 (UTC) (envelope-from wyt168@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 067DC43D78 for ; Fri, 17 Nov 2006 19:32:14 +0000 (GMT) (envelope-from wyt168@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so712330uge for ; Fri, 17 Nov 2006 11:32:14 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=tHw9T3knY9y9uEmLgfqJswqRhDLowtCVB07oEhA5BXgbgOzPfvmbE0EYpG1ih1Vi5AZ9WLdx/HJtsmHaUNEs4bNNaQ91iAZOxkbh5+F8mA1UeS+JvD7XpJnIxAJJ6qht16saPgj/peHzl2yqK57DNlvefQY8kw/0MBa1FFaB6QQ= Received: by 10.67.117.2 with SMTP id u2mr1598329ugm.1163791933161; Fri, 17 Nov 2006 11:32:13 -0800 (PST) Received: by 10.67.87.1 with HTTP; Fri, 17 Nov 2006 11:32:13 -0800 (PST) Message-ID: <3dcda0520611171132q6f337e23j39f6fa8720feaf15@mail.gmail.com> Date: Fri, 17 Nov 2006 11:32:13 -0800 From: Winston To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Fri, 17 Nov 2006 20:58:49 +0000 Subject: How to break into kernel debugger X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Nov 2006 19:32:21 -0000 I've set up kgdb for remote debugging over serial lines (null modem) between two machines. I can get into the debugger when I boot the target machine with "boot -d" and from the debugging machine with the command "target remote /dev/cuad1". However, once I let the debugger go with "continue" command, I can't break into the debugger anymore. If hit ctl-c once on the debugging machine, there is no response. Hit it again, I got: ^C Interrupted while waiting for the program. Give up (and stop debugging it)? (y or n) n The gdb doc mentioned this and stated: "Whenever gdb is waiting for the remote program, if you type the interrupt character (often Ctrl-c), gdb attempts to stop the program. This may or may not succeed, depending in part on the hardware and the serial drivers the remote system uses." However, it doesn't offer a suggestion as to how to make it work. I tried to set remotebreak to on with: set remotebreak on; But it still doesn't work. I search this mailing list and it appears there was an earlier thread "escape to kernel debugger" that enquired about the same thing. However, it was a while ago, and the options mentioned in the thread are not in the config file anymore. Any suggestions? From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 18 09:54:05 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7F6C016A407 for ; Sat, 18 Nov 2006 09:54:05 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65EFD43D5C for ; Sat, 18 Nov 2006 09:54:02 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id kAI9s219079768; Sat, 18 Nov 2006 12:54:02 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id kAI9s07c079766; Sat, 18 Nov 2006 12:54:00 +0300 (MSK) (envelope-from yar) Date: Sat, 18 Nov 2006 12:54:00 +0300 From: Yar Tikhiy To: Kostik Belousov Message-ID: <20061118095400.GE68439@comp.chem.msu.su> References: <20061029140716.GA12058@comp.chem.msu.su> <20061029152227.GA11826@walton.maths.tcd.ie> <006801c6fb77$e4e30100$1200a8c0@gsicomp.on.ca> <20061030130519.GE27062@comp.chem.msu.su> <20061030134737.GF1627@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061030134737.GF1627@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.9i Cc: David Malone , hackers@freebsd.org Subject: Re: File trees: the deeper, the weirder X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2006 09:54:05 -0000 On Mon, Oct 30, 2006 at 03:47:37PM +0200, Kostik Belousov wrote: > On Mon, Oct 30, 2006 at 04:05:19PM +0300, Yar Tikhiy wrote: > > On Sun, Oct 29, 2006 at 11:32:58AM -0500, Matt Emmerton wrote: > > > [ Restoring some OP context.] > > > > > > > On Sun, Oct 29, 2006 at 05:07:16PM +0300, Yar Tikhiy wrote: > > > > > > > > > As for the said program, it keeps its 1 Hz pace, mostly waiting on > > > > > "vlruwk". It's killable, after a delay. The system doesn't show ... > > > > > > > > > > Weird, eh? Any ideas what's going on? > > > > > > > > I would guess that you need a new vnode to create the new file, but no > > > > vnodes are obvious candidates for freeing because they all have a child > > > > directory in use. Is there some sort of vnode clearing that goes on every > > > > second if we are short of vnodes? > > > > > > See sys/vfs_subr.c, subroutine getnewvnode(). We call msleep() if we're > > > waiting on vnodes to be created (or recycled). And just look at the 'hz' > > > parameter passed to msleep()! > > > > > > The calling process's mkdir() will end up waiting in getnewvnode() (in > > > "vlruwk" state) while the vnlru kernel thread does it's thing (which is to > > > recycle vnodes.) > > > > > > Either the vnlru kernel thread has to work faster, or the caller has to > > > sleep less, in order to avoid this lock-step behaviour. > > > > I'm afraid that, though your analysis is right, you arrive at wrong > > conclusions. The process waits for the whole second in getnewvnode() > > because the vnlru thread cannot free as much vnodes as it wants to. > > vnlru_proc() will wake up sleepers on vnlruproc_sig (i.e., > > getnewvnode()) only if (numvnodes <= desiredvnodes * 9 / 10). > > Whether this condition is attainable depends on vlrureclaim() (called > > from the vnlru thread) freeing vnodes at a sufficient rate. Perhaps > > vlrureclaim() just can't keep the pace at this conditions. > > debug.vnlru_nowhere increasing is an indication of that. Consequently, > > each getnewvnode() call sleeps 1 second, then grabs a vnode beyond > > desiredvnodes. It's no surprise that the 1 second delays start to > > appear after approx. kern.maxvnodes directories were created. > > I think that David is right. The references _from_ the directory make it immune > to vnode reclamation. Try this patch. It is very unfair for lsof. > > Index: sys/kern/vfs_subr.c > =================================================================== > RCS file: /usr/local/arch/ncvs/src/sys/kern/vfs_subr.c,v > retrieving revision 1.685 > diff -u -r1.685 vfs_subr.c > --- sys/kern/vfs_subr.c 2 Oct 2006 07:25:58 -0000 1.685 > +++ sys/kern/vfs_subr.c 30 Oct 2006 13:44:59 -0000 > @@ -582,7 +582,7 @@ > * If it's been deconstructed already, it's still > * referenced, or it exceeds the trigger, skip it. > */ > - if (vp->v_usecount || !LIST_EMPTY(&(vp)->v_cache_src) || > + if (vp->v_usecount || /* !LIST_EMPTY(&(vp)->v_cache_src) || */ > (vp->v_iflag & VI_DOOMED) != 0 || (vp->v_object != NULL && > vp->v_object->resident_page_count > trigger)) { > VI_UNLOCK(vp); > @@ -607,7 +607,7 @@ > * interlock, the other thread will be unable to drop the > * vnode lock before our VOP_LOCK() call fails. > */ > - if (vp->v_usecount || !LIST_EMPTY(&(vp)->v_cache_src) || > + if (vp->v_usecount || /* !LIST_EMPTY(&(vp)->v_cache_src) || */ > (vp->v_object != NULL && > vp->v_object->resident_page_count > trigger)) { > VOP_UNLOCK(vp, LK_INTERLOCK, td); By the way, what do you think v_cache_src is for? The only two places it is used in the kernel are in the unused function cache_leaf_test() and this one, in vlrureclaim(). Is its main purpose just to keep directory vnodes that are referenced by nc_dvp in some namecache entries? -- Yar From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 18 11:06:11 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 23C5616A49E for ; Sat, 18 Nov 2006 11:06:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (fw.zoral.com.ua [213.186.206.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F89F43D6A for ; Sat, 18 Nov 2006 11:06:04 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id kAIB5kEa025347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 18 Nov 2006 13:05:46 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8) with ESMTP id kAIB5kjU047776; Sat, 18 Nov 2006 13:05:46 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.8/8.13.8/Submit) id kAIB5iSN047775; Sat, 18 Nov 2006 13:05:44 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 18 Nov 2006 13:05:44 +0200 From: Kostik Belousov To: Yar Tikhiy Message-ID: <20061118110544.GN1841@deviant.kiev.zoral.com.ua> References: <20061029140716.GA12058@comp.chem.msu.su> <20061029152227.GA11826@walton.maths.tcd.ie> <006801c6fb77$e4e30100$1200a8c0@gsicomp.on.ca> <20061030130519.GE27062@comp.chem.msu.su> <20061030134737.GF1627@deviant.kiev.zoral.com.ua> <20061118095400.GE68439@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="e8/wErwm0bqugfcz" Content-Disposition: inline In-Reply-To: <20061118095400.GE68439@comp.chem.msu.su> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=1.4 required=5.0 tests=SPF_NEUTRAL, UNPARSEABLE_RELAY autolearn=no version=3.1.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-25) on fw.zoral.com.ua Cc: David Malone , hackers@freebsd.org Subject: Re: File trees: the deeper, the weirder X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2006 11:06:11 -0000 --e8/wErwm0bqugfcz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 18, 2006 at 12:54:00PM +0300, Yar Tikhiy wrote: > On Mon, Oct 30, 2006 at 03:47:37PM +0200, Kostik Belousov wrote: > > On Mon, Oct 30, 2006 at 04:05:19PM +0300, Yar Tikhiy wrote: > > > On Sun, Oct 29, 2006 at 11:32:58AM -0500, Matt Emmerton wrote: > > > > [ Restoring some OP context.] > > > >=20 > > > > > On Sun, Oct 29, 2006 at 05:07:16PM +0300, Yar Tikhiy wrote: > > > > > > > > > > > As for the said program, it keeps its 1 Hz pace, mostly waiting= on > > > > > > "vlruwk". It's killable, after a delay. The system doesn't sh= ow ... > > > > > > > > > > > > Weird, eh? Any ideas what's going on? > > > > > > > > > > I would guess that you need a new vnode to create the new file, b= ut no > > > > > vnodes are obvious candidates for freeing because they all have a= child > > > > > directory in use. Is there some sort of vnode clearing that goes = on every > > > > > second if we are short of vnodes? > > > >=20 > > > > See sys/vfs_subr.c, subroutine getnewvnode(). We call msleep() if = we're > > > > waiting on vnodes to be created (or recycled). And just look at th= e 'hz' > > > > parameter passed to msleep()! > > > >=20 > > > > The calling process's mkdir() will end up waiting in getnewvnode() = (in > > > > "vlruwk" state) while the vnlru kernel thread does it's thing (whic= h is to > > > > recycle vnodes.) > > > >=20 > > > > Either the vnlru kernel thread has to work faster, or the caller ha= s to > > > > sleep less, in order to avoid this lock-step behaviour. > > >=20 > > > I'm afraid that, though your analysis is right, you arrive at wrong > > > conclusions. The process waits for the whole second in getnewvnode() > > > because the vnlru thread cannot free as much vnodes as it wants to. > > > vnlru_proc() will wake up sleepers on vnlruproc_sig (i.e., > > > getnewvnode()) only if (numvnodes <=3D desiredvnodes * 9 / 10). > > > Whether this condition is attainable depends on vlrureclaim() (called > > > from the vnlru thread) freeing vnodes at a sufficient rate. Perhaps > > > vlrureclaim() just can't keep the pace at this conditions. > > > debug.vnlru_nowhere increasing is an indication of that. Consequentl= y, > > > each getnewvnode() call sleeps 1 second, then grabs a vnode beyond > > > desiredvnodes. It's no surprise that the 1 second delays start to > > > appear after approx. kern.maxvnodes directories were created. > >=20 > > I think that David is right. The references _from_ the directory make i= t immune > > to vnode reclamation. Try this patch. It is very unfair for lsof. > >=20 > > Index: sys/kern/vfs_subr.c > > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > RCS file: /usr/local/arch/ncvs/src/sys/kern/vfs_subr.c,v > > retrieving revision 1.685 > > diff -u -r1.685 vfs_subr.c > > --- sys/kern/vfs_subr.c 2 Oct 2006 07:25:58 -0000 1.685 > > +++ sys/kern/vfs_subr.c 30 Oct 2006 13:44:59 -0000 > > @@ -582,7 +582,7 @@ > > * If it's been deconstructed already, it's still > > * referenced, or it exceeds the trigger, skip it. > > */ > > - if (vp->v_usecount || !LIST_EMPTY(&(vp)->v_cache_src) || > > + if (vp->v_usecount || /* !LIST_EMPTY(&(vp)->v_cache_src) || */ > > (vp->v_iflag & VI_DOOMED) !=3D 0 || (vp->v_object !=3D NULL && > > vp->v_object->resident_page_count > trigger)) { > > VI_UNLOCK(vp); > > @@ -607,7 +607,7 @@ > > * interlock, the other thread will be unable to drop the > > * vnode lock before our VOP_LOCK() call fails. > > */ > > - if (vp->v_usecount || !LIST_EMPTY(&(vp)->v_cache_src) || > > + if (vp->v_usecount || /* !LIST_EMPTY(&(vp)->v_cache_src) || */ > > (vp->v_object !=3D NULL &&=20 > > vp->v_object->resident_page_count > trigger)) { > > VOP_UNLOCK(vp, LK_INTERLOCK, td); >=20 > By the way, what do you think v_cache_src is for? The only two > places it is used in the kernel are in the unused function > cache_leaf_test() and this one, in vlrureclaim(). Is its main > purpose just to keep directory vnodes that are referenced by nc_dvp > in some namecache entries? I think that yes. Now, it mostly gives immunity for the vnodes that could be used for getcwd()/lsof path lookups through namecache. Does my change helped on you load ? cache_leaf_test() seems to be way to go. By partitioning vlru reclaim into two stages - first, which reclaim leaf vnodes (that it, vnodes that do not contain child dirs in namecache), and second, which will be fired only if first stage failed to free something and simply ignores v_cache_src, as in my change. See comment for rev. 1.56 of vfs_cache.c. --e8/wErwm0bqugfcz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFXukIC3+MBN1Mb4gRAiGjAJ0f/cjRs7VF0XTrLJzC97wQijPbMgCgw81K Ru8QuyN55t6xNp4UNYUuySY= =r88t -----END PGP SIGNATURE----- --e8/wErwm0bqugfcz-- From owner-freebsd-hackers@FreeBSD.ORG Sat Nov 18 18:14:47 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5817016A4C9 for ; Sat, 18 Nov 2006 18:14:47 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id D568F441FA for ; Sat, 18 Nov 2006 18:04:31 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.3) with ESMTP id kAII4QcM084056; Sat, 18 Nov 2006 21:04:27 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.3/Submit) id kAII4P5H084055; Sat, 18 Nov 2006 21:04:25 +0300 (MSK) (envelope-from yar) Date: Sat, 18 Nov 2006 21:04:24 +0300 From: Yar Tikhiy To: Kostik Belousov Message-ID: <20061118180424.GC80527@comp.chem.msu.su> References: <20061029140716.GA12058@comp.chem.msu.su> <20061029152227.GA11826@walton.maths.tcd.ie> <006801c6fb77$e4e30100$1200a8c0@gsicomp.on.ca> <20061030130519.GE27062@comp.chem.msu.su> <20061030134737.GF1627@deviant.kiev.zoral.com.ua> <20061118095400.GE68439@comp.chem.msu.su> <20061118110544.GN1841@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20061118110544.GN1841@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.5.9i Cc: David Malone , hackers@freebsd.org Subject: Re: File trees: the deeper, the weirder X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Nov 2006 18:14:47 -0000 On Sat, Nov 18, 2006 at 01:05:44PM +0200, Kostik Belousov wrote: > On Sat, Nov 18, 2006 at 12:54:00PM +0300, Yar Tikhiy wrote: > > On Mon, Oct 30, 2006 at 03:47:37PM +0200, Kostik Belousov wrote: > > > On Mon, Oct 30, 2006 at 04:05:19PM +0300, Yar Tikhiy wrote: > > > > On Sun, Oct 29, 2006 at 11:32:58AM -0500, Matt Emmerton wrote: > > > > > [ Restoring some OP context.] > > > > > > > > > > > On Sun, Oct 29, 2006 at 05:07:16PM +0300, Yar Tikhiy wrote: > > > > > > > > > > > > > As for the said program, it keeps its 1 Hz pace, mostly waiting on > > > > > > > "vlruwk". It's killable, after a delay. The system doesn't show ... > > > > > > > > > > > > > > Weird, eh? Any ideas what's going on? > > > > > > > > > > > > I would guess that you need a new vnode to create the new file, but no > > > > > > vnodes are obvious candidates for freeing because they all have a child > > > > > > directory in use. Is there some sort of vnode clearing that goes on every > > > > > > second if we are short of vnodes? > > > > > > > > > > See sys/vfs_subr.c, subroutine getnewvnode(). We call msleep() if we're > > > > > waiting on vnodes to be created (or recycled). And just look at the 'hz' > > > > > parameter passed to msleep()! > > > > > > > > > > The calling process's mkdir() will end up waiting in getnewvnode() (in > > > > > "vlruwk" state) while the vnlru kernel thread does it's thing (which is to > > > > > recycle vnodes.) > > > > > > > > > > Either the vnlru kernel thread has to work faster, or the caller has to > > > > > sleep less, in order to avoid this lock-step behaviour. > > > > > > > > I'm afraid that, though your analysis is right, you arrive at wrong > > > > conclusions. The process waits for the whole second in getnewvnode() > > > > because the vnlru thread cannot free as much vnodes as it wants to. > > > > vnlru_proc() will wake up sleepers on vnlruproc_sig (i.e., > > > > getnewvnode()) only if (numvnodes <= desiredvnodes * 9 / 10). > > > > Whether this condition is attainable depends on vlrureclaim() (called > > > > from the vnlru thread) freeing vnodes at a sufficient rate. Perhaps > > > > vlrureclaim() just can't keep the pace at this conditions. > > > > debug.vnlru_nowhere increasing is an indication of that. Consequently, > > > > each getnewvnode() call sleeps 1 second, then grabs a vnode beyond > > > > desiredvnodes. It's no surprise that the 1 second delays start to > > > > appear after approx. kern.maxvnodes directories were created. > > > > > > I think that David is right. The references _from_ the directory make it immune > > > to vnode reclamation. Try this patch. It is very unfair for lsof. > > > > > > Index: sys/kern/vfs_subr.c > > > =================================================================== > > > RCS file: /usr/local/arch/ncvs/src/sys/kern/vfs_subr.c,v > > > retrieving revision 1.685 > > > diff -u -r1.685 vfs_subr.c > > > --- sys/kern/vfs_subr.c 2 Oct 2006 07:25:58 -0000 1.685 > > > +++ sys/kern/vfs_subr.c 30 Oct 2006 13:44:59 -0000 > > > @@ -582,7 +582,7 @@ > > > * If it's been deconstructed already, it's still > > > * referenced, or it exceeds the trigger, skip it. > > > */ > > > - if (vp->v_usecount || !LIST_EMPTY(&(vp)->v_cache_src) || > > > + if (vp->v_usecount || /* !LIST_EMPTY(&(vp)->v_cache_src) || */ > > > (vp->v_iflag & VI_DOOMED) != 0 || (vp->v_object != NULL && > > > vp->v_object->resident_page_count > trigger)) { > > > VI_UNLOCK(vp); > > > @@ -607,7 +607,7 @@ > > > * interlock, the other thread will be unable to drop the > > > * vnode lock before our VOP_LOCK() call fails. > > > */ > > > - if (vp->v_usecount || !LIST_EMPTY(&(vp)->v_cache_src) || > > > + if (vp->v_usecount || /* !LIST_EMPTY(&(vp)->v_cache_src) || */ > > > (vp->v_object != NULL && > > > vp->v_object->resident_page_count > trigger)) { > > > VOP_UNLOCK(vp, LK_INTERLOCK, td); > > > > By the way, what do you think v_cache_src is for? The only two > > places it is used in the kernel are in the unused function > > cache_leaf_test() and this one, in vlrureclaim(). Is its main > > purpose just to keep directory vnodes that are referenced by nc_dvp > > in some namecache entries? > > I think that yes. Now, it mostly gives immunity for the vnodes that > could be used for getcwd()/lsof path lookups through namecache. Another purpose of v_cache_src that I missed is to allow for removing all namecache entries with nc_dvp pointing to a particular vnode when the vnode is recycled so that we don't end up with stale nc_dvp's in the namecache. Perhaps this is the main role v_cache_src plays. > Does my change helped on you load ? Your hack works, thanks! Your analysis of the problem proves correct. And I'm gaining some understanding of it, too :-) > cache_leaf_test() seems to be way to go. By partitioning vlru reclaim into > two stages - first, which reclaim leaf vnodes (that it, vnodes that do > not contain child dirs in namecache), and second, which will be fired only > if first stage failed to free something and simply ignores v_cache_src, as > in my change. See comment for rev. 1.56 of vfs_cache.c. Excuse me, but why "vnodes that do not contain child dirs in the namecache"? Perhaps they should be vnodes that do not contain _any_ children in the namecache? That would be better suited for trying to preserve information for vn_fullpath(). However, I must admit that I don't know how lsof works because I've never used it. -- Yar