mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Juerg Haefliger <juerg.haefliger@canonical.com>,
	jfs-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Jfs-discussion] [PATCH] jfs: Add missing NULL pointer check in __get_metapage
Date: Thu, 2 Nov 2017 09:44:03 -0500	[thread overview]
Message-ID: <30b7320e-3fd4-71b7-3aa4-c62cbf49aa14@oracle.com> (raw)
In-Reply-To: <50f61041-7507-6410-ddf5-36892759be8b@canonical.com>

On 11/02/2017 08:43 AM, Juerg Haefliger wrote:

>>>> Furthermore, it looks like all the callers of __get_metapage() check for
>>>> a null return, so I'm not sure we need to handle the error at this
>>>> point. I might have to look a bit harder at that, since there are many
>>>> callers.
>>>
>>> I don't understand this either :-) Yes, the callers do check for a null
>>> pointer but things blow up (in __get_metapage) before that check without
>>> the above fix.
>>
>> Yeah, the fix to __get_metapage() is necessary. I'm not convinced the
>> first part of the patch, to alloc_metapage(), is necessary.
> 
> It's not. I just thought it'd be nice to get some sort of notification
> in the log when the alloc fails. But if the callers log it then that's fine.

Okay. I'll push just the __get_metapage part of your patch.

Thanks,
Shaggy

      reply	other threads:[~2017-11-02 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04  8:24 Juerg Haefliger
2017-10-25  7:50 ` Juerg Haefliger
2017-10-30 22:13   ` [Jfs-discussion] " Dave Kleikamp
2017-11-02  6:59     ` Juerg Haefliger
2017-11-02 13:15       ` Dave Kleikamp
2017-11-02 13:43         ` Juerg Haefliger
2017-11-02 14:44           ` Dave Kleikamp [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=30b7320e-3fd4-71b7-3aa4-c62cbf49aa14@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=juerg.haefliger@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®