[lkml]   [2006]   [Feb]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [lock validator] inet6_destroy_sock(): soft-safe -> soft-unsafe lock dependency

* Herbert Xu <> wrote:

> On Wed, Feb 01, 2006 at 02:32:19PM +0100, Ingo Molnar wrote:
> >
> > update: with all of Herbert's fixes i havent gotten these yet - so maybe
> > the validator was not producing a false positive, but perhaps the
> > inet6_destroy_sock()->sk_dst_reset() thing was causing the messages?
> Maybe. But in that case shouldn't the validator show that code-path?

yeah, it should have. In any case, things are looking good so far with
your fixes. (Any suggestions wrt. how to trigger as many different
codepaths in the networking code as possible, to increase coverage of
locking scenarios mapped? I've tried LTP so far, and a few ad-hoc tests.
Perhaps there's some IP protocol tester i should try, which is known to
trigger lots of boundary conditions?)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-02-02 08:50    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean