RE: [PATCH 9/24] make atomic_read() behave consistently on ia64
From: "Luck, Tony" <tony.luck@intel.com>
Date: 2007-08-10 22:59:59
Also in:
linux-arch, lkml
Possibly related (same subject, not in this thread)
- 2007-08-10 · RE: [PATCH 9/24] make atomic_read() behave consistently on ia64 · "Luck, Tony" <tony.luck@intel.com>
- 2007-08-10 · Re: [PATCH 9/24] make atomic_read() behave consistently on ia64 · Chris Snook <hidden>
- 2007-08-09 · RE: [PATCH 9/24] make atomic_read() behave consistently on ia64 · "Luck, Tony" <tony.luck@intel.com>
- 2007-08-09 · [PATCH 9/24] make atomic_read() behave consistently on ia64 · Chris Snook <hidden>
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