From: Sasha Levin <levinsasha928@gmail.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
David Miller <davem@davemloft.net>,
lauro.venancio@openbossa.org, aloisio.almeida@openbossa.org,
Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: net: nfc: BUG and panic in accept() on 3.5-rc2
Date: Mon, 11 Jun 2012 18:56:50 +0200 [thread overview]
Message-ID: <1339433810.4999.65.camel@lappy> (raw)
In-Reply-To: <20120611152007.GZ22557@sortiz-mobl>
On Mon, 2012-06-11 at 17:20 +0200, Samuel Ortiz wrote:
> On Mon, Jun 11, 2012 at 04:59:38PM +0200, Eric Dumazet wrote:
> > On Mon, 2012-06-11 at 16:57 +0200, Samuel Ortiz wrote:
> > > Hi Eric,
> > >
> > > On Mon, Jun 11, 2012 at 04:41:33PM +0200, Eric Dumazet wrote:
> > > > On Mon, 2012-06-11 at 16:41 +0200, Samuel Ortiz wrote:
> > > > > Hi Sasha,
> > > > >
> > > > > On Mon, Jun 11, 2012 at 04:00:41PM +0200, Sasha Levin wrote:
> > > > > > Hi all,
> > > > > >
> > > > > > I've stumbled on the following while fuzzing with trinity inside a KVM tools guest, running on 3.5-rc2:
> > > > > >
> > > > > Thanks for the report, it could be worth adding this one to
> > > > > bugzilla.kernel.org.
> > > > >
> > > > > What's trinity ?
> > > > > Also, if this one is reproducible, would you mind sharing some details about
> > > > > how we could reproduce it ?
> > > >
> > > > Well, bugfix should be trivial enough ;)
> > > Yep, I looked at the code only after looking at Sasha's report.
> > >
> > > Thanks for the patch, do you mind if I add your SOB to it ?
> >
> > I would prefer making sure it fixes the bug first ;)
> Sure, although your patch makes sense regardless of that :)
> I'll still wait for Sasha to confirm that it fixes his crash.
I don't have a direct way of reproducing it, but I've put it in the test
vm and the fuzzer is running, I'll let you know tomorrow if it happened
again.
next prev parent reply other threads:[~2012-06-11 16:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 14:00 net: nfc: BUG and panic in accept() on 3.5-rc2 Sasha Levin
2012-06-11 14:41 ` Samuel Ortiz
2012-06-11 14:41 ` Eric Dumazet
2012-06-11 14:50 ` Sasha Levin
2012-06-11 14:58 ` Eric Dumazet
2012-06-11 16:55 ` Sasha Levin
2012-06-11 14:57 ` Samuel Ortiz
2012-06-11 14:59 ` Eric Dumazet
2012-06-11 15:20 ` Samuel Ortiz
2012-06-11 16:56 ` Sasha Levin [this message]
2012-06-11 17:25 ` Dave Jones
2012-06-11 19:49 ` Samuel Ortiz
2012-06-25 15:04 ` Sasha Levin
2012-06-25 15:53 ` [PATCH] net: nfc: fix panic in accept() Eric Dumazet
2012-06-25 17:15 ` Samuel Ortiz
2012-06-28 12:11 ` Sasha Levin
2012-06-28 12:56 ` Samuel Ortiz
2012-06-28 13:42 ` John W. Linville
2012-06-11 15:05 ` net: nfc: BUG and panic in accept() on 3.5-rc2 Dave Jones
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=1339433810.4999.65.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=aloisio.almeida@openbossa.org \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=lauro.venancio@openbossa.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.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).