From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
Jeff Mahoney <jeffm@suse.com>, Jan Kara <jack@suse.cz>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] reiserfs: update reiserfs_xattrs_initialized() condition
Date: Mon, 22 Mar 2021 16:43:01 +0100 [thread overview]
Message-ID: <20210322154301.GG31783@quack2.suse.cz> (raw)
In-Reply-To: <CAHk-=wjoa-F1mgQ8bFYhbyGCf+RP_WNrbciVqe42MYkjNjUMpg@mail.gmail.com>
On Sun 21-03-21 12:20:21, Linus Torvalds wrote:
> On Sun, Mar 21, 2021 at 7:37 AM Tetsuo Handa
> <penguin-kernel@i-love.sakura.ne.jp> wrote:
> >
> > syzbot is reporting NULL pointer dereference at reiserfs_security_init()
>
> Whee. Both of the mentioned commits go back over a decade.
>
> I guess I could just take this directly, but let's add Jeff Mahoney
> and Jan Kara to the participants in case they didn't see it on the
> fsdevel list. I think they might want to be kept in the loop.
>
> I'll forward the original in a separate email to them.
>
> Jeff/Jan - just let me know if I should just apply this as-is.
> Otherwise I'd expect it to (eventually) come in through Jan's random
> fs tree, which is how I think most of these things have come in ..
Thanks Linus. I've replied to Tetsuo's patch. Honestly, I've seen the patch
when Tetsuo sent it but reiserfs fuzzing bugs are not high on my priority
list so I forgot about it before I found time to understand what's going on
there. I think his patch is safe but I'm not sure it is a complete solution
so let's wait a bit what he has to say.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2021-03-22 15:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 9:32 general protection fault in reiserfs_security_init syzbot
2020-09-21 19:58 ` syzbot
2021-02-21 5:09 ` [PATCH] reiserfs: update reiserfs_xattrs_initialized() condition Tetsuo Handa
2021-03-05 6:31 ` [PATCH (resend)] " Tetsuo Handa
2021-03-15 0:44 ` Tetsuo Handa
2021-03-22 15:31 ` Jan Kara
2021-03-24 14:47 ` Tetsuo Handa
2021-03-24 15:20 ` Jeff Mahoney
2021-03-25 6:19 ` Tetsuo Handa
2021-03-25 15:36 ` Tetsuo Handa
2021-03-21 14:37 ` [PATCH] " Tetsuo Handa
2021-03-21 19:20 ` Linus Torvalds
2021-03-22 15:43 ` Jan Kara [this message]
2021-03-30 14:47 ` Tetsuo Handa
2021-03-30 14:51 ` Jeff Mahoney
2021-03-30 14:53 ` Jan Kara
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=20210322154301.GG31783@quack2.suse.cz \
--to=jack@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=jeffm@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.