Re: pf: incorrect IPL in pool_init()

2017-01-11 Thread Alexander Bluhm
On Wed, Jan 11, 2017 at 07:33:49PM +0100, Martin Pieuchot wrote: > After discussing the issue with bluhm@ a better solution would be to > unlink the state key before passing the mbuf to the driver. This way > we would respect the contract that PF data structures are only accessed > at IPL_SOFTNET.

Re: pf: incorrect IPL in pool_init()

2017-01-11 Thread Mark Patruck
Running >2 hours with your patch now and everything's fine. As this is the longest splassert error free time frame in the last 24 hours, i'd say -> fixed. Thanks, -Mark On Wed, Jan 11, 2017 at 07:33:49PM +0100, Martin Pieuchot wrote: > On 11/01/17(Wed) 18:27, Martin Pieuchot wrote: > > M

Re: pf: incorrect IPL in pool_init()

2017-01-11 Thread Mike Belopuhov
On 11 January 2017 at 19:33, Martin Pieuchot wrote: > On 11/01/17(Wed) 18:27, Martin Pieuchot wrote: >> Mark Patruck reported the following assertion: >> >> splassert: pool_put: want 5 have 7 >> Starting stack trace... >> pool_put() at pool_put+0x4e >> pf_pkt_unlink_state_k

Re: pf: incorrect IPL in pool_init()

2017-01-11 Thread Martin Pieuchot
On 11/01/17(Wed) 18:27, Martin Pieuchot wrote: > Mark Patruck reported the following assertion: > > splassert: pool_put: want 5 have 7 > Starting stack trace... > pool_put() at pool_put+0x4e > pf_pkt_unlink_state_key() at pf_pkt_unlink_state_key+0x15 > m_free() at m_

pf: incorrect IPL in pool_init()

2017-01-11 Thread Martin Pieuchot
Mark Patruck reported the following assertion: splassert: pool_put: want 5 have 7 Starting stack trace... pool_put() at pool_put+0x4e pf_pkt_unlink_state_key() at pf_pkt_unlink_state_key+0x15 m_free() at m_free+0xa0 m_freem() at m_freem+0x19