linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anatoly Trosinenko <anatoly.trosinenko@gmail.com>
To: "Ernesto A. Fernandez" <ernesto.mnd.fernandez@gmail.com>
Cc: pavel@ucw.cz, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Subject: Re: Mounting corrupted HFS+ causes kernel NULL pointer dereference
Date: Mon, 2 Jul 2018 10:41:27 +0300	[thread overview]
Message-ID: <CAE5jQCfP1ZteOhBD3-inASWtp1i-0NuFhZCSKyEy=wx+eQ=bbw@mail.gmail.com> (raw)
In-Reply-To: <20180629184542.jwxhruxgp5xv2abt@eaf>

Thank you, now (with just this patch applied on top of v4.18-rc2) it
just (asynchronously?) writes `hfsplus: b-tree write err: -5, ino: 3`
to dmesg and does not segfaults.
пт, 29 июн. 2018 г. в 21:45, Ernesto A. Fernández
<ernesto.mnd.fernandez@gmail.com>:
>
> Hi again:
>
> A patch for your original report has already been added to the -mm tree.
>
> On Tue, Jun 12, 2018 at 09:43:26PM +0300, Anatoly Trosinenko wrote:
> > Now, when mounting the attached hfsplus_16mb_segv to /mnt and
> > performing `dd if=/dev/zero of=/mnt/xyz bs=567879 count=1` I get
> >
> > [    1.646451] BUG: unable to handle kernel NULL pointer dereference
> > at 0000000000000043
>
> I just sent you a patch for this second report. It's really simple, so
> it would be great if you could take a look at it and review it yourself.
> Otherwise it's not very likely to get picked up.
>
> Thanks,
> Ernest



-- 
С уважением,
Анатолий Тросиненко
e-mail: anatoly.trosinenko@gmail.com

  parent reply	other threads:[~2018-07-02  7:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03 15:52 Mounting corrupted HFS+ causes kernel NULL pointer dereference Anatoly Trosinenko
2018-06-03 18:49 ` Ernesto A. Fernández
2018-06-03 19:06   ` Anatoly Trosinenko
2018-06-08 15:25   ` Pavel Machek
2018-06-12 18:43     ` Anatoly Trosinenko
2018-06-12 21:35       ` Ernesto A. Fernández
2018-06-16  9:58         ` Anatoly Trosinenko
2018-06-29 18:45       ` Ernesto A. Fernández
2018-06-30  2:38         ` Ernesto A. Fernández
2018-07-02  7:41         ` Anatoly Trosinenko [this message]
2018-07-09 20:34       ` Ernesto A. Fernández
2018-07-10 17:28         ` Anatoly Trosinenko
2018-07-10 18:38           ` Ernesto A. Fernández
2018-07-10 18:57             ` Anatoly Trosinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE5jQCfP1ZteOhBD3-inASWtp1i-0NuFhZCSKyEy=wx+eQ=bbw@mail.gmail.com' \
    --to=anatoly.trosinenko@gmail.com \
    --cc=ernesto.mnd.fernandez@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).