From: Christoph Hellwig <hch@infradead.org>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] Handle ENOMEM during log initialisation
Date: Wed, 22 Oct 2008 06:11:46 -0400 [thread overview]
Message-ID: <20081022101146.GA11313@infradead.org> (raw)
In-Reply-To: <20081022061002.GG18495@disturbed>
On Wed, Oct 22, 2008 at 05:10:02PM +1100, Dave Chinner wrote:
> XFS: handle memory allocation failures during log initialisation
>
> When there is no memory left in the system, xfs_buf_get_noaddr()
> can fail. If this happens at mount time during xlog_alloc_log()
> we fail to catch the error and oops.
>
> Catch the error from xfs_buf_get_noaddr(), and allow other memory
> allocations to fail and catch those errors too. Report the error
> to the console and fail the mount with ENOMEM.
>
> Tested by manually injecting errors into xfs_buf_get_noaddr() and
> xlog_alloc_log().
>
> Signed-off-by: Dave Chinner <david@fromorbit.com>
> ---
> fs/xfs/xfs_log.c | 38 ++++++++++++++++++++++++++++++++++++--
> 1 files changed, 36 insertions(+), 2 deletions(-)
>
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index 5184017..1dfa5fe 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> - log = (xlog_t *)kmem_zalloc(sizeof(xlog_t), KM_SLEEP);
> + log = (xlog_t *)kmem_zalloc(sizeof(xlog_t), KM_MAYFAIL);
You might want to remove the cast when you touch that line anyway.
> for (i=0; i < log->l_iclog_bufs; i++) {
> *iclogp = (xlog_in_core_t *)
> - kmem_zalloc(sizeof(xlog_in_core_t), KM_SLEEP);
> + kmem_zalloc(sizeof(xlog_in_core_t), KM_MAYFAIL);
Same here.
Modulo those nitpicks this looks good.
next prev parent reply other threads:[~2008-10-22 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 6:10 [PATCH] Handle ENOMEM during log initialisation Dave Chinner
2008-10-22 10:11 ` Christoph Hellwig [this message]
2008-10-22 21:18 ` Dave 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=20081022101146.GA11313@infradead.org \
--to=hch@infradead.org \
--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