From: Christoph Hellwig <hch@lst.de>
To: Takeo Tung <kernel@takeo.idv.tw>
Cc: Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
sfr@canb.auug.org.au
Subject: Re: linux-next-20100608 will /bin/sh: scripts/basic/fixdep: Permission denied
Date: Sat, 12 Jun 2010 11:49:37 +0200 [thread overview]
Message-ID: <20100612094937.GA12455@lst.de> (raw)
In-Reply-To: <F8C0125B8F424A279E9679EAC24AC983@TAKEOW7NB1>
Please try the patch below, looks like I did a horrible messup in the
last version of the patch:
Index: linux-2.6/fs/attr.c
===================================================================
--- linux-2.6.orig/fs/attr.c 2010-06-12 11:45:50.458003839 +0200
+++ linux-2.6/fs/attr.c 2010-06-12 11:45:59.103005305 +0200
@@ -34,7 +34,7 @@ int inode_change_ok(const struct inode *
* First check size constraints. These can't be overriden using
* ATTR_FORCE.
*/
- if (attr->ia_mode & ATTR_SIZE) {
+ if (ia_valid & ATTR_SIZE) {
int error = inode_newsize_ok(inode, attr->ia_size);
if (error)
return error;
next prev parent reply other threads:[~2010-06-12 9:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 15:13 linux-next-20100608 will /bin/sh: scripts/basic/fixdep: Permission denied Takeo Tung
2010-06-11 20:07 ` Michal Marek
2010-06-12 8:44 ` Takeo Tung
2010-06-12 9:49 ` Christoph Hellwig [this message]
2010-06-12 19:35 ` Takeo Tung
2010-06-28 10:52 ` block: unify flags for struct bio and struct request will kernel panic Takeo Tung
2010-07-07 23:05 ` [PATCH] struct io panic on raid1 - " Takeo Tung
2010-07-07 23:17 ` Christoph Hellwig
2010-07-07 23:48 ` Neil Brown
2010-07-08 0:43 ` Takeo Tung
2010-07-08 1:15 ` Neil Brown
2010-07-08 1:42 ` Takeo Tung
-- strict thread matches above, loose matches on Subject: below --
2010-06-11 15:04 linux-next-20100608 will /bin/sh: scripts/basic/fixdep: Permission denied Takeo Tung
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=20100612094937.GA12455@lst.de \
--to=hch@lst.de \
--cc=kernel@takeo.idv.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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.