From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 214895] F2FS BUG: KASAN: stack-out-of-bounds in d_shrink_add+0x17f/0x1c0
Date: Sun, 31 Oct 2021 09:57:54 +0000 [thread overview]
Message-ID: <bug-214895-202145-jKkd5EFh4I@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-214895-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=214895
Daniel Santos (daniel.santos@pobox.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.santos@pobox.com
--- Comment #1 from Daniel Santos (daniel.santos@pobox.com) ---
That's a 3.5 year old kernel and 4.15 is EOLed. Can you see if this bug still
exists in one of the current longterm releases, like 4.19.214 or 4.14.253?
https://www.kernel.org
When you have a bug like this, it's always best to check to see if it still
exists in a longterm branch, because bug fixes are regularly back-ported to
these branches.
--
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:[~2021-10-31 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-31 9:03 [f2fs-dev] [Bug 214895] New: F2FS BUG: KASAN: stack-out-of-bounds in d_shrink_add+0x17f/0x1c0 bugzilla-daemon
2021-10-31 9:57 ` bugzilla-daemon [this message]
2021-11-01 9:41 ` [f2fs-dev] [Bug 214895] " bugzilla-daemon
2021-11-01 10:01 ` bugzilla-daemon
2021-12-11 2:14 ` bugzilla-daemon
2021-12-12 4:10 ` bugzilla-daemon
2021-12-12 4:11 ` bugzilla-daemon
2021-12-12 4:11 ` 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-214895-202145-jKkd5EFh4I@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 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).