[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <617E1C2C70743745A92448908E030B2A0224C8D7@scsmsx411.amr.corp.intel.com>
Date: Fri, 10 Aug 2007 15:59:44 -0700
From: "Luck, Tony" <tony.luck@...el.com>
To: "Chris Snook" <csnook@...hat.com>
Cc: "Andreas Schwab" <schwab@...e.de>, <linux-kernel@...r.kernel.org>,
<linux-arch@...r.kernel.org>, <torvalds@...ux-foundation.org>,
<netdev@...r.kernel.org>, <akpm@...ux-foundation.org>,
<ak@...e.de>, <heiko.carstens@...ibm.com>, <davem@...emloft.net>,
<schwidefsky@...ibm.com>, <wensong@...ux-vs.org>,
<horms@...ge.net.au>, <wjiang@...ilience.com>,
<cfriesen@...tel.com>, <zlynx@....org>, <rpjday@...dspring.com>,
<jesper.juhl@...il.com>
Subject: RE: [PATCH 9/24] make atomic_read() behave consistently on ia64
> Possibly. Either that or we've uncovered some latent bugs. Maybe a
> combination of the two. Can you list those 19 changes so we can
evaluate them?
Here are the functions in which they occur in the object file. You
may have to chase down some inlining to find the function that
actually uses atomic_*().
freeque
do_msgrcv
sk_free
sock_wfree
sock_rfree
sock_kmalloc
sock_kfree_s
sock_setsockopt
skb_release_data
__sk_stream_mem_reclaim
sk_tream_mem_schedule
sk_stream_rfree
sk_attach_filter
ip_frag_destroy * 2
ip_frag_queue * 2
ip_frag_reasm * 2
-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists