"Symlink component flag not implemented": problem with long symlinks?

"Symlink component flag not implemented": problem with long symlinks?

Post by Peter Bouthoo » Sat, 22 May 1999 04:00:00



Hi,

ther other day I got the following kernel error messages, a couplt of times:

"Symlink component flag not implemented"

Something followed by a number. Looking through the kernel souce code I found
that this message is generated by the rockridge part of the iso9660. Which
makes sense because I was reading a CD-ROM. I suspect the error is cause by
a buffer overflow of some kind because when I tried to reproduce the error
it displayed less errors than before! Eventually the number of errors was
reduced to 1.

I got this error with: kernel 2.2.8 using while reading the Solaris 2.5.1
installation CD-ROM (Sparc version). For instance try to do an ls on:

/cdrom/MU/Solaris_2.5.1MU5/sparc/Patches/patch/SUNWpatch.sun4u1/reloc/opt/SUNWit
s/Graphics-sw/xil/lib/pipelines

And see what happens. In my case the first symlink should probably end in
"pipelines/", but it was displayed as "pipelinki". So it seems there's some
kind of buffer overflow (?).

Is this a know problem? (couldn't find anything on dejanews though).

Cheers,
Peter

--

    Peter Bouthoorn        |  "We will encourage you to develop the three

     Linux *          |   impatience, and hubris"
                           |                          L. Wall & R.L. Schwarz

 
 
 

1. problem with sysfs symlink "fix"

In the latest -bk tree sysfs's symlinks are a bit messed up:

$ tree /sys/bus/pci/
/sys/bus/pci/
|-- devices
|   |-- 00:00.0 -> ../../../
|   |-- 00:01.0 -> ../../../
|   |-- 00:1d.0 -> ../../../
|   |-- 00:1d.1 -> ../../../
|   |-- 00:1d.7 -> ../../../
|   |-- 00:1e.0 -> ../../../
|   |-- 00:1f.0 -> ../../../
|   |-- 00:1f.1 -> ../../../
|   |-- 00:1f.3 -> ../../../
|   |-- 00:1f.5 -> ../../../
|   |-- 02:03.0 -> ../../../    
|   |-- 02:04.0 -> ../../../    
|   `-- 02:05.0 -> ../../../    
`-- drivers                    
    |-- PIIX IDE                
    |   `-- 00:1f.1 -> ../../../../
    |-- aic7xxx                
    |   `-- 02:05.0 -> ../../../../
    |-- eepro100                
    |-- ehci-hcd                
    |   `-- 00:1d.7 -> ../../../../
    |-- intel810_audio          
    |   `-- 00:1f.5 -> ../../../../
    |-- ohci-hcd
    |-- parport_pc
    |-- serial
    |-- tg3
    |   `-- 02:03.0 -> ../../../../
    `-- uhci-hcd
        |-- 00:1d.0 -> ../../../../
        `-- 00:1d.1 -> ../../../../

Could your fix to fs/sysfs/symlink.c have caused this?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

2. Alpha raw performance question

3. Unix question: Elegant way to "dereference" symlink?

4. Firewalling a linux box. Are there any packages avail?

5. "bootptab" is only a symlink

6. I received Solaris 2.5 and have some questions...

7. What exactly is a "symlink race" etc?

8. fdisk fails with seagate IDE HD

9. RH6: "Failed to create symlink for package source"

10. "File exists writing symlinking article file -- throttling"

11. "make mrproper" breaks symlinks?

12. Meaning of ".." in symlinked directory

13. RH 6.0 Hard Drive install "symlink" error message