public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Panin <pazke@orbita1.ru>
To: yf <fyou@dsguardian.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pls help me
Date: Thu, 24 Oct 2002 16:39:40 +0400	[thread overview]
Message-ID: <20021024123940.GA304@pazke.ipt> (raw)
In-Reply-To: <1035441048.727.3.camel@yf.dsguardian.com>

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

On Чтв, Окт 24, 2002 at 02:30:45 +0800, yf wrote:
> Hi, all, 
> 
> Recently I wrote a file-system under Linux. When mounting, it prints 
> these messages. I use iget(sb, ino) to get the root inode. 
> 
> But when run into get_new_inode():wake_up(), it hangs there. Who could 
> give me some hints? 
> 
> what the dmesg output: 
> ************************************************************************
> 
> ==> vvfs_init() 
> ==> vvfs_read_super(<NULL>) 
> ==> vvfs_connect(192.168.1.57, 52886) 
> 2, 38606, 956410048 
> <== vvfs_connect()OK 
> superblock ordinary filling ok 
> ==> vvfs_alloc_inode() 
> <== vvfs_alloc_inode() 
> ==> vvfs_read_inode(c67fb000) 
> get sb sock 
> get inode fid 
> root inode 
> fetch inode OK 
> set server info OK 
> <== vvfs_read_inode()c67fb000 
> Unable to handle kernel paging request at virtual address fffffffc 

Address fffffffc looks like negative error code assigned to a pointer.

-- 
Andrey Panin            | Embedded systems software developer
pazke@orbita1.ru        | PGP key: wwwkeys.eu.pgp.net

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2002-10-24 12:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-24  6:30 pls help me yf
2002-10-24 12:13 ` Richard B. Johnson
2002-10-24 12:39 ` Andrey Panin [this message]
2002-10-24 15:31   ` Georg Nikodym
  -- strict thread matches above, loose matches on Subject: below --
2005-08-25 14:07 PLS HELP ME Ms ROSE

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=20021024123940.GA304@pazke.ipt \
    --to=pazke@orbita1.ru \
    --cc=fyou@dsguardian.com \
    --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