Does your code wait for both clients to unwind so that it merges the two
replies before it unwinds itself? You typically would need to keep a call
count (# of winds) and wait for that many _cbk invocations before calling
STACK_UNWIND yourself.
If you are not waiting for both replies, it is possibl
call frames and stacks are re-used from a mem-pool. So pointers might
repeat. Can you describe your use case a little more in detail, just to be
sure?
On Mon, Jul 28, 2014 at 11:27 AM, Matthew McKeen
wrote:
> Is it true that different fops will always have a different frame
> (i.e. different fr
Is it true that different fops will always have a different frame
(i.e. different frame pointer) as seen in the translator stack? I've
always thought this to be true, but it seems that with the
release-3.6.0 branch the two quick getxattr syscalls that the getfattr
cli command calls share the same
