[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE5jQCd0dD2jcNLGXK0N1g6TOfNfruyTV-7R6Eh1v65bkoqi1g@mail.gmail.com>
Date: Tue, 10 Jul 2018 20:28:37 +0300
From: Anatoly Trosinenko <anatoly.trosinenko@...il.com>
To: "Ernesto A. Fernandez" <ernesto.mnd.fernandez@...il.com>
Cc: pavel@....cz, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Subject: Re: Mounting corrupted HFS+ causes kernel NULL pointer dereference
Thank you,
When applied this single patch on v4.18-rc4 and performed "echo >
/mnt/xyz" on hfsplus_16mb_hang image, I get about 14 pairs of lines
hfsplus: unable to mark blocks free: error -5
hfsplus: can't free extent
Then `echo` exits with "No space left on device" error. Then it
permits to perform `rm /mnt/xyz` and on `echo > /mnt/1` it responds
with no space left on device (but file *is* created and is cattable).
I don't know what is safer, but now it doesn't deadlock. :) Maybe it
is even worth to remount FS r/o, I don't know. (Please excuse me for
speculations)
Thanks,
Anatoly
пн, 9 июл. 2018 г. в 23:35, Ernesto A. Fernández
<ernesto.mnd.fernandez@...il.com>:
>
> On Tue, Jun 12, 2018 at 09:43:26PM +0300, Anatoly Trosinenko wrote:
> > And when I mount hfsplus_16mb_hang and perform `echo > /mnt/xyz`, it hangs.
>
> I just sent you a patch for this final report. Let me know if it works
> for you.
Powered by blists - more mailing lists