From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: muirj@nortel.com, mszeredi@suse.cz
Subject: + fuse-fix-uninitialized-field-in-fuse_inode.patch added to -mm tree
Date: Thu, 15 Nov 2007 19:27:17 -0800 [thread overview]
Message-ID: <200711160327.lAG3RHOR030787@imap1.linux-foundation.org> (raw)
The patch titled
fuse: fix uninitialized field in fuse_inode
has been added to the -mm tree. Its filename is
fuse-fix-uninitialized-field-in-fuse_inode.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: fuse: fix uninitialized field in fuse_inode
From: John Muir <muirj@nortel.com>
I found problems accessing (executing) previously existing files, until
I did chmod on them (or setattr).
If the fi->attr_version is not initialized, then it could be
larger than fc->attr_version until a setattr is executed, and as a
result the inode attributes would never be set.
Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/fuse/inode.c | 1 +
1 file changed, 1 insertion(+)
diff -puN fs/fuse/inode.c~fuse-fix-uninitialized-field-in-fuse_inode fs/fuse/inode.c
--- a/fs/fuse/inode.c~fuse-fix-uninitialized-field-in-fuse_inode
+++ a/fs/fuse/inode.c
@@ -56,6 +56,7 @@ static struct inode *fuse_alloc_inode(st
fi->i_time = 0;
fi->nodeid = 0;
fi->nlookup = 0;
+ fi->attr_version = 0;
INIT_LIST_HEAD(&fi->write_files);
fi->forget_req = fuse_request_alloc();
if (!fi->forget_req) {
_
Patches currently in -mm which might be from muirj@nortel.com are
fuse-fix-uninitialized-field-in-fuse_inode.patch
reply other threads:[~2007-11-16 3:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200711160327.lAG3RHOR030787@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=mszeredi@suse.cz \
--cc=muirj@nortel.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.