All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 202747] sometime kernel crash when kzfree is called in fs/f2fs/xattr.c
Date: Tue, 05 Mar 2019 06:40:30 +0000	[thread overview]
Message-ID: <bug-202747-202145-vOMSx4rC2N@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202747-202145@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=202747

Chao Yu (chao@kernel.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |chao@kernel.org

--- Comment #1 from Chao Yu (chao@kernel.org) ---
I didn't see many filesystems are using kzfree(), instead, there are many
callers come from crypto module, I guess they use the buffer to store
ciphertext or crypto key temporarily, so, before freeing those buffer it will
be better to clean the data in buffer to avoid confidential data leak.

For f2fs, I think there is no such demand, and we just missed to change kzfree
to kvfree in below commit:

5222595d093e ("f2fs: use kvmalloc, if kmalloc is failed")

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  reply	other threads:[~2019-03-05  6:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 13:30 [Bug 202747] New: sometime kernel crash when kzfree is called in fs/f2fs/xattr.c bugzilla-daemon
2019-03-05  6:40 ` bugzilla-daemon [this message]
2019-03-16  8:09 ` [Bug 202747] " bugzilla-daemon

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=bug-202747-202145-vOMSx4rC2N@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.