From: Eric Sandeen <sandeen@sandeen.net>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: PARTIAL TAKE 987159 - Fix extent list corruption in xfs_iext_irec_compact_full().
Date: Sun, 05 Oct 2008 06:56:10 -0500 [thread overview]
Message-ID: <48E8AB5A.7080301@sandeen.net> (raw)
In-Reply-To: <20080923032821.A91D758C52AE@chook.melbourne.sgi.com>
Lachlan McIlroy wrote:
> Fix extent list corruption in xfs_iext_irec_compact_full().
>
> If we don't move all the records from the next buffer into the current buffer
> then we need to update the er_extoff field of the next buffer as we shift the
> remaining records to the start of the buffer.
>
> Date: Tue Sep 23 13:20:30 AEST 2008
> Workarea: redback.melbourne.sgi.com:/home/lachlan/isms/2.6.x-xfs
> Inspected by:
> sandeen@sandeen.net
> cattelan@thebarn.com
> Author: lachlan
>
> The following file(s) were checked into:
> longdrop.melbourne.sgi.com:/isms/linux/2.6.x-xfs-melb
>
>
> Modid: xfs-linux-melb:xfs-kern:32165a
> fs/xfs/xfs_inode.c - 1.521 - changed
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/> xfs_inode.c.diff?r1=text&tr1=1.521&r2=text&tr2=1.520&f=h
> http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_inode.c.diff?r1=text&tr1=1.521&r2=text&tr2=1.520&f=h
> - Fix extent list corruption in xfs_iext_irec_compact_full().
Are there plans to try to get this, and possibly the compact_full
removal pushed into 2.6.27 still? (and maybe even 2.6.26.x?)
-Eric
next prev parent reply other threads:[~2008-10-05 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 3:28 PARTIAL TAKE 987159 - Fix extent list corruption in xfs_iext_irec_compact_full() Lachlan McIlroy
2008-10-05 11:56 ` Eric Sandeen [this message]
2008-10-05 12:00 ` Eric Sandeen
2008-10-06 1:00 ` Mark Goodwin
2008-10-06 17:24 ` Russell Cattelan
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=48E8AB5A.7080301@sandeen.net \
--to=sandeen@sandeen.net \
--cc=lachlan@sgi.com \
--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 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.