diff options
author | danborkmann@iogearbox.net <danborkmann@iogearbox.net> | 2012-08-10 22:48:54 +0000 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2012-08-12 13:42:17 -0700 |
commit | 7f5c3e3a80e6654cf48dfba7cf94f88c6b505467 (patch) | |
tree | 6a0c9ee28e2ebb6a8831d9839ad5758bc584c919 /README | |
parent | 3a7f8c34fefb109903af9a0fac6d0d05f93335c5 (diff) | |
download | linux-7f5c3e3a80e6654cf48dfba7cf94f88c6b505467.tar.bz2 |
af_packet: remove BUG statement in tpacket_destruct_skb
Here's a quote of the comment about the BUG macro from asm-generic/bug.h:
Don't use BUG() or BUG_ON() unless there's really no way out; one
example might be detecting data structure corruption in the middle
of an operation that can't be backed out of. If the (sub)system
can somehow continue operating, perhaps with reduced functionality,
it's probably not BUG-worthy.
If you're tempted to BUG(), think again: is completely giving up
really the *only* solution? There are usually better options, where
users don't need to reboot ASAP and can mostly shut down cleanly.
In our case, the status flag of a ring buffer slot is managed from both sides,
the kernel space and the user space. This means that even though the kernel
side might work as expected, the user space screws up and changes this flag
right between the send(2) is triggered when the flag is changed to
TP_STATUS_SENDING and a given skb is destructed after some time. Then, this
will hit the BUG macro. As David suggested, the best solution is to simply
remove this statement since it cannot be used for kernel side internal
consistency checks. I've tested it and the system still behaves /stable/ in
this case, so in accordance with the above comment, we should rather remove it.
Signed-off-by: Daniel Borkmann <daniel.borkmann@tik.ee.ethz.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions