From: Dmitry Bazhenov <atrey@emcraft.com>
To: linux-mtd@lists.infradead.org
Cc: David Woodhouse <dwmw2@infradead.org>
Subject: Re: JFFS2 has possible race when setting file attributes
Date: Fri, 5 May 2006 16:44:33 +0400 [thread overview]
Message-ID: <200605051644.33891.atrey@emcraft.com> (raw)
In-Reply-To: <1146830084.20773.117.camel@pmac.infradead.org>
On Friday 05 May 2006 15:54, David Woodhouse wrote:
> Thanks. Please could you resend, including a 'Signed-off-by:' line?
I posted it to the list, but it didn't appear. So, I repost it.
It seems like there is a potential race in the function jffs2_do_setattr() in
the case when attributes of a symlink are updated. The symlink metadata is
read without having f->sem locked.
The following patch should fix the race.
Signed-off-by: Dmitry Bazhenov <atrey@emcraft.com>
--- a/fs/jffs2/fs.c 2006-04-29 18:51:53.000000000 +0400
+++ b/fs/jffs2/fs.c 2006-05-04 17:32:09.000000000 +0400
@@ -56,15 +56,20 @@ static int jffs2_do_setattr (struct inod
mdatalen = sizeof(dev);
D1(printk(KERN_DEBUG "jffs2_setattr(): Writing %d bytes of
kdev_t\n", mdatalen));
} else if (S_ISLNK(inode->i_mode)) {
+ down(&f->sem);
mdatalen = f->metadata->size;
mdata = kmalloc(f->metadata->size, GFP_USER);
- if (!mdata)
+ if (!mdata) {
+ up(&f->sem);
return -ENOMEM;
+ }
ret = jffs2_read_dnode(c, f, f->metadata, mdata, 0, mdatalen);
if (ret) {
+ up(&f->sem);
kfree(mdata);
return ret;
}
+ up(&f->sem);
D1(printk(KERN_DEBUG "jffs2_setattr(): Writing %d bytes of
symlink target\n", mdatalen));
}
--
Dmitry
prev parent reply other threads:[~2006-05-05 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 6:50 JFFS2 has possible race when setting file attributes Dmitry Bazhenov
2006-05-05 11:54 ` David Woodhouse
2006-05-05 12:44 ` Dmitry Bazhenov [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=200605051644.33891.atrey@emcraft.com \
--to=atrey@emcraft.com \
--cc=dwmw2@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