linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>
Cc: Anatoly Trosinenko <anatoly.trosinenko@gmail.com>,
	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: Fri, 8 Jun 2018 17:25:57 +0200	[thread overview]
Message-ID: <20180608152557.GB11958@amd> (raw)
In-Reply-To: <20180603184955.zrowxp4y3ij66y5n@eaf>

[-- Attachment #1: Type: text/plain, Size: 959 bytes --]

On Sun 2018-06-03 15:49:56, Ernesto A. Fernández wrote:
1;2802;0c> Hi, thank you for your report.
> 
> On Sun, Jun 03, 2018 at 06:52:19PM +0300, Anatoly Trosinenko wrote:
> > How to reproduce:
> > 1. Take kernel source v4.17-rc7
> > 2. Compile it with the config attached
> > 3. Unpack and mount the attached FS image as hfsplus.
> 
> We are aware of this issue and I've sent some patches [1][2]. It's hard
> to get reviewers interested in hfsplus, so I don't know when it will be
> fixed.

I guess Anatoly can still test the patches, and add Tested-by tags if
they help. No guarantees, but that may make it easier to get the patches
merged.

Thanks,
								Pavel

> [1] https://www.spinics.net/lists/linux-fsdevel/msg125241.html
> [2] https://www.spinics.net/lists/linux-fsdevel/msg126499.html

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  parent reply	other threads:[~2018-06-08 15:25 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 [this message]
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
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=20180608152557.GB11958@amd \
    --to=pavel@ucw.cz \
    --cc=anatoly.trosinenko@gmail.com \
    --cc=ernesto.mnd.fernandez@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).