From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <yuchao0@huawei.com>
Cc: Anant Thazhemadam <anant.thazhemadam@gmail.com>,
Chao Yu <chao@kernel.org>,
syzbot+ca9a785f8ac472085994@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] fs: f2fs: fix potential shift-out-of-bounds error in sanity_check_raw_super()
Date: Thu, 10 Dec 2020 09:14:08 -0800 [thread overview]
Message-ID: <X9JXYAqaTwdtMABE@google.com> (raw)
In-Reply-To: <e72ff237-9d9a-2dbe-6a31-65046db9ee64@huawei.com>
On 12/10, Chao Yu wrote:
> Jaegeuk,
>
> Could you please help to add signed-off of Anant manually in
>
> f2fs: fix shift-out-of-bounds in sanity_check_raw_super()
Done. Thank you guys. :)
>
> Thanks,
>
> On 2020/12/10 10:14, Anant Thazhemadam wrote:
> >
> > On 10/12/20 7:40 am, Chao Yu wrote:
> > > On 2020/12/10 10:00, Anant Thazhemadam wrote:
> > > >
> > > > On 10/12/20 7:16 am, Chao Yu wrote:
> > > > > Hi Anant,
> > > > >
> > > > > I've posted a patch a little earlier. :P
> > > > >
> > > > > https://lore.kernel.org/linux-f2fs-devel/20201209084936.31711-1-yuchao0@huawei.com/T/#u
> > > > >
> > > > Ah well, that's alright, especially considering that your patch looks better.
> > > > Glad that bug has been fixed nonetheless. :)
> > >
> > > Anyway, thanks a lot for taking time to fix f2fs bug. :)
> > >
> > > I prefer to add your Signed-off-by into "f2fs: fix shift-out-of-bounds
> > > in sanity_check_raw_super()" if you don't mind.
> > >
> > >
> >
> > Sure, I'd appreciate that. Thank you! :D
> >
> > Thanks,
> > Anant
> >
> > .
> >
prev parent reply other threads:[~2020-12-10 17:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 18:13 [PATCH] fs: f2fs: fix potential shift-out-of-bounds error in sanity_check_raw_super() Anant Thazhemadam
2020-12-10 1:46 ` [f2fs-dev] " Chao Yu
2020-12-10 2:00 ` Anant Thazhemadam
2020-12-10 2:10 ` Chao Yu
2020-12-10 2:14 ` Anant Thazhemadam
2020-12-10 5:57 ` Chao Yu
2020-12-10 17:14 ` Jaegeuk Kim [this message]
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=X9JXYAqaTwdtMABE@google.com \
--to=jaegeuk@kernel.org \
--cc=anant.thazhemadam@gmail.com \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+ca9a785f8ac472085994@syzkaller.appspotmail.com \
--cc=yuchao0@huawei.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