linux-kernel - Seeking recommendation on whether a bahviour is right/wrong

lists.openwall.net		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-next>] [day] [month] [year] [list]

Message-ID: <CAHP4M8V6sD5rWEwSeOTvnrmi+EvpSwp78CmxV1M=xS97cqO+TA@mail.gmail.com>
Date:   Fri, 19 Aug 2016 10:56:37 +0530
From:   Ajay Garg <ajaygargnsit@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: Seeking recommendation on whether a bahviour is right/wrong

Hi All.

I have been trying to debug a strange issue occurring on a "mostly
mainline"-linux-kernel, running on a proprietary embedded-platform.

I still haven't been able to zero-on the issue with 100% confirmation,
but I think the following might be happening ::

a)
A C-user-application is running, and a file is being written, one byte
at a time.
Let's say the file-name being written is "file1.txt"

b)
There's another file "file2.txt", which is in absolutely sane-state
(no open file-descriptors, etc.)

c)
Now, a cron-script reboots the machine via /sbin/reboot "abruptly"
(i.e. without closing the open-file-descriptor of "file1.txt").

d)
When the machine comes up, we find that "file2.txt" is corrupted.

In this behaviour, is the kernel at fault?
Or the cron-job is the culprit for abrupt reboot?

Thanks and Regards,
Ajay