Bug 52481 - Occasional NULL pointer dereference during ftp networking since 3.7
Summary: Occasional NULL pointer dereference during ftp networking since 3.7
Status: RESOLVED OBSOLETE
Alias: None
Product: Networking
Classification: Unclassified
Component: IPV4 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Stephen Hemminger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-08 14:29 UTC by Coacher
Modified: 2013-03-02 11:45 UTC (History)
0 users

See Also:
Kernel Version: 3.7.x
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
lspci -vvv (11.90 KB, text/plain)
2013-01-08 14:29 UTC, Coacher
Details

Description Coacher 2013-01-08 14:29:18 UTC
Created attachment 90771 [details]
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.
Comment 1 Coacher 2013-01-15 18:16:53 UTC
Another crash just happened during uploading 2MB file on ftp and again no traces in logs.

Here is a couple of photos:
https://docs.google.com/folder/d/0B9NAm8_0mptgUFpRM1NhREx5cTg/edit
Comment 2 Coacher 2013-03-02 11:45:31 UTC
Seems to be fixed in 3.8.0 kernel. I am running 3.8.0 for about a week now and this problem never reappeared. I'll close this bug for now and continue testing 3.8.0

Note You need to log in before you can comment on or make changes to this bug.