Thread (95 messages) 95 messages, 4 authors, 2008-10-01

Re: xfrm_state locking regression...

From: Timo Teräs <hidden>
Date: 2008-09-24 05:46:14

Herbert Xu wrote:
On Wed, Sep 24, 2008 at 08:14:11AM +0300, Timo Teräs wrote:
quoted
Only comment is that there really should be struct for the
shared stuff. Otherwise it's bound to break at some point.
That's why I put comments there.  If people change it without
reading the comments, they'll ignore the struct too :)
Well, it's also because in the dump routine the entries
are cast to xfrm_state, even if it was a walker entry. This
is just wrong, though it probably works since only the specific
entries are used.

There should be some intermediate struct which we use to 
iterate in dumping routing, check if it was iterator/real entry
(can be still based on the state thing). And only after that
cast to struct xfrm_state. It would make the dumping routine
more readable.

Cheers,
  Timo
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help