RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When exiting the mdflush command, there is a python traceback present:

[root@localhost tools]# ./mdflush
Tracing md flush requests... Hit Ctrl-C to end.
TIME     PID    COMM             DEVICE
15:09:47 8115   dd               md0
15:09:54 8119   dd               md0
15:10:00 8123   dd               md0
15:10:07 8127   dd               md0
15:10:13 8131   dd               md0
15:10:20 8135   dd               md0
15:10:26 8139   dd               md0
^CTraceback (most recent call last):
  File "./mdflush", line 81, in <module>
    b.perf_buffer_poll()
  File "/usr/lib/python3.6/site-packages/bcc/__init__.py", line 1216, in perf_buffer_poll
    lib.perf_reader_poll(len(readers), readers, timeout)
KeyboardInterrupt

Version-Release number of selected component (if applicable):

kernel-4.18.0-48.el8.x86_64
bcc-0.7.0-3.el8.x86_64
bcc-tools-0.7.0-3.el8.x86_64

Steps to Reproduce:

Install bcc and bcc-tools
Execute mdflush
Use ctrl-c to exit

Actual results:

Traceback is reported

Expected results:

Ctrl-c exit should be smooth as in biotop or bitesize

Multiple tools do not properly catch the keyboard interrupt and it's not very clean indeed. But let's stick to one bz for this.

*** This bug has been marked as a duplicate of bug 1658369 ***

*** This bug has been marked as a duplicate of bug 1658692 ***

Sorry, I marked this as a duplicate of the wrong bz.