From: Peter van Hardenberg <pvh@uvic.ca>
To: reiserfs-list@namesys.com
Subject: Re: Reiser4 Pseudo Directory Segfault
Date: Sat, 17 Dec 2005 16:37:20 -0800 [thread overview]
Message-ID: <200512171637.20232.pvh@uvic.ca> (raw)
In-Reply-To: <43A1C4F4.9090102@namesys.com>
Edward,
we are running reiser4-for-2.6.12-3.patch.gz on 2.6.12 Debian. Your patch
worked perfectly and directed us to some code that answered a few other
questions we had. Thank you.
-pvh
On December 15, 2005 11:33 am, Edward Shishkin wrote:
> Peter van Hardenberg wrote:
> >How to produce the error:
> >
> >$ chmod +w "file/...."
> >$ touch file/..../newattr
> >Segmentation fault.
>
> What the basic setup (kernel, patches) do you use?
> Indeed, in the old one the problem exists, because init_pseudo()
> does not care about missed regular plugin, so the attached patch
> fixes the problem.
>
> Thanks,
> Edward.
>
> >We tried setting "dir_eperm" on the pseudo directory plugin's create
> > member. Why didn't this fix it?
> >
> >-pvh
--
Peter van Hardenberg (pvh@pvh.ca)
Victoria, BC, Canada
prev parent reply other threads:[~2005-12-18 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-15 5:39 Reiser4 Pseudo Directory Segfault Peter van Hardenberg
2005-12-15 19:33 ` Edward Shishkin
2005-12-18 0:37 ` Peter van Hardenberg [this message]
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=200512171637.20232.pvh@uvic.ca \
--to=pvh@uvic.ca \
--cc=reiserfs-list@namesys.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.