Kernel stack trace to source code lines

Given a kernel stack trace as below, how do you determine the specific line of code where the issue occurred?

kernel:  [<ffffffff80009a14>] __link_path_walk+0x173/0xfb9kernel:  [<ffffffff8002cbec>] mntput_no_expire+0x19/0x89kernel:  [<ffffffff8000eb94>] link_path_walk+0xa6/0xb2kernel:  [<ffffffff80063c4f>] __mutex_lock_slowpath+0x60/0x9bkernel:  [<ffffffff800238de>] __path_lookup_intent_open+0x56/0x97kernel:  [<ffffffff80063c99>] .text.lock.mutex+0xf/0x14kernel:  [<ffffffff8001b222>] open_namei+0xea/0x712kernel:  [<ffffffff8006723e>] do_page_fault+0x4fe/0x874kernel:  [<ffffffff80027660>] do_filp_open+0x1c/0x38kernel:  [<ffffffff8001a061>] do_sys_open+0x44/0xbekernel:  [<ffffffff8005d28d>] tracesys+0xd5/0xe0

While I have no trouble finding the function call -- but translating __link_path_walk plus an offset to an actual line number is the difficult part.

Assuming this is for a standard distribution-provided kernel for which I know the exact version and build number, what's the process for fetching the necessary metadata and doing the corresponding lookup?