[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200915051331.GA7980@Thinkpad>
Date: Tue, 15 Sep 2020 10:43:31 +0530
From: Anmol Karn <anmol.karan123@...il.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kernel-mentees@...ts.linuxfoundation.org,
syzbot+f7204dcf3df4bb4ce42c@...kaller.appspotmail.com,
Eric Dumazet <eric.dumazet@...il.com>,
Bjorn Andersson <bjorn.andersson@...aro.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>,
Eric Biggers <ebiggers@...gle.com>,
Necip Fazil Yildiran <necip@...gle.com>
Subject: Re: [Linux-kernel-mentees] [PATCH] idr: remove WARN_ON_ONCE() when
trying to check id
On Mon, Sep 14, 2020 at 08:26:55PM +0100, Matthew Wilcox wrote:
> On Tue, Sep 15, 2020 at 12:17:55AM +0530, Anmol Karn wrote:
> > On Mon, Sep 14, 2020 at 12:08:03PM +0100, Matthew Wilcox wrote:
> > > On Mon, Sep 14, 2020 at 12:47:24PM +0530, Anmol Karn wrote:
> > > > idr_get_next() gives WARN_ON_ONCE() when it gets (id > INT_MAX) true
> > > > and this happens when syzbot does fuzzing, and that warning is
> > > > expected, but WARN_ON_ONCE() is not required here and, cecking
> > > > the condition and returning NULL value would be suffice.
> > > >
> > > > Reference: commit b9959c7a347 ("filldir[64]: remove WARN_ON_ONCE() for bad directory entries")
> > > > Reported-and-tested-by: syzbot+f7204dcf3df4bb4ce42c@...kaller.appspotmail.com
> > > > Link: https://syzkaller.appspot.com/bug?extid=f7204dcf3df4bb4ce42c
> > > > Signed-off-by: Anmol Karn <anmol.karan123@...il.com>
> > >
> > > https://lore.kernel.org/netdev/20200605120037.17427-1-willy@infradead.org/
> >
> > Hello sir,
> >
> > I have looked into the patch, and it seems the problem is fixed to the root cause
> > in this patch, but not yet merged due to some backport issues, so, please ignore
> > this patch(sent by me), and please let me know if i can contribute to fixing this
> > bug's root cause.
>
> The root cause is that the network maintainers believe I have a far
> greater interest in the qrtr code than I actually do, and the maintainer
> of the qrtr code is not doing anything.
Hello sir,
I hope the patch will get merged soon.
also, i have tried a patch for this bug
Link: https://syzkaller.appspot.com/bug?extid=3b14b2ed9b3d06dcaa07
can you please guide me little how should i proceede with it, and
also syzbot tested it.
Thanks,
Anmol
Powered by blists - more mailing lists