From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 200951] kernel NULL pointer dereference in update_sit_entry
Date: Sat, 01 Sep 2018 12:53:38 +0000 [thread overview]
Message-ID: <bug-200951-202145-fUvsafRiRJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200951-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200951
--- Comment #4 from vicencb@gmail.com ---
Hi! Yes, it is reproducible.
Each time TRIM is enabled via the UDEV rule and the FS mounted with
the discard option, the issue is triggered at the very first write attempt.
Before mounting fsck.f2fs was successfully run on the FS.
Regards,
Vicenç.
--
You are receiving this mail because:
You are watching the assignee of the bug.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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:[~2018-09-01 12:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 13:44 [Bug 200951] New: kernel NULL pointer dereference in update_sit_entry bugzilla-daemon
2018-08-27 13:45 ` [Bug 200951] " bugzilla-daemon
2018-08-27 13:46 ` bugzilla-daemon
2018-08-31 8:17 ` bugzilla-daemon
2018-09-01 12:53 ` bugzilla-daemon [this message]
2018-09-01 12:54 ` bugzilla-daemon
2018-09-01 13:18 ` bugzilla-daemon
2018-09-02 6:52 ` bugzilla-daemon
2018-09-02 16:47 ` bugzilla-daemon
2018-09-02 16:49 ` bugzilla-daemon
2018-09-02 16:50 ` bugzilla-daemon
2018-09-03 1:27 ` bugzilla-daemon
2018-09-03 9:35 ` bugzilla-daemon
2018-09-03 9:41 ` bugzilla-daemon
2018-09-03 9:54 ` bugzilla-daemon
2018-09-04 9:43 ` bugzilla-daemon
2018-09-04 12:51 ` bugzilla-daemon
2018-09-04 14:13 ` bugzilla-daemon
2018-09-11 3:15 ` 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-200951-202145-fUvsafRiRJ@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).