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 200465] null ptr dereference in fscrypt_do_page_crypto() when operating a file on a corrupted f2fs image
Date: Mon, 17 Sep 2018 03:04:10 +0000	[thread overview]
Message-ID: <bug-200465-202145-6zGZtzx6JU@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200465-202145@https.bugzilla.kernel.org/>

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

--- Comment #3 from Chao Yu (chao@kernel.org) ---
Steve,

I figure out that patch to solve issue which I encounter with image attached by
Wen Xu, the bug can be triggered with below scripts:
- mount image /mnt/f2fs/
- cd /mnt/f2fs/foo/bar/
- ls -l

After applying that patch, the problem was gone.

But when the bug triggeres, related call stack is not the same as reported one,
also I can't reproduce reported call stack with the method provided from Wen
Xu.

I guess the right producing way is adding master key for encrypted file, I'd
like to confirm with Wen Xu.

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

  parent reply	other threads:[~2018-09-17  3:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-200465-202145@https.bugzilla.kernel.org/>
2018-08-26  0:56 ` [Bug 200465] null ptr dereference in fscrypt_do_page_crypto() when operating a file on a corrupted f2fs image bugzilla-daemon
2018-09-13 18:48 ` bugzilla-daemon
2018-09-17  3:04 ` bugzilla-daemon [this message]
2018-09-20 21:11 ` bugzilla-daemon
2018-09-21  1:41 ` 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-200465-202145-6zGZtzx6JU@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.