From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [Bug 200951] New: kernel NULL pointer dereference in update_sit_entry
Date: Mon, 27 Aug 2018 13:44:43 +0000 [thread overview]
Message-ID: <bug-200951-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=200951
Bug ID: 200951
Summary: kernel NULL pointer dereference in update_sit_entry
Product: File System
Version: 2.5
Kernel Version: v4.19-rc1, v4.18.2
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: f2fs
Assignee: filesystem_f2fs@kernel-bugs.kernel.org
Reporter: vicencb@gmail.com
Regression: No
Created attachment 278127
--> https://bugzilla.kernel.org/attachment.cgi?id=278127&action=edit
dmesg
Hi,
in the setup there is a SATA SSD connected to a SATA-to-USB bridge.
The disc is "Samsung SSD 850 PRO 256G" which supports TRIM.
There are four partitions:
sda1: FAT /boot
sda2: F2FS /
sda3: F2FS /home
sda4: F2FS
The bridge is ASMT1153e which uses the "uas" driver.
There is no TRIM pass-through, so, when mounting it reports:
mounting with "discard" option, but the device does not support discard
The USB host is USB3.0 and UASP capable. It is the one on RK3399.
Given this everything works fine, except there is no TRIM support.
In order to enable TRIM a new UDEV rule is added [1]:
/etc/udev/rules.d/10-sata-bridge-trim.rules:
ACTION=="add|change", ATTRS{idVendor}=="174c", ATTRS{idProduct}=="55aa",
SUBSYSTEM=="scsi_disk", ATTR{provisioning_mode}="unmap"
After reboot any F2FS write hangs forever and dmesg reports:
Unable to handle kernel NULL pointer dereference
Also tested on a x86_64 system: works fine even with TRIM enabled.
same disc
same bridge
different usb host controller
different cpu architecture
not root filesystem
Regards,
Vicenç.
[1] Post #5 in https://bbs.archlinux.org/viewtopic.php?id=236280
--
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 reply other threads:[~2018-08-27 13:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 13:44 bugzilla-daemon [this message]
2018-08-27 13:45 ` [Bug 200951] kernel NULL pointer dereference in update_sit_entry bugzilla-daemon
2018-08-27 13:46 ` bugzilla-daemon
2018-08-31 8:17 ` bugzilla-daemon
2018-09-01 12:53 ` bugzilla-daemon
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@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).