From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org, dmwm2@infradead.org
Subject: Possible JFFS2 bug
Date: Fri, 12 Apr 2002 20:21:08 +1200 [thread overview]
Message-ID: <20020412090913.3DDE34059@creative.actrix.co.nz> (raw)
In-Reply-To: <200204080906.47847.hxos@rz.fh-augsburg.de>
I'm not using JFFS2, but I happened to be reading the code in 2.4.18
In dir.c/jffs2_readdir()....
I notice that if the filldir returns <0 during the fill for "." and "..", the
execution gotos out:. This bypasses the down() of the semaphore, however the
semaphore still gets up()ed.
The up without a corresponding down was, I hunch, unintended.
Maybe someone using the code would like to take a look.
-- Charles
next prev parent reply other threads:[~2002-04-12 9:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-08 7:06 Problems with writing on jffs2 Stefan Warmuth
2002-04-09 12:18 ` David Woodhouse
2002-04-12 8:21 ` Charles Manning [this message]
2002-04-12 12:52 ` Possible JFFS2 bug Elizabeth Clarke
-- strict thread matches above, loose matches on Subject: below --
2008-08-12 11:23 Adrian Hunter
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=20020412090913.3DDE34059@creative.actrix.co.nz \
--to=manningc2@actrix.gen.nz \
--cc=dmwm2@infradead.org \
--cc=linux-mtd@lists.infradead.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