summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorrrs <rrs@FreeBSD.org>2015-02-12 13:31:08 +0000
committerrrs <rrs@FreeBSD.org>2015-02-12 13:31:08 +0000
commite878a76f4638727fc513af3de11e376c4e667163 (patch)
tree70980ca030a67d8cfb1a4dfb933357e40a13462e /lib
parenta4c9135bbff0220420fee361cf7b4c00edae7abe (diff)
downloadFreeBSD-src-e878a76f4638727fc513af3de11e376c4e667163.zip
FreeBSD-src-e878a76f4638727fc513af3de11e376c4e667163.tar.gz
This fixes a bug I in-advertantly inserted when I updated the callout
code in my last commit. The cc_exec_next is used to track the next when a direct call is being made from callout. It is *never* used in the in-direct method. When macro-izing I made it so that it would separate out direct/vs/non-direct. This is incorrect and can cause panics as Peter Holm has found for me (Thanks so much Peter for all your help in this). What this change does is restore that behavior but also get rid of the cc_next from the array and instead make it be part of the base callout structure. This way no one else will get confused since we will never use it for non-direct. Reviewed by: Peter Holm and more importantly tested by him ;-) MFC after: 3 days. Sponsored by: Netflix Inc.
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud