public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Tobias Ulmer <tu@emlix.com>
To: David Chinner <dgc@sgi.com>
Cc: Sven Geggus <lists@fuchsschwanzdomain.de>,
	xfs@oss.sgi.com, Andrea Perotti <andreamtp@goodfellow.it>
Subject: Re: [PATCH] Possible fix for 2.6.24 xfs_file_readdir crash
Date: Wed, 6 Feb 2008 10:46:17 +0100	[thread overview]
Message-ID: <E1JMgrB-0002nu-Lq@mailer.emlix.com> (raw)
In-Reply-To: <20080205052418.GU155259@sgi.com>

On Tue, Feb 05, 2008 at 04:24:18PM +1100, David Chinner wrote:
> Sven, Tomas, Andrea:
> 
> Can you try the patch attached below to see if it fixes the
> xfs_file_readdir() oops you are seeing and let me know if it fixes
> the problem?

Works for me(TM) :)

My testbox survived 24h with this patch, no problems.

Tobias

> 
> It looks like we're deferencing a pointer beyond the end of a buffer
> if the buffer is filled exactly. This bug does not crash ia64 (even
> with memory poisoning enabled), which is why the targeted corner
> case testing I did a while back did not pick this up when fixing a
> similar bug a month ago.
> 
> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> Principal Engineer
> SGI Australian Software Group
> 
> ---
> Fix yet another corner case oops in xfs_file_readdir().
> 
> Signed-off-by: Dave Chinner <dgc@sgi.com>
> ---
>  fs/xfs/linux-2.6/xfs_file.c |    3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> Index: 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_file.c
> ===================================================================
> --- 2.6.x-xfs-new.orig/fs/xfs/linux-2.6/xfs_file.c	2008-01-16 16:24:01.000000000 +1100
> +++ 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_file.c	2008-02-05 15:13:17.153110696 +1100
> @@ -351,8 +351,8 @@ xfs_file_readdir(
>  
>  		size = buf.used;
>  		de = (struct hack_dirent *)buf.dirent;
> -		curr_offset = de->offset /* & 0x7fffffff */;
>  		while (size > 0) {
> +			curr_offset = de->offset /* & 0x7fffffff */;
>  			if (filldir(dirent, de->name, de->namlen,
>  					curr_offset & 0x7fffffff,
>  					de->ino, de->d_type)) {
> @@ -363,7 +363,6 @@ xfs_file_readdir(
>  				       sizeof(u64));
>  			size -= reclen;
>  			de = (struct hack_dirent *)((char *)de + reclen);
> -			curr_offset = de->offset /* & 0x7fffffff */;
>  		}
>  	}
>  

  parent reply	other threads:[~2008-02-06  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  5:24 [PATCH] Possible fix for 2.6.24 xfs_file_readdir crash David Chinner
2008-02-06  4:55 ` Christoph Hellwig
2008-02-06  9:46 ` Tobias Ulmer [this message]
2008-02-06  9:59 ` .:deadhead:.
2008-02-09 12:04 ` Sven Geggus
2008-02-11  0:17   ` David Chinner
2008-02-11  6:35     ` Federico Sevilla III
2008-02-13  0:46       ` Jason White

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=E1JMgrB-0002nu-Lq@mailer.emlix.com \
    --to=tu@emlix.com \
    --cc=andreamtp@goodfellow.it \
    --cc=dgc@sgi.com \
    --cc=lists@fuchsschwanzdomain.de \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox