The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Michael König" <Michael.Koenig@ipcas.de>
To: linux-kernel@vger.kernel.org
Subject: CRAMFS: Possible problem with named pipes
Date: Wed, 13 Jun 2007 09:30:22 +0200	[thread overview]
Message-ID: <132FF90BD68D10CCD22AE5F7@franken3> (raw)

Hello there,

I'm using Linux on a device with an ETRAX100LX utilizing SDK 2.10 fom Axis, 
which includes Linux 2.6.19.
I tried to use the latest CRAMFS code from the GIT repository, but I get 
the following error:
fs/cramfs/inode.c: In function `cramfs_readdir':
fs/cramfs/inode.c:342: structure has no member named `f_path'

I hope the behaviour is also reproducable with the latest code. 
Unfortunately I'm not sure which revision the code in the Axis distribution 
has, since there is no information in the source files.

To reproduce the problem follow these steps:
1. Create two named pipes on a CRAMFS image (in my case "fifo1" and 
"fifo2").
2. Output the pipes on separate terminals with "cat fifo1" and "cat fifo2".
3. Pipe a large text file (around 1MiB) into one of the pipes "cat 
large.txt > fifo1"

The result of these steps should be that some parts of the text file are 
piped to fifo1 while other parts are piped to fifo2.

I'm no kernel nor file system expert, but since pipes should be handled in 
the VFS but the inodes are provided by the file system (as far as I 
understand), this could be an inode mixup regarding named pipes in the 
CRAMFS.

Thanks in advance for any hints that might clear up this issue.

-- 
Mit freundlichen Grüßen
Best regards
Michael König

ipcas GmbH
Wetterkreuz 17
91058 Erlangen, Germany
Tel.: +49 9131 7677-31
Fax: +49 9131 7677-78
mailto:Michael.Koenig@ipcas.de

Geschäftsführer: Dipl.-Ing. S. Sutiono
Sitz der Gesellschaft: Erlangen
Registergericht: Fürth, HBR 3676
WEEE-Reg.-Nr. DE 77202473

Hinweis: Diese E-Mail und etwaige Anlagen können Betriebs- oder
Geschäftsgeheimnisse, dem Anwaltsgeheimnis unterliegen oder sonstige
vertrauliche Informationen enthalten. Sollten Sie diese E-Mail
irrtümlich erhalten haben, ist Ihnen der Status dieser E-Mail bekannt.
Bitte benachrichtigen Sie uns in diesem Fall sofort durch Antwort-Mail
und löschen Sie diese E-Mail nebst etwaigen Anlagen von Ihrem System.
Ebenso dürfen Sie diese E-Mail oder seine Anlagen
nicht kopieren oder an Dritte weitergeben. Vielen Dank.


                 reply	other threads:[~2007-06-13  7:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=132FF90BD68D10CCD22AE5F7@franken3 \
    --to=michael.koenig@ipcas.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox