netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jslaby@suse.cz>
To: Julian Anastasov <ja@ssi.bg>,
	Smart Weblications GmbH - Florian Wiessner
	<f.wiessner@smart-weblications.de>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
	netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	stable@vger.kernel.org, Simon Horman <horms@verge.net.au>,
	lvs-devel@vger.kernel.org
Subject: Re: 3.12.33 - BUG xfrm_selector_match+0x25/0x2f6
Date: Tue, 06 Jan 2015 13:56:56 +0100	[thread overview]
Message-ID: <54ABDB98.9060504@suse.cz> (raw)
In-Reply-To: <alpine.LFD.2.11.1412132211260.3229@ja.home.ssi.bg>

On 12/13/2014, 09:19 PM, Julian Anastasov wrote:
> 
> 	Hello,
> 
> On Thu, 11 Dec 2014, Smart Weblications GmbH - Florian Wiessner wrote:
> 
>>>> [  512.485323] CPU: 4 PID: 28142 Comm: vsftpd Not tainted 3.12.33 #5
>>>
>>> 	Above "#5" is same as previous oops. It means kernel
>>> is not updated. Or you updated only the IPVS modules after
>>> applying the both patches?
>>
>> I did it with make-kpkg --initrd linux_image which only rebuilt the modules,
>> correct. I can retry with make clean before building the package
> 
> 	I just tested PASV and PORT with 3.12.33 including
> both patches (seq adj fix + ip_route_me_harder fix) and do not
> see any crashes in nf_ct_seqadj_set. If you still have problem
> with FTP send me more info offlist.
> 
>>> 	You can also try without FTP tests to see if there
>>> are oopses in xfrm, so that we can close this topic and then
>>> to continue for the FTP problem on IPVS lists without
>>> bothering non-IPVS people.
>>>
>>
>> yeah, it seems that the xfrm issue is away.
> 
> 	Thanks for the confirmation!

Great! Thanks for tracking it down.

So what should be done to fix the issue in stable 3.12? Are those
patches needed in the upstream kernel too? In that case I suppose it
will propagate to me through upstream. Otherwise, could you send "3.12
only" patches to stable@ so that I can apply them?

thanks,
-- 
js
suse labs

  reply	other threads:[~2015-01-06 12:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 14:55 3.12.33 - BUG xfrm_selector_match+0x25/0x2f6 Smart Weblications GmbH - Florian Wiessner
2014-12-04  7:56 ` Steffen Klassert
2014-12-04 16:36   ` Smart Weblications GmbH - Florian Wiessner
2014-12-05 10:43     ` Steffen Klassert
2014-12-04 23:15   ` Julian Anastasov
2014-12-05  2:23     ` Smart Weblications GmbH - Florian Wiessner
2014-12-05  9:55       ` Julian Anastasov
2014-12-05 13:55         ` Smart Weblications GmbH - Florian Wiessner
2014-12-05 21:32           ` Julian Anastasov
2014-12-07 22:04             ` Smart Weblications GmbH - Florian Wiessner
2014-12-07 18:27           ` Julian Anastasov
2014-12-08 11:19             ` Smart Weblications GmbH - Florian Wiessner
2014-12-08 20:40               ` Julian Anastasov
2014-12-09 10:23                 ` Smart Weblications GmbH - Florian Wiessner
2014-12-10 21:41                   ` Julian Anastasov
2014-12-11 14:04                     ` Smart Weblications GmbH - Florian Wiessner
2014-12-13 20:19                       ` Julian Anastasov
2015-01-06 12:56                         ` Jiri Slaby [this message]
2015-01-06 20:46                           ` Julian Anastasov
2014-12-05 10:53     ` Steffen Klassert
2014-12-04  9:44 ` Jiri Slaby
2014-12-04 16:40   ` Smart Weblications GmbH - Florian Wiessner

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=54ABDB98.9060504@suse.cz \
    --to=jslaby@suse.cz \
    --cc=f.wiessner@smart-weblications.de \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lvs-devel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=steffen.klassert@secunet.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).