public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Niv Sardi <xaiki@cxhome.ath.cx>
Cc: David Chinner <dgc@sgi.com>, xfs-dev <xfs-dev@sgi.com>, xfs@oss.sgi.com
Subject: Re: [Review] Improve XFS error checking and propagation
Date: Wed, 2 Apr 2008 14:07:08 +1000	[thread overview]
Message-ID: <20080402040708.GB103491721@sgi.com> (raw)
In-Reply-To: <nccfxu5kloe.fsf@sgi.com>

On Wed, Apr 02, 2008 at 01:58:09PM +1100, Niv Sardi wrote:
> David Chinner <dgc@sgi.com> writes:
> > On Tue, Mar 11, 2008 at 12:04:21PM +1100, David Chinner wrote:
> >> A recent paper at the FAST08 conference highlighted a large number
> >> of unchecked error paths in Linux filesystems and I/O layers.  As a
> >> subsystem, XFS had the highest aggregate numbers of bad error
> >> propagation. A tarball which contains a quilt patch series of 32
> >> patches aimed at improving this situation can be found here:
> >> 
> >> http://oss.sgi.com/~dgc/xfs/error-check/xfs-error-checking.tar.gz
> 
> All looks good except some minor typo-editing,
> 
> and
> 
> NOK xfs-mustcheck-quotamount.patch # need to check if can happen when forcing quotas
> 
> I'm not sure what happens if we really DO want quotas (specified on
> mount line and such).

The behaviour will be exactly the same as previously, because the
error returned by xfs_qm_mount_quotas() is ignored.  i.e. if we try
to mount with quotas and the quota mount fails, we continue (after
issuing a warning to syslog) that quotas were not turned on.

This is especially important for root filesystems with quota
enabled....

> OK xfs-mustcheck-reset-dqcounts.patch
> OK xfs-mustcheck-dqflushall.patch
> OK xfs-mustcheck-acl-setmode.patch
> OK xfs-mustcheck-search-busy.patch
> EDITED xfs-mustcheck-compute-diff.patch # xfs_fs_cmn_err alignment

That patch doesn't have any calls to xfs_fs_cmn_err() in it. Can you
clarify, please?

> OK xfs-mustcheck-bmap-adjacent.patch
> OK xfs-mustcheck-iflush-fork.patch # less error handeling !!

You can't have less error handling than intentionally ignoring
the return from a function that can't return an error. You can
have simpler code, though, by declaring the function void....

> OK xfs-mustcheck-bulkstat-dinode.patch
> OK xfs-mustcheck-quiesce-fs.patch
> OK xfs-mustcheck-bdstrat.patch
> OK xfs-fix-error-prototypes.patch # not error handeling related
> OK xfs-mustcheck-acl-vremove.patch
> OK xfs-mustcheck-icsb-disable.patch
> OK xfs-mustcheck-ioend-unwritten.patch
> OK xfs-mustcheck-buf-associate.patch
> OK xfs-mustcheck-reserve-blocks.patch
> EDITED xfs-mustcheck-bawrite.patch # xfs_fs_cmn_err alignment

Which means?

> OK xfs-mustcheck-bdwrite.patch
> OK xfs-mustcheck-truncate-page.patch # might be incomplete

Incomplete in what way?

> EDITED xfs-mustcheck-dqflush.patch # slight style change/typo

Details?

> OK xfs-mustcheck-reset-sbqflags.patch
> OK xfs-mustcheck-quotaoff.patch
> EDITED xfs-mustcheck-inactive.patch # slight style change/typo

Details?

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2008-04-02  4:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11  1:04 [Review] Improve XFS error checking and propagation David Chinner
2008-04-01 23:00 ` David Chinner
2008-04-02  2:58   ` Niv Sardi
2008-04-02  4:07     ` David Chinner [this message]
2008-04-02  4:31       ` Niv Sardi
2008-04-02  5:12         ` David Chinner

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=20080402040708.GB103491721@sgi.com \
    --to=dgc@sgi.com \
    --cc=xaiki@cxhome.ath.cx \
    --cc=xfs-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox