All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@redhat.com>, Warren Togami <wtogami@redhat.com>,
	Al Viro <viro@redhat.com>
Subject: [PATCH 2.6] i2o_proc converting from proc_read to seq_file with problems and request for help
Date: Wed, 12 May 2004 13:37:26 +0200	[thread overview]
Message-ID: <40A20C76.40204@shadowconnect.com> (raw)

Hello,

first, i didn't attach the patch because the size is 120k and it doesn't 
work at the moment. If you want it by e-mail, please let me know. 
Meanwhile you could download the patch from:

http://i2o.shadowconnect.com/testing/i2o_proc-seq_file.patch

The patch converts the proc_read function to the seq_file function 
(thanks to Al Viro for helping).

Only some functions are working without any problem (e. g. i2o_*_lct). 
But some others get a Segmentation fault (e. g. i2o_*_claimed). Strange 
about it is that the Segmentation fault occur after the function returns 
and the output is displayed normally.

If you want the output of the kernel for 32-bit UP and 64-bit SMP 
system, look at http://i2o.shadowconnect.com/testing/.

Any help what i done wrong would be appreciated.

Thank you very much.


Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)

Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany

Phone:  +49 82 82/99 51-0
Fax:    +49 82 82/99 51-11

E-Mail: Markus.Lidel@shadowconnect.com
URL:    http://www.shadowconnect.com


                 reply	other threads:[~2004-05-12 11:32 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=40A20C76.40204@shadowconnect.com \
    --to=markus.lidel@shadowconnect.com \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@redhat.com \
    --cc=wtogami@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.