lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon,  5 Nov 2012 13:50:28 +0000 (UTC)
Subject: [Bug 50021] ext4 discard option not working on journal dissabled

Tao Ma <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #1 from Tao Ma <>  2012-11-05 13:50:28 ---
Interesting, it works fine here with my intel ssd.
So could you please do:
1. mount -t debugfs none /sys/kernel/debug/
2. echo 1 > /sys/kernel/debug/tracing/events/ext4/ext4_discard_blocks/enable 
3. run you test
4. after 'rm', do
cat /sys/kernel/debug/tracing/trace

If your see something like 
jbd2/sdb2-8-23853 [000] .... 30125.695303: ext4_discard_blocks: dev 8,18 blk
34816 count 3072
              rm-23870 [000] .... 30130.908415: ext4_discard_blocks: dev 8,17
blk 34816 count 3072

(The first one is captured by the device with journal and the second one is
captured by the device without journal).
Then that does mean ext4 has sent out the discard command to the underlying

btw, my kernel version is 3.6.

Configure bugmail:
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists