Page MenuHomeFreeBSD

Since a fatal trap can happen at aribtrary times, don't panic when the completions are not in a consistent state.
ClosedPublic

Authored by imp on May 30 2019, 9:32 PM.
Tags
None
Referenced Files
F173580614: D20478.id58131.diff
Sat, Sep 26, 11:39 PM
F173567700: D20478.id58096.diff
Sat, Sep 26, 9:44 PM
F173563785: D20478.id58113.diff
Sat, Sep 26, 9:10 PM
F173561052: D20478.id58132.diff
Sat, Sep 26, 8:51 PM
F173560928: D20478.id58124.diff
Sat, Sep 26, 8:50 PM
F173539467: D20478.id58148.diff
Sat, Sep 26, 5:18 PM
F173536013: D20478.id58148.diff
Sat, Sep 26, 4:41 PM
Unknown Object (File)
Fri, Sep 25, 6:05 AM
Subscribers

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 24636
Build 23414: arc lint + arc unit

Event Timeline

jhb added a subscriber: jhb.

Just a few spelling nits: s/aribtrary/arbitrary/ in log, s/panicing/panicking/ (yes, it looks weird to me too, but adding the 'k' appears to be correct for adding -ing or -ed), s/sceduler/scheduler/, s/leading/leaving/. I still do double spaces at start of sentences in monospace fonts as well FWIW (and style(9) probably wants a blank line before the block comment).

I think your change probably makes sense though. We do similar hacks for lock assertions for similar reasons IIRC.

This revision is now accepted and ready to land.May 31 2019, 12:11 AM
markj added inline comments.
sys/dev/nvme/nvme_qpair.c
573

While here the \n can be removed from the kassert string.

sys/dev/nvme/nvme_qpair.c
573

gotcha

Try a little harder, add comments.

This revision now requires review to proceed.May 31 2019, 3:27 PM

Plug more holes with tips from kib, jhb and markj.

Remove now-obsolete comment.

imp marked an inline comment as done.May 31 2019, 9:06 PM
This revision was not accepted when it landed; it landed in state Needs Review.Jun 1 2019, 3:37 PM
This revision was automatically updated to reflect the committed changes.