From: Andrew Morton <akpm@linux-foundation.org>
To: Valdis.Kletnieks@vt.edu
Cc: miklos@szeredi.hu, linux-kernel@vger.kernel.org,
jdike@addtoit.com, jack@suse.cz
Subject: Re: isofs - Re: 2.6.24-mm1 bugs
Date: Fri, 15 Feb 2008 12:15:48 -0800 [thread overview]
Message-ID: <20080215121548.b3c3f548.akpm@linux-foundation.org> (raw)
In-Reply-To: <19039.1203094015@turing-police.cc.vt.edu>
On Fri, 15 Feb 2008 11:46:55 -0500
Valdis.Kletnieks@vt.edu wrote:
> On Fri, 15 Feb 2008 12:43:45 +0100, Miklos Szeredi said:
> > I'm trying out 2.6.24-mm1 on my work laptop (T60), and generally it
>
> > - mounting isofs always results in an empty directory
>
> I hit this in 24-rc8-mm1, and bisected it down to
> iget-stop-isofs-from-using-read_inode-fix-2.patch
>
> Apparently it got broken way back in 24-rc6-mm1.
>
> And that directory is *really* empty - even . and .. are missing. :)
>
Seems that 2.6.24-mm1+hot-fixes still didn't have
iget-stop-isofs-from-using-read_inode-fix-3.patch:
From: David Howells <dhowells@redhat.com>
Fix isofs_get_block() to return only 0 on success. It shouldn't return a
+ve block count for example.
Also make sure that isofs_get_blocks() doesn't accidentally return an error
if rv is 0 come the return statement.
Signed-off-by: David Howells <dhowells@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
fs/isofs/inode.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff -puN fs/isofs/inode.c~iget-stop-isofs-from-using-read_inode-fix-3 fs/isofs/inode.c
--- a/fs/isofs/inode.c~iget-stop-isofs-from-using-read_inode-fix-3
+++ a/fs/isofs/inode.c
@@ -1022,6 +1022,7 @@ int isofs_get_blocks(struct inode *inode
rv++;
}
+ error = 0;
abort:
unlock_kernel();
return rv != 0 ? rv : error;
@@ -1033,12 +1034,15 @@ abort:
static int isofs_get_block(struct inode *inode, sector_t iblock,
struct buffer_head *bh_result, int create)
{
+ int ret;
+
if (create) {
printk(KERN_DEBUG "%s: Kernel tries to allocate a block\n", __func__);
return -EROFS;
}
- return isofs_get_blocks(inode, iblock, &bh_result, 1);
+ ret = isofs_get_blocks(inode, iblock, &bh_result, 1);
+ return ret < 0 ? ret : 0;
}
static int isofs_bmap(struct inode *inode, sector_t block)
_
next prev parent reply other threads:[~2008-02-15 20:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 11:43 2.6.24-mm1 bugs Miklos Szeredi
2008-02-15 12:45 ` Peter Zijlstra
2008-02-15 12:54 ` Miklos Szeredi
2008-02-18 12:05 ` Miklos Szeredi
2008-02-15 16:28 ` Kok, Auke
2008-02-15 16:41 ` Miklos Szeredi
2008-02-15 16:53 ` Kok, Auke
2008-02-15 17:51 ` Miklos Szeredi
2008-02-15 18:15 ` Miklos Szeredi
2008-02-15 18:16 ` Kok, Auke
2008-02-15 18:24 ` Miklos Szeredi
2008-02-15 18:36 ` Kok, Auke
2008-02-15 16:42 ` Kok, Auke
2008-02-15 16:46 ` isofs - " Valdis.Kletnieks
2008-02-15 20:15 ` Andrew Morton [this message]
2008-02-15 18:47 ` Jeff Dike
2008-02-15 19:52 ` Miklos Szeredi
2008-02-15 20:27 ` Bartlomiej Zolnierkiewicz
2008-02-15 20:46 ` Jeff Dike
2008-02-15 21:00 ` Miklos Szeredi
2008-02-18 21:03 ` [bug] uml doesn't boot under 2.6.25-rc1 host (was Re: 2.6.24-mm1 bugs) Miklos Szeredi
2008-02-21 17:20 ` Miklos Szeredi
2008-02-21 23:54 ` Jeff Dike
2008-02-22 4:37 ` Roland McGrath
2008-02-22 4:37 ` [PATCH] x86 ptrace: fix compat PTRACE_SETREGS Roland McGrath
2008-02-22 9:08 ` Ingo Molnar
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=20080215121548.b3c3f548.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=jack@suse.cz \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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