linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel@vger.kernel.org, jack@suse.cz, hch@infradead.org,
	sandeen@redhat.com
Subject: Re: [PATCH 0/6] RFC quota: Redesign IO error handling interface
Date: Fri, 7 May 2010 18:38:25 +0200	[thread overview]
Message-ID: <20100507163825.GD3700@quack.suse.cz> (raw)
In-Reply-To: <1270749865-25441-1-git-send-email-dmonakhov@openvz.org>

On Thu 08-04-10 22:04:19, Dmitry Monakhov wrote:
> This patchset is tended to provide interface for handling IO errors
> from internal quota code.
> Any error must being returned to fs-caller to signal about possible
> quota inconsistency. I've done it in following way:
> 
> 1) Handle low-level io errors from dqget() and it's callers
> 2) Handle errors from dquot_initialize
>    This path catch most of IO error, but no all.
> 3) Check what i_dquot was initialized in each low-level function.
>    There are two types of such functions
>    3A) Charging functions (alloc_{space,inode}): Caller of such
>        function may easy handle an error and abort an operation.
>    3B) nofail functions (claim_space,free_{space,inode})
>        In most cases caller can not abort an operation even if
>        inode's quotas was semi-initialized, so I just skip this
>        functions for now.
> I would like to know you ideas suggestions about this.
> Note: Only ext4's part was basically tested for now, others was just
> compile tested.
  Sorry for not replying earlier. I've glanced over the patch set and I
have no major objections. I'll send you now the problems I've found and
next week I will have a more detailed look.

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

      parent reply	other threads:[~2010-05-07 16:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08 18:04 [PATCH 0/6] RFC quota: Redesign IO error handling interface Dmitry Monakhov
2010-04-08 18:04 ` [PATCH 1/6] quota: unify quota init condition in setattr Dmitry Monakhov
2010-04-08 18:04   ` [PATCH 2/6] quota: Add proper error handling on quota initialization Dmitry Monakhov
2010-04-08 18:04     ` [PATCH 3/6] quota: Check what quota is properly initialized for inode before charge Dmitry Monakhov
2010-04-08 18:04       ` [PATCH 4/6] ext3: handle errors in orphan_cleanup Dmitry Monakhov
2010-04-08 18:04         ` [PATCH 5/6] ext4: " Dmitry Monakhov
2010-04-08 18:04           ` [PATCH 6/6] quota: check error code from dquot_initialize Dmitry Monakhov
2010-05-07 17:01             ` Jan Kara
2010-05-07 16:59         ` [PATCH 4/6] ext3: handle errors in orphan_cleanup Jan Kara
2010-05-07 16:48       ` [PATCH 3/6] quota: Check what quota is properly initialized for inode before charge Jan Kara
2010-05-17  6:22         ` Dmitry Monakhov
2010-05-07 16:44     ` [PATCH 2/6] quota: Add proper error handling on quota initialization Jan Kara
2010-05-07 16:39   ` [PATCH 1/6] quota: unify quota init condition in setattr Jan Kara
2010-05-13 16:29   ` Jan Kara
2010-05-05  8:45 ` [PATCH 0/6] RFC quota: Redesign IO error handling interface Dmitry Monakhov
2010-05-07 16:38 ` Jan Kara [this message]

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=20100507163825.GD3700@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=dmonakhov@openvz.org \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).