linux-kernel - Re: F2FS Segmentation Fault

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-prev] [day] [month] [year] [list]

Message-ID: <CALaQ_hq+Cxt7BhcEAMWXFwaOGVtVs6+kOZqoYPvze7ee-USY9A@mail.gmail.com>
Date:   Sat, 27 Mar 2021 07:41:09 -0500
From:   Nathan Royce <nroycea+kernel@...il.com>
To:     Jaegeuk Kim <jaegeuk@...nel.org>
Cc:     Chao Yu <chao@...nel.org>, linux-f2fs-devel@...ts.sourceforge.net,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: F2FS Segmentation Fault

I don't know how much of it was the issue, but when I unmounted the
sd-card, and closed the cryptsetup for it, and then ran
non-destructive badblocks on it, I was getting ONLY errors.
I stopped bb, then pulled out the card, blew on it, wiped down the
contacts with rubbing alcohol, let it dry, put it back in and now bb
is running cleanly.
I then stopped bb, tried to cryptsetup-open it and it said the
partition is not a valid LUKS device.
Weird since I was using non-destructive.
Looks like I'm now forced to rebuild that partition.

I wish I had troubleshot the aspect of the sd-card being properly
seated. I know I've experienced something similar to it in the past
where files suddenly aren't able to be read. Once I reseat the
sd-card, everything was fine.
The last time I had to even remove the card was maybe 1-2 weeks ago
when I had to deal with a noisy power-supply fan.

The whole debacle (including btrfs, keyboard leds blinking) may very
well have been from the sd-card not being seated well.

On Sat, Mar 27, 2021 at 7:02 AM Nathan Royce <nroycea+kernel@...il.com> wrote:
>
> An update, not quite 1 year later. I encountered another segfault issue.
>
> It began with my email report to the linux-btrfs mailing list titled
> "BTRFS Balance Hard System Crash (Blinking LEDs)" just the other day.
...