From: Randy Dunlap <rdunlap@infradead.org>
To: Joe Perches <joe@perches.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
Andrew Morton <akpm@linux-foundation.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Shigeru Yoshida <syoshida@redhat.com>
Cc: syzbot <syzbot+1631f09646bc214d2e76@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com, ntfs3@lists.linux.dev,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs/ntfs3: fix negative shift size in true_sectors_per_clst()
Date: Thu, 22 Sep 2022 18:14:45 -0700 [thread overview]
Message-ID: <d61b11b9-620e-698a-b826-22b2604a9234@infradead.org> (raw)
In-Reply-To: <34b60d0ed48e4384e82a29020702ee2471092fb1.camel@perches.com>
On 9/22/22 17:47, Joe Perches wrote:
> On Thu, 2022-09-22 at 17:38 -0700, Randy Dunlap wrote:
>> it appears that the NTFS3 maintainer is MIA again. :(
>
> (I've no affiliation with the NTFS3 maintainer or paragon)
>
> Perhaps the expectation of prioritized immediate turnaround is unrealistic.
>
> It's free. Be patient.
>
Yes Joe, I get that.
https://lore.kernel.org/all/da20d32b-5185-f40b-48b8-2986922d8b25@stargateuniverse.net/
--
~Randy
next prev parent reply other threads:[~2022-09-23 1:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 8:16 [syzbot] UBSAN: shift-out-of-bounds in ntfs_fill_super syzbot
2022-04-21 8:37 ` syzbot
2022-04-21 12:29 ` syzbot
2022-09-20 15:59 ` [PATCH] fs/ntfs3: fix negative shift size in true_sectors_per_clst() Tetsuo Handa
2022-09-23 0:38 ` Randy Dunlap
2022-09-23 0:47 ` Joe Perches
2022-09-23 1:14 ` Randy Dunlap [this message]
2022-09-23 9:59 ` Dan Carpenter
2022-09-23 1:25 ` Tetsuo Handa
2022-09-23 11:58 ` Aleksandr Nogikh
2022-09-23 14:35 ` Tetsuo Handa
2022-09-24 11:58 ` Aleksandr Nogikh
2022-09-24 12:03 ` Aleksandr Nogikh
2022-09-23 11:58 ` Konstantin Komarov
2022-09-23 16:07 ` Randy Dunlap
2022-09-30 16:34 ` Konstantin Komarov
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=d61b11b9-620e-698a-b826-22b2604a9234@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=joe@perches.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=syoshida@redhat.com \
--cc=syzbot+1631f09646bc214d2e76@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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).