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:

Please backport asap the following commit:

https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b024fb


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

dovecot-2.3.8-2.el8_2.2.x86_64


How reproducible:

Very often on customer's installation

Do you have reproducer for this?

Did the customer verify that the commit fixes the issue for him?

I have no reproducer.

I'm currently building a test package for the customer to confirm.
Anyway from the coredump I have, it's obvious the customer is hitting what is described here and the commit would fix this.

Upstream did have to fix it, so the bug is there. It may be obvious that this is the commit that is related to it, but my point is that especially without reproducer, we should be sure that the commit is enough to fix the issue. Let me know when you have any feedback from customer.

I've got the confirmation that the commit a668d767a710ca18ab6e7177d8e8be22a6b024fb fixes the crash.

The customer has another unrelated crash that I will investigate tomorrow.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: dovecot security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:1887