From: Stephen Hemminger <shemminger@vyatta.com>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 52481] New: Occasional NULL pointer dereference during ftp networking since 3.7
Date: Thu, 10 Jan 2013 09:21:36 -0800 [thread overview]
Message-ID: <20130110092136.0a74f203@nehalam.linuxnetplumber.net> (raw)
Begin forwarded message:
Date: Tue, 8 Jan 2013 14:29:18 +0000 (UTC)
From: bugzilla-daemon@bugzilla.kernel.org
To: shemminger@linux-foundation.org
Subject: [Bug 52481] New: Occasional NULL pointer dereference during ftp networking since 3.7
https://bugzilla.kernel.org/show_bug.cgi?id=52481
Summary: Occasional NULL pointer dereference during ftp
networking since 3.7
Product: Networking
Version: 2.5
Kernel Version: 3.7.0
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: IPV4
AssignedTo: shemminger@linux-foundation.org
ReportedBy: itumaykin@gmail.com
Regression: Yes
Created an attachment (id=90771)
--> (https://bugzilla.kernel.org/attachment.cgi?id=90771)
lspci -vvv
I am experiencing occasional panics during ftp networking after installing
kernel 3.7.0.
I have vsftpd-3.0.2 up and running on port 21 with configuration not changed
for months, I use passive FTP with nf_conntrack_ftp helper. My distro is
Hardened Gentoo amd64 and I use not vanilla kernel, but with some Gentoo
specific and grsec specific patches.
Anyway, with kernel 3.5.4 I had no problems with my FTP at all, but with 3.7.0
there are random panics during or after FTP sessions. It happens more often
after sessions with lots of data transferred, but sometimes only `ls` is enough
to hang my machine.
The nature of these errors is unknown to me, but the issue is definetely within
the kernel as I tried to downgrade solely kernel back to 3.5.4 and everything
returned back to normal.
Also, I don't have traces of these panics in my logs, but I took photos of one
of such cases. Here are links to them:
https://docs.google.com/folder/d/0B9NAm8_0mptgU2RrMTZWX0NucUk/edit
I understand there is probably not enough info to investigate the source of
this issue, but I am ready to provide any additional info or do some testing.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
reply other threads:[~2013-01-10 17:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130110092136.0a74f203@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=netdev@vger.kernel.org \
/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).