From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 216285] KASAN: slab-out-of-bounds in mutex_lock and NULL pointer dereference at fs/f2fs/segment.c: f2fs_update_meta_page() when mount a crafted f2fs image
Date: Tue, 26 Jul 2022 20:06:35 +0000 [thread overview]
Message-ID: <bug-216285-202145-WYYjk4S2GX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216285-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216285
Wenqing Liu (wenqingliu0120@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|KASAN: slab-out-of-bounds |KASAN: slab-out-of-bounds
|in mutex_lock and NULL |in mutex_lock and NULL
|pointer deference at |pointer dereference at
|fs/f2fs/segment.c: |fs/f2fs/segment.c:
|f2fs_update_meta_page() |f2fs_update_meta_page()
|when mount a crafted f2fs |when mount a crafted f2fs
|image |image
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2022-07-26 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 19:57 [f2fs-dev] [Bug 216285] New: KASAN: slab-out-of-bounds in mutex_lock and NULL pointer deference at fs/f2fs/segment.c: f2fs_update_meta_page() when mount a crafted f2fs image bugzilla-daemon
2022-07-26 20:06 ` bugzilla-daemon [this message]
2022-08-27 23:29 ` [f2fs-dev] [Bug 216285] KASAN: slab-out-of-bounds in mutex_lock and NULL pointer dereference " bugzilla-daemon
2022-09-07 1:39 ` bugzilla-daemon
2022-09-19 9:04 ` 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-216285-202145-WYYjk4S2GX@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 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).