[SRU][Q][PATCH 0/1] ubuntu_blktrace_smoke_test fails on questing with rust coreutils (LP: #2137698)

[Edoardo Canepa]

BugLink: https://bugs.launchpad.net/bugs/2137698

SRU Justification:

[Impact]

ubuntu_blktrace_smoke_test fails on questing with rust coreutils enabled.
Executing with GNU coreutils makes the test pass.

  ID: com.canonical.kernel::ubuntu_blktrace_smoke_test/blktrace-smoke-test
  Category: com.canonical.plainbox::uncategorised
  ... 8<
-------------------------------------------------------------------------
  PASSED (CONFIG_BLK_DEV_IO_TRACE=y in /boot/config-6.17.0-11-generic)

  Using block device /dev/loop0 for path /tmp/cwd-
hmzznri9.43f7bf5d91458d09dc595f27a2105298dbd7be4196a6f7444786bd783e1e92a1/mnt

  Test regime:
   dd performing 65536 1K block writes
   looking for at least 1024 blktrace events

  Sat Dec 20 19:52:16 UTC 2025: blktrace starting
  Sat Dec 20 19:52:16 UTC 2025: dd starting
  Sat Dec 20 19:52:16 UTC 2025: dd stopped
  Sat Dec 20 19:52:16 UTC 2025: waiting for 10 seconds
  Sat Dec 20 19:52:26 UTC 2025: blktrace being terminated
  Sat Dec 20 19:52:26 UTC 2025: blktrace terminated
  Sat Dec 20 19:52:26 UTC 2025: blktrace data parsed

  FAILED (expecting at least 1024 block traces events from the dd process,
got 0)
  FAILED (expecting at least 1024 block read traces events, got 0)
  FAILED (expecting at least 1024 block write traces events, got 0)

[Fix]

Revert commit "ext4: fail unaligned direct IO write with EINVAL".

[Test Plan]

To reproduce the issue:
execute ubuntu_blktrace_smoke_test

with the reverted commit the test should pass as before the commit was pulled.

[Where problems could occur]

The regression potential is low, since this commit was actually a cleanup of an unnecessary error condition.

That said, further investigation should be made as to why it behaves differently on rust and GNU coreutils.