All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: Nikolay Borisov <kernel@kyup.com>
Cc: "Yan, Zheng" <zyan@redhat.com>,
	ceph-devel <ceph-devel@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2] ceph: Fix error handling in ceph_read_iter
Date: Mon, 10 Oct 2016 15:50:42 +0200	[thread overview]
Message-ID: <CAOi1vP_piBraimiPzzZL8h9d1WLjJ9h1amYbmsUBSJfprT9u-Q@mail.gmail.com> (raw)
In-Reply-To: <57FB93ED.5030602@kyup.com>

On Mon, Oct 10, 2016 at 3:13 PM, Nikolay Borisov <kernel@kyup.com> wrote:
>
>
> On 10/10/2016 04:11 PM, Yan, Zheng wrote:
>>
>>> On 10 Oct 2016, at 20:56, Nikolay Borisov <kernel@kyup.com> wrote:
>>>
>>> In case __ceph_do_getattr returns an error and the retry_op in
>>> ceph_read_iter is not READ_INLINE, then it's possible to invoke
>>> __free_page on a page which is NULL, this naturally leads to a crash.
>>> This can happen when, for example, a process waiting on a MDS reply
>>> receives sigterm.
>>>
>>> Fix this by explicitly checking whether the page is set or not.
>>>
>>> Signed-off-by: Nikolay Borisov <kernel@kyup.com>
>>> Link: http://www.spinics.net/lists/ceph-users/msg31592.html
>>> ---
>>>
>>> Inverted the condition, so resending with correct condition
>>> this time.
>>>
>>> fs/ceph/file.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/fs/ceph/file.c b/fs/ceph/file.c
>>> index 3c68e6aee2f0..7413313ae6c8 100644
>>> --- a/fs/ceph/file.c
>>> +++ b/fs/ceph/file.c
>>> @@ -929,7 +929,8 @@ again:
>>>              statret = __ceph_do_getattr(inode, page,
>>>                                          CEPH_STAT_CAP_INLINE_DATA, !!page);
>>>              if (statret < 0) {
>>> -                     __free_page(page);
>>> +                    if (page)
>>> +                            __free_page(page);
>>>                      if (statret == -ENODATA) {
>>>                              BUG_ON(retry_op != READ_INLINE);
>>>                              goto again;
>>> —
>> Reviewed-by: Yan, Zheng <zyan@redhat.com>
>
> I believe this needs to also be tagged as stable. To whomever is going
> to merge it: can you please do that?

I'll do that.  Zheng, do you see any other issues with the killable
wait here?

Thanks,

                Ilya

  parent reply	other threads:[~2016-10-10 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 12:38 [PATCH] ceph: Fix error handling in ceph_read_iter Nikolay Borisov
2016-10-10 12:56 ` [PATCHv2] " Nikolay Borisov
2016-10-10 13:11   ` Yan, Zheng
2016-10-10 13:13     ` Nikolay Borisov
2016-10-10 13:14       ` Yan, Zheng
2016-10-10 13:50       ` Ilya Dryomov [this message]
2016-10-10 15:09         ` Yan, Zheng

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=CAOi1vP_piBraimiPzzZL8h9d1WLjJ9h1amYbmsUBSJfprT9u-Q@mail.gmail.com \
    --to=idryomov@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=kernel@kyup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zyan@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 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.