cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Thomas Tai <thomas.tai@oracle.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] gfs2: fix slab corruption during mounting and umounting gfs file system
Date: Tue, 15 Aug 2017 13:59:10 -0400	[thread overview]
Message-ID: <79a6f301-8a95-e90c-b742-9e0754b096fa@oracle.com> (raw)
In-Reply-To: <1824068695.880672.1502817050529.JavaMail.zimbra@redhat.com>



On 2017-08-15 01:10 PM, Bob Peterson wrote:
> ----- Original Message -----
> | When using cman-3.0.12.1 and gfs2-utils-3.0.12.1, mounting and
> | unmounting GFS2 file system would cause kernel to hang. The slab
> | allocator suggests that it is likely a double free memory corrruption.
> | The issue is traced back to v3.9-rc6 where a patch is submitted to
> | use kzalloc() for storing a bitmap instead of using a local variable.
> | The intention is to allocate memory during mounting and to free memory
> | during unmounting. The original patch misses a code path which has
> | already freed the memory and caused memory corruption. This patch sets
> | the memory pointer to NULL after the memory is freed, so that double
> | free memory corruption will not be happened.
> |
> | gdlm_mount()
> |   '-- set_recover_size() which use kzalloc()
> |   '-- if dlm does not support ops callbacks then
> |           '--- free_recover_size() which use kfree()
> |
> | gldm_unmount()
> |   '-- free_recover_size() which use kfree()
> |
> | Previous patch which introduce the double free issue is
> | commit 57c7310b8eb9 ("GFS2: use kmalloc for lvb bitmap")
> |
> | Signed-off-by: Thomas Tai <thomas.tai@oracle.com>
> | Reviewed-by: Liam R. Howlett <Liam.Howlett@Oracle.com>
> | ---
> Hi,
> 
> Thanks. This is now pushed to the for-next branch of the linux-gfs2 tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/gfs2/linux-gfs2.git/commit/fs/gfs2?h=for-next&id=cc1dfa8b7571ea16dec9a29e0f4c4cad90b2a761
> 
> Please note that I fixed up the grammar a bit in your patch description.
> 

Hi Bob,
Thank you very much for your quick response and helps.

Thanks,
Thomas


> Regards,
> 
> Bob Peterson
> Red Hat File Systems
> 



      reply	other threads:[~2017-08-15 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 15:03 [Cluster-devel] [PATCH] gfs2: fix slab corruption during mounting and umounting gfs file system Thomas Tai
2017-08-15 17:10 ` Bob Peterson
2017-08-15 17:59   ` Thomas Tai [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=79a6f301-8a95-e90c-b742-9e0754b096fa@oracle.com \
    --to=thomas.tai@oracle.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).