jfs: add check read-only before truncation in jfs_truncate_nolock()

Vulnerability Description

In the Linux kernel, the following vulnerability has been resolved: jfs: add check read-only before truncation in jfs_truncate_nolock() Added a check for "read-only" mode in the `jfs_truncate_nolock` function to avoid errors related to writing to a read-only filesystem. Call stack: block_write_begin() { jfs_write_failed() { jfs_truncate() { jfs_truncate_nolock() { txEnd() { ... log = JFS_SBI(tblk->sb)->log; // (log == NULL) If the `isReadOnly(ip)` condition is triggered in `jfs_truncate_nolock`, the function execution will stop, and no further data modification will occur. Instead, the `xtTruncate` function will be called with the "COMMIT_WMAP" flag, preventing modifications in "read-only" mode.

References

• https://git.kernel.org/stable/c/f605bc3e162f5c6faa9bd3602ce496053d06a4bb
• https://git.kernel.org/stable/c/b5799dd77054c1ec49b0088b006c9908e256843b