All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikita Danilov <Nikita@Namesys.COM>
To: Jonathan Briggs <jbriggs@esoft.com>
Cc: Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: Reiser4 oops on cat ./..plugin/..readdir
Date: Fri, 27 Feb 2004 20:14:03 +0300	[thread overview]
Message-ID: <16447.31451.279097.181894@laputa.namesys.com> (raw)
In-Reply-To: <1077901194.6423.2.camel@localhost.localdomain>

Jonathan Briggs writes:
 > On Fri, 2004-02-27 at 04:29, Nikita Danilov wrote:
 > > Jonathan Briggs writes:
 > >  > Filesystem is on a RAID 0 MD device.
 > >  > Config is attached.
 > >  > Kernel compiled with:
 > >  > 
 > >  > # gcc34 --version
 > >  > gcc34 (GCC) 3.4.0 20040129 (Red Hat Linux 3.4.0-0.3)
 > >  > Copyright (C) 2004 Free Software Foundation, Inc.
 > >  > This is free software; see the source for copying conditions.  There is NO
 > >  > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
 > >  > 
 > >  > Problem Description:
 > >  > A clean, fresh boot into single user mode, no tainted modules:
 > >  > # cd /home
 > >  > # cat ./..plugin/..readdir
 > > 
 > > Please try the following patch:
 > > ----------------------------------------------------------------------
 > > ===== plugin/pseudo/pseudo.c 1.41 vs edited =====
 > > --- 1.41/plugin/pseudo/pseudo.c	Tue Jan 27 18:40:13 2004
 > > +++ edited/plugin/pseudo/pseudo.c	Fri Feb 27 14:27:54 2004
 > > @@ -533,7 +533,7 @@
 > >  	dotname.len  = 1;
 > >  
 > >  	down(&host->i_sem);
 > > -	if (dplug == NULL) {
 > > +	if (dplug == NULL || dplug->build_entry_key == NULL) {
 > >  		finish(NULL);
 > >  		return NULL;
 > >  	}
 > > ----------------------------------------------------------------------
 > 
 > Yes, this fixed the Oops.  Thanks.
 > 
 > That gives me another question.  Why do I not see any plugins listed
 > when I do either ls ./..plugin/ or cat ./..plugin/..readdir?

/data1/tests> cat ./..pseudo # list of pseudo file accessible under "."
..uid
..gid
..rwx
..oid
..key
..size
..nlink
..locality
..pagecache
..pseudo
..bmap
..readdir
..plugin
..items
..new
/data1/tests> cd ./..plugin # pseudo directory representing plugins of "."
/mnt/b1/tests/..plugin> ls
compression  crypto  digest  dir  dir_item  file  formatting  hash  perm  sd

 > 
 > Shouldn't there be at least a few default plugins?  I seem to remember
 > seeing some when I was using a previous snapshot in January.

See http://namesys.com/v4/pseudo.html for details.

 > -- 
 > Jonathan Briggs
 > jbriggs@esoft.com

Nikita.

  reply	other threads:[~2004-02-27 17:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27  1:34 Reiser4 oops on cat ./..plugin/..readdir Jonathan Briggs
2004-02-27 11:29 ` Nikita Danilov
2004-02-27 16:59   ` Jonathan Briggs
2004-02-27 17:14     ` Nikita Danilov [this message]
2004-02-27 17:20       ` Jonathan Briggs
2004-02-27 17:33         ` Nikita Danilov

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=16447.31451.279097.181894@laputa.namesys.com \
    --to=nikita@namesys.com \
    --cc=Reiserfs-List@Namesys.COM \
    --cc=jbriggs@esoft.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.