Re: CVS_LOCAL_BRANCH_NUM?
On Tue, Dec 10, 2002 at 11:56:26AM -0800, Lamont Granquist wrote: On Tue, 10 Dec 2002, Dmitry Morozovsky wrote: On Tue, 10 Dec 2002, Lamont Granquist wrote: LG From the man page, I'm not really sure where it makes a difference other LG than when someone is playing with IFS, but $@ seems to be more of what I LG intended... Please note quotes explicitly, $@ is really needed where your parameters contain spaces (bad practice in filenames, yeah, but don't make yourself another one PITA you can avoid ;-P ) got it. Mmm.. I am not really sure if we need quotes in this particular case. In my experience, the CVS invocation in the server or pserver case almost always has more than one argument (at the very least, the 'server' or 'pserver' keyword and one 'allow-root' option). The quotes around $@ would make the whole param string be passed as a single parameter to the real CVS binary, which might not be quite the desired result... G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 This sentence claims to be an Epimenides paradox, but it is lying. msg38615/pgp0.pgp Description: PGP signature
Re: CVS_LOCAL_BRANCH_NUM?
On Wed, Dec 11, 2002 at 10:59:55AM +0200, Peter Pentchev wrote: On Tue, Dec 10, 2002 at 11:56:26AM -0800, Lamont Granquist wrote: On Tue, 10 Dec 2002, Dmitry Morozovsky wrote: Please note quotes explicitly, $@ is really needed where your parameters contain spaces (bad practice in filenames, yeah, but don't make yourself another one PITA you can avoid ;-P ) got it. Mmm.. I am not really sure if we need quotes in this particular case. In my experience, the CVS invocation in the server or pserver case almost always has more than one argument (at the very least, the 'server' or 'pserver' keyword and one 'allow-root' option). The quotes around $@ would make the whole param string be passed as a single parameter to the real CVS binary, which might not be quite the desired result... No, that's not the behaviour with /bin/sh, from the man page: @ Expands to the positional parameters, starting from one. When the expansion occurs within double-quotes, each positional param- eter expands as a separate argument. If there are no positional parameters, the expansion of @ generates zero arguments, even when @ is double-quoted. What this basically means, for example, is if $1 is ``abc'' and $2 is ``def ghi'', then $@ expands to the two arguments: abc def ghi I think $@ (with the quotes) is ok. --Stijn -- Help Wanted: Telepath. You know where to apply. msg38616/pgp0.pgp Description: PGP signature
Re: CVS_LOCAL_BRANCH_NUM?
On Wed, Dec 11, 2002 at 10:40:04AM +0100, Stijn Hoop wrote: On Wed, Dec 11, 2002 at 10:59:55AM +0200, Peter Pentchev wrote: On Tue, Dec 10, 2002 at 11:56:26AM -0800, Lamont Granquist wrote: On Tue, 10 Dec 2002, Dmitry Morozovsky wrote: Please note quotes explicitly, $@ is really needed where your parameters contain spaces (bad practice in filenames, yeah, but don't make yourself another one PITA you can avoid ;-P ) got it. Mmm.. I am not really sure if we need quotes in this particular case. In my experience, the CVS invocation in the server or pserver case almost always has more than one argument (at the very least, the 'server' or 'pserver' keyword and one 'allow-root' option). The quotes around $@ would make the whole param string be passed as a single parameter to the real CVS binary, which might not be quite the desired result... No, that's not the behaviour with /bin/sh, from the man page: @ Expands to the positional parameters, starting from one. When the expansion occurs within double-quotes, each positional param- eter expands as a separate argument. If there are no positional parameters, the expansion of @ generates zero arguments, even when @ is double-quoted. What this basically means, for example, is if $1 is ``abc'' and $2 is ``def ghi'', then $@ expands to the two arguments: abc def ghi I think $@ (with the quotes) is ok. Oops. Thanks for the clarification. Never had to deal with $@ before, actually. /me crawls back into his hole. G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 No language can express every thought unambiguously, least of all this one. msg38617/pgp0.pgp Description: PGP signature
soft updates
Hello all... In this moment, i have one linux server to provides me NFS sharing... Why? Because i need xfs instant recovery feature, and the performance. I don't know very well about soft updates, and i would like have only BSD systems... Somebody knows if i could and how to install FreeBSD with xfs? or how can i create a ufs filesystem with soft updates for big volumes (+300GB) and NFS services? Thanks! [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
kernel/userland ssh filesystem for FreeBSD?
Hi, as you might know, both kde (via kio-fish) and gnome (via gnome virtual file system) provide a userland filesystem-like API that allows to mount a remote filesystem using ssh. What I don't like about those solutions is that they require the application to use a particular API (kio slave or gnome vfs). Another approach, that provides a real filesystem interface, is the Linux Userspace File System. Quoting from http://lufs.sourceforge.net/lufs/intro.html: LUFS is a hybrid userspace filesystem framework supporting an indefinite number of filesystems transparently for any application. It consists of a kernel module and an userspace daemon. Basically it delegates most of the VFS calls to a specialized daemon which handles them. Now the question: if I wanted to do something similar for FreeBSD, how would I do it? Any high-level hints? thanks Marco To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: kernel/userland ssh filesystem for FreeBSD?
On Wed, Dec 11, 2002 at 10:04:06AM +0100, Marco Molteni wrote: Hi, as you might know, both kde (via kio-fish) and gnome (via gnome virtual file system) provide a userland filesystem-like API that allows to mount a remote filesystem using ssh. What I don't like about those solutions is that they require the application to use a particular API (kio slave or gnome vfs). Another approach, that provides a real filesystem interface, is the Linux Userspace File System. Quoting from http://lufs.sourceforge.net/lufs/intro.html: LUFS is a hybrid userspace filesystem framework supporting an indefinite number of filesystems transparently for any application. It consists of a kernel module and an userspace daemon. Basically it delegates most of the VFS calls to a specialized daemon which handles them. Now the question: if I wanted to do something similar for FreeBSD, how would I do it? Any high-level hints? Take a look at mount_portal(8). G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 When you are not looking at it, this sentence is in Spanish. msg38620/pgp0.pgp Description: PGP signature
Re: kernel/userland ssh filesystem for FreeBSD?
On Wed, Dec 11, 2002 at 02:34:44PM +0200, Peter Pentchev wrote: On Wed, Dec 11, 2002 at 10:04:06AM +0100, Marco Molteni wrote: [snip] Quoting from http://lufs.sourceforge.net/lufs/intro.html: LUFS is a hybrid userspace filesystem framework supporting an indefinite number of filesystems transparently for any application. It consists of a kernel module and an userspace daemon. Basically it delegates most of the VFS calls to a specialized daemon which handles them. Now the question: if I wanted to do something similar for FreeBSD, how would I do it? Any high-level hints? Take a look at mount_portal(8). Which reminds me.. I really should dig up and polish my mount_portal 'exec' fstype patches.. but this is a fight for another day :( G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 No language can express every thought unambiguously, least of all this one. msg38621/pgp0.pgp Description: PGP signature
How can I post a pr when my IP can't be reverse-resolved?
Hi, I'm working in a small educational website(Simplified Chinese), Frontfree Technology Network ( www.frontfree.net ). Because the IP address is rent by my University from an ISP, and for unknown reasons we can't have the permission to reverse-resolve our IP address, it seemed impossible to send mail to FreeBSD.org, except for the maillist subscribing and unsubscribing. On the other hand, I usually want to submit some patch along with PRs to FreeBSD-gnats-submit@. I knew that I can paste the information to some other mail providers like Microsoft Hotmail, but it's a bit bother. Is it possible to change the policy of gnats@ in order to get mails from IPs which couldn't reverse-resolve, or I'll have to use Hotmail again and again? Thanks! Xin Li, Frontfree Technology Network, Beijing University of Technology _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Crash with 5.0-RC1
Greetings, I understand that this is the place to send debugging dumps from kernel crashes. If I'm misinformed, please advise. The original problem is described here and other thread contributor indicates a similar problem on similar hardware: http://marc.theaimsgroup.com/?l=freebsd-currentm=103954227212045w=2 There is another person with an acpi crash problem here: http://marc.theaimsgroup.com/?l=freebsd-currentm=103955920101157w=2 The gdb output from where is below. Please let me know what I can do to help. The configuration ran without a hitch under DP2. /Paul -bash-2.05b$ gdb -k kernel.debug.0 vmcore.1 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 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-undermydesk-freebsd... panic: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x42 fault code = supervisor read, page not present instruction pointer = 0x8:0xc042c517 stack pointer = 0x10:0xdf0caa04 frame pointer = 0x10:0xdf0caa1c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 6 (acpi_task1) panic: from debugger Fatal trap 3: breakpoint instruction fault while in kernel mode instruction pointer = 0x8:0xc045c4f4 stack pointer = 0x10:0xdf0ca784 frame pointer = 0x10:0xdf0ca790 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= IOPL = 0 current process = 6 (acpi_task1) panic: from debugger Uptime: 31s Dumping 1023 MB ata0: resetting devices .. done 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976 992 1008Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-RC1 #0: Sat Dec 7 22:16:29 GMT 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel /boot/kernel/kernel at 0xc06b5000. Preloaded elf module /boot/kernel/acpi.ko at 0xc06b50a8. Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 1200049432 Hz CPU: Pentium 4 (1200.05-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebf9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,b31 real memory = 1073713152 (1023 MB) avail memory = 1036169216 (988 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: math processor on motherboard npx0: INT 16 interface acpi0: ASUS P4_L3CS on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0625: *** Info: GPE Block1 defined as GPE16 to GPE31 Using $PIR table, 6 entries at 0xc00f13b0 acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-fast frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_tz0: thermal zone on acpi0 acpi_button0: Sleep Button on acpi0 acpi_acad0: AC adapter on acpi0 acpi_cmbat0: Control method Battery on acpi0 acpi_lid0: Control Method Lid Switch on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82845 host to AGP bridge mem 0xe000-0xefff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) uhci0: Intel 82801CA/CAM (ICH3) USB controller USB-A port 0xb800-0xb81f irq 5 at device 29.0 on pci0 usb0: Intel 82801CA/CAM (ICH3) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801CA/CAM (ICH3) USB controller USB-B port 0xb400-0xb41f irq 9 at device 29.1 on pci0 usb1: Intel 82801CA/CAM (ICH3) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pcib2: ACPI PCI-PCI bridge at device 30.0 on pci0 pci2: ACPI PCI bus on pcib2 rl0: RealTek 8139 10/100BaseTX port 0xa800-0xa8ff mem 0xd680-0xd68000ff irq 9 at device 5.0 on pci2 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:e0:18:bc:f6:85
Re: soft updates
--- omestre [EMAIL PROTECTED] wrote: Hello all... In this moment, i have one linux server to provides me NFS sharing... Why? Because i need xfs instant recovery feature, and the performance. I don't know very well about soft updates, and i would like have only BSD systems... Somebody knows if i could and how to install FreeBSD with xfs? or how can i create a ufs filesystem with soft updates for big volumes (+300GB) and NFS services? Thanks! [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message XFS (also ReiserFS and ext3fs) are GPL code (in Linux), so there won't be any direct port of these (the same is true of ext2fs though, but it was probably reimplemented under a BSD license). You would have to port them over yourself to build FreeBSD with them. Ext3fs is probably a good possibility for a journaling file system for FreeBSD, since it supposedly reuses a lot of the organization of ext2fs with some features added on (I don't know how well these journaling file systems perform compared to each other and nthings like ffs and I have seen conflicting results/claims). It should be easier to implement ext3fs in FreeBSD since ext2fs is already in FreeBSD. The only logging/journaling file system available for *BSD that I am aware of is LFS, which I don't think is either stable or fast. I don't know how big a filesystem FFS+softdeps will support, but soft updates is not completly stable although I think it can be used with reasonable assurance it won't explode (I have). FFS on FreeBSD can support +300GB file systems I think, but whether soft updates will work correctly (or at least as correctly as it does in smaller file systems) at these sizes is unknown to me. __ Post your free ad now! http://personals.yahoo.ca To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
New version of unifdef(1)
Following a bug spotted by Ian Dowse, I have hacked a bit more on unifdef(). This version has a much more ANSI-like lexical parser which should fix the zero byte in input problem as well as the handling of files that don't end with a newline. The bogus string parsing has been killed. The other main change is that the broken hand-coded #if processing state machine has been replaced with a table-driven one. I think I have all the state transitions right, but if people could bang on it a bit that would be good. The new code can be obtained from http://dotat.at/prog/misc/unifdef.c Tony. -- f.a.n.finch [EMAIL PROTECTED] http://dotat.at/ MULL OF KINTYRE TO ARDNAMURCHAN POINT: EAST TO SOUTHEAST 5 LOCALLY 6. FAIR. GOOD. SLIGHT TO MODERATE. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: soft updates
Gary Thorpe wrote: The only logging/journaling file system available for *BSD that I am aware of is LFS, which I don't think is either stable or fast. I don't know how big a filesystem FFS+softdeps will support, but soft updates is not completly stable although I think it can be used with reasonable assurance it won't explode (I have). FFS on FreeBSD can support +300GB file systems I think, but whether soft updates will work correctly (or at least as correctly as it does in smaller file systems) at these sizes is unknown to me. I've been using softupdates on a 361GB filesystem for some time now. Although some hardware failures gave vinum fits, softupdates has never caused me a problem: /dev/vinum/media361G 288G45G87%/media -- \ |_ _|__ __|_ \ __| Jason Andresen[EMAIL PROTECTED] |\/ | ||/ _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Some problems about KSE
On Wed, 11 Dec 2002, ouyang kai wrote: Hi, everybody, I want to make sure whether we can program the multi-thread code based on KSE in FreeBSD5.0 RC-1. Well it's still being written so you may be a bit ahead of yourself.. I have make in '/usr/src/lib/libpthread', I found some new things in '/usr/lib' as follow: lrwxr-xr-x 1 root wheel 11 Dec 11 16:04 libkse.so - libkse.so.1 -r--r--r-- 1 root wheel68780 Dec 11 16:04 libkse.so.1 -r--r--r-- 1 root wheel 164448 Dec 11 16:04 libkse_p.a -r--r--r-- 1 root wheel 153854 Dec 11 16:04 libkse.a So if I program. How can I use the kse? cc ... -lkse I can use pthread(3) as traditional manner, only using '-lpthread' instead of '-pthread' in my makefile, right? no use -lkse until we have if more finished... then it will become -lpthread when I use /usr/src/tools/KSE/ksetest/ksetest program , it always cause my box crash. I have report this issue to Julian. the fix was committed yesterday. I am seeing KSE(2), I have some puzzles about that. 1. upcall is really means what? Does it represent through 'km_func'? if it were true, the 'km_func' is indicated by whom? UTS, Kernel, or user program, I do not know. the UTS fills in km_func before creating the KSE and loaded by the kernel. At THIS time it is never looked at again, but that could change in the future. (see how ksetest is written) 2. When one process has more than one KSEG, the signal should be delivered to which KSEG? The manual said it is indeterminate. I do not know how the signal could be delivered to the special KSEG exactly? It is indetirminate because that code has not been written. At this time the signal will be delivered in the normal way to the next thread to enter the kernel in any way. This actually works for a surprising number of programs as long as they do not need to do any thread_specific actions in the handler. How to route the signals to a specific thread is still under discussion. Thank you! Best Regards Ouyang Kai _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: panic: icmp_error: bad length
In message [EMAIL PROTECTED] , Patrick Soltani writes: In the last couple of months, upgraded to 4.6 and 4.7 using RELENG_4 = with again no errors, however, now under a light smurf attack, I get: panic: icmp_error: bad length Hardware: Dell PowerEdge 350, 2 built-in Intel nic cards, 256 meg of ram = and only doing ipfw.=20 The kernel is built with options BRIDGE. Don't know what other info you = might be interested. Deeply appreciate any help or info.=20 Could you try to get a stack trace from the panic? There are instructions on how to set this up in the Kernel Debugging chapter of the Developers Handbook at: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html Even just a list of the function names from DDB would be a good start, but if possible try to compile a debug kernel, get a full crash dump and provide the gdb stack trace. Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: panic: icmp_error: bad length
In message [EMAIL PROTECTED], Alexander Langer
writes:
Yeah, same situation here. 4.6 used to work w/o problem, 4.7 doesn't.
Great, thanks for the debugging info. The bug seems to be that
icmp_error() requires that the IP header fields are in host order,
but when it is called on a briged packet by the IPFW code, this is
not the case. Something like the patch below (untested) should fix
the IPFW1 case. A similar change is needed for IPFW2.
Luigi: does this look reasonable? I'm not familiour enough with the
IPFW code to know if it is OK to modify the mbuf like this. If not
then it needs to be copied first like ip_forward() does, making
sure that the IP header does not end up in a shared cluster.
Ian
Index: ip_fw.c
===
RCS file: /home/iedowse/CVS/src/sys/netinet/ip_fw.c,v
retrieving revision 1.131.2.38
diff -u -r1.131.2.38 ip_fw.c
--- ip_fw.c 21 Nov 2002 01:27:30 - 1.131.2.38
+++ ip_fw.c 12 Dec 2002 00:43:22 -
@@ -1573,6 +1573,11 @@
break;
}
default:/* Send an ICMP unreachable using code */
+ /* Must convert to host order for icmp_error(). */
+ if (BRIDGED) {
+ NTOHS(ip-ip_len);
+ NTOHS(ip-ip_off);
+ }
icmp_error(*m, ICMP_UNREACH,
f-fw_reject_code, 0L, 0);
*m = NULL;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: panic: icmp_error: bad length
the diagnosis looks reasonable, though i do not remember changing
anything related to this between 4.6 and 4.7 so i wonder why the
error did not appear in earlier versions of the code.
icmp_error() consumes the mbuf so i believe it is ok to scramble it
but one should double check.
Note that NTOHS() seem to be deprecated in favour of the function version
of the same
cheers
luigi
On Thu, Dec 12, 2002 at 12:54:48AM +, Ian Dowse wrote:
In message [EMAIL PROTECTED], Alexander Langer
writes:
Yeah, same situation here. 4.6 used to work w/o problem, 4.7 doesn't.
Great, thanks for the debugging info. The bug seems to be that
icmp_error() requires that the IP header fields are in host order,
but when it is called on a briged packet by the IPFW code, this is
not the case. Something like the patch below (untested) should fix
the IPFW1 case. A similar change is needed for IPFW2.
Luigi: does this look reasonable? I'm not familiour enough with the
IPFW code to know if it is OK to modify the mbuf like this. If not
then it needs to be copied first like ip_forward() does, making
sure that the IP header does not end up in a shared cluster.
Ian
Index: ip_fw.c
===
RCS file: /home/iedowse/CVS/src/sys/netinet/ip_fw.c,v
retrieving revision 1.131.2.38
diff -u -r1.131.2.38 ip_fw.c
--- ip_fw.c 21 Nov 2002 01:27:30 - 1.131.2.38
+++ ip_fw.c 12 Dec 2002 00:43:22 -
@@ -1573,6 +1573,11 @@
break;
}
default:/* Send an ICMP unreachable using code */
+ /* Must convert to host order for icmp_error(). */
+ if (BRIDGED) {
+ NTOHS(ip-ip_len);
+ NTOHS(ip-ip_off);
+ }
icmp_error(*m, ICMP_UNREACH,
f-fw_reject_code, 0L, 0);
*m = NULL;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: panic: icmp_error: bad length
In message [EMAIL PROTECTED], Luigi Rizzo writes:
the diagnosis looks reasonable, though i do not remember changing
anything related to this between 4.6 and 4.7 so i wonder why the
error did not appear in earlier versions of the code.
Yes strange - actually, it looks like the THERE IS NO FUNCTIONAL
OR EXTERNAL API CHANGE IN THIS COMMIT commit may be to blame :-)
Some fragments below.
Ian
bridge.c 1.16.2.2:
+#ifdef PFIL_HOOKS
...
-* before calling the firewall, swap fields the same as IP does.
-* here we assume the pkt is an IP one and the header is contiguous
...
- ip = mtod(m0, struct ip *);
- NTOHS(ip-ip_len);
- NTOHS(ip-ip_off);
ip_fw.c 1.131.2.34:
- if (0 BRIDGED) { /* not yet... */
- offset = (ntohs(ip-ip_off) IP_OFFMASK);
+ if (BRIDGED) { /* bridged packets are as on the wire */
+ ip_off = ntohs(ip-ip_off);
ip_len = ntohs(ip-ip_len);
} else {
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
RE: panic: icmp_error: bad length
Hi again, the diagnosis looks reasonable, though i do not remember changing anything related to this between 4.6 and 4.7 so i wonder why the error did not appear in earlier versions of the code. This is happening on 4.6-STABLE and -RELEASE as well as 4.7 all flavors. Many thanx for identifying the problem and hopefully a patch to fix it; keeping my fingers crossed :-). Best Regards, Patrick Soltani. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: panic: icmp_error: bad length
On Thu, 12 Dec 2002, Ian Dowse wrote:
--- ip_fw.c 21 Nov 2002 01:27:30 - 1.131.2.38
+++ ip_fw.c 12 Dec 2002 00:43:22 -
@@ -1573,6 +1573,11 @@
break;
}
default:/* Send an ICMP unreachable using code */
+ /* Must convert to host order for icmp_error(). */
+ if (BRIDGED) {
+ NTOHS(ip-ip_len);
+ NTOHS(ip-ip_off);
+ }
icmp_error(*m, ICMP_UNREACH,
f-fw_reject_code, 0L, 0);
*m = NULL;
Since the REJECT case needs several headers in host order, why not put
this there (line 1546), taking care of potential problems in the tcp RST
case?
-Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Sound Card Problems
Hi, I'm having some trouble with my sound card. I have a Hercules Muse XL. I compiled my kernel with device pcm and did the MAKEDEV snd0. My sound is only coming out of the front channel (the card has rear and center channel as well). Also, my dmesg has the following: config di sn0 No such device: sn0 Invalid command or syntax. Type `?' for help. config di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config q Anyone have any ideas on how I might get around these problems? (I'm assuming they are related to each other). Thanks Corey Mosher To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: RE: registers not saved
: function A calls function B which uses ecx as a loop index. The bad part is :function B never : saves/restores the value of ecx and function A starts dereferencing garbage. : : An informal sampling of my driver seems to indicate that ebx gets : pushed/poped at entry/exit but ecx and edx don't. Does any of this : sound familiar? Thanks! : :Yes, eax, ebx, and edx are not call-safe registers. If you are writing :your own function in assembly and you call a function you need to either :save those registers yourself or reload their values. If you are writing :... :John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ :Power Users Use the Power to Serve! - http://www.FreeBSD.org/ I think you meant ecx there. eax, ecx, and edx are not call safe. ebx is. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Sound Card Problems
On Thu, 2002-12-12 at 13:11, Corey Mosher wrote: Hi, I'm having some trouble with my sound card. I have a Hercules Muse XL. I compiled my kernel with device pcm and did the MAKEDEV snd0. My sound is only coming out of the front channel (the card has rear and center channel as The driver probably doesn't properly support the other channels.. Patches would be accepted I bet :) well). Also, my dmesg has the following: config di sn0 No such device: sn0 Invalid command or syntax. Type `?' for help. config di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config q Anyone have any ideas on how I might get around these problems? (I'm assuming they are related to each other). They don't have anything to do with each other. The stuff above is from /boot/kernel.conf disabling the devices that where disabled using 'boot -c', and can safely be ignored. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: panic: icmp_error: bad length
BTW, if this bug exists in 5.0 for the same reasons (or even different
ones), we should try to generate a fix ASAP and get it committed.
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED] Network Associates Laboratories
On Thu, 12 Dec 2002, Ian Dowse wrote:
In message [EMAIL PROTECTED], Luigi Rizzo writes:
the diagnosis looks reasonable, though i do not remember changing
anything related to this between 4.6 and 4.7 so i wonder why the
error did not appear in earlier versions of the code.
Yes strange - actually, it looks like the THERE IS NO FUNCTIONAL
OR EXTERNAL API CHANGE IN THIS COMMIT commit may be to blame :-)
Some fragments below.
Ian
bridge.c 1.16.2.2:
+#ifdef PFIL_HOOKS
...
-* before calling the firewall, swap fields the same as IP does.
-* here we assume the pkt is an IP one and the header is contiguous
...
- ip = mtod(m0, struct ip *);
- NTOHS(ip-ip_len);
- NTOHS(ip-ip_off);
ip_fw.c 1.131.2.34:
- if (0 BRIDGED) { /* not yet... */
- offset = (ntohs(ip-ip_off) IP_OFFMASK);
+ if (BRIDGED) { /* bridged packets are as on the wire */
+ ip_off = ntohs(ip-ip_off);
ip_len = ntohs(ip-ip_len);
} else {
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: kernel/userland ssh filesystem for FreeBSD?
On Wed, 11 Dec 2002, Marco Molteni wrote: as you might know, both kde (via kio-fish) and gnome (via gnome virtual file system) provide a userland filesystem-like API that allows to mount a remote filesystem using ssh. What I don't like about those solutions is that they require the application to use a particular API (kio slave or gnome vfs). Another approach, that provides a real filesystem interface, is the Linux Userspace File System. Quoting from http://lufs.sourceforge.net/lufs/intro.html: LUFS is a hybrid userspace filesystem framework supporting an indefinite number of filesystems transparently for any application. It consists of a kernel module and an userspace daemon. Basically it delegates most of the VFS calls to a specialized daemon which handles them. Now the question: if I wanted to do something similar for FreeBSD, how would I do it? Any high-level hints? FreeBSD actually includes a module for this very purpose to support the Coda file system, which uses a userspace cache manager to interact with directory services, manage the on-disk local cache, etc. I actually slightly prefer the Arla XFS kernel module, which behaves in an almost identical manner. Both create /dev nodes and communicate their needs via what are effectively RPC upcalls. They both follow the model that a daemon exists in userspace to support a file system mount, and will update the kernel with namespace information, as well as providing referenced to cache files locally. Usually the userland daemon is threaded, and matches worker threads with kernel threads/processes currently blocked in file system activity. I know there was discussion of getting the XFS module to support more than one mountpoint at a time, but I'm not sure if that happened or not. The Arla code is separately distributed from FreeBSD, but there's a port I believe. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Some problems about KSE
A commit was made to correct the KSE crash shortly after 5.0-RC1. You can cvsup forward to a newer revision, or wait for RC2. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories On Wed, 11 Dec 2002, ouyang kai wrote: Hi, everybody, I want to make sure whether we can program the multi-thread code based on KSE in FreeBSD5.0 RC-1. I have make in '/usr/src/lib/libpthread', I found some new things in '/usr/lib' as follow: lrwxr-xr-x 1 root wheel 11 Dec 11 16:04 libkse.so - libkse.so.1 -r--r--r-- 1 root wheel68780 Dec 11 16:04 libkse.so.1 -r--r--r-- 1 root wheel 164448 Dec 11 16:04 libkse_p.a -r--r--r-- 1 root wheel 153854 Dec 11 16:04 libkse.a So if I program. How can I use the kse? I can use pthread(3) as traditional manner, only using '-lpthread' instead of '-pthread' in my makefile, right? when I use /usr/src/tools/KSE/ksetest/ksetest program , it always cause my box crash. I have report this issue to Julian. I am seeing KSE(2), I have some puzzles about that. 1. upcall is really means what? Does it represent through 'km_func'? if it were true, the 'km_func' is indicated by whom? UTS, Kernel, or user program, I do not know. 2. When one process has more than one KSEG, the signal should be delivered to which KSEG? The manual said it is indeterminate. I do not know how the signal could be delivered to the special KSEG exactly? Thank you! Best Regards Ouyang Kai _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
