This is the mail archive of the
ecos-maintainers@sources.redhat.com
mailing list for the eCos project.
Re: FWD: JFFS2 : Node info mutex fix suggestion.
- From: David Woodhouse <dwmw2 at infradead dot org>
- To: Gary Thomas <gary at mlbassoc dot com>
- Cc: Andrew Lunn <andrew at lunn dot ch>, eCos Maintainers <ecos-maintainers at ecos dot sourceware dot org>
- Date: Tue, 17 Feb 2004 14:58:30 +0000
- Subject: Re: FWD: JFFS2 : Node info mutex fix suggestion.
- References: <20040216170742.GF29388@lunn.ch> <1077027103.17692.32.camel@hermes>
On Tue, 2004-02-17 at 07:11 -0700, Gary Thomas wrote:
> On Mon, 2004-02-16 at 10:07, Andrew Lunn wrote:
> > Hi Folks
> >
> > Does anybody know how locking should work in the jffs2 package?
> >
> > To me this patch looks the wrong solution.
>
> I agree. I did already pass this to David, with no reply :-(
Hmmm. I think the answer is to remove the one in jffs2_do_new_inode()
instead.
That function should rely on the OS-specific code to pass it a struct
jffs2_inode_info which is initialised correctly, and that includes
having a locked semaphore in it.
I've committed the appropriate change to my CVS tree.
--
dwmw2