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.
Bug 2181974 - In RHEL 9 /usr/bin/which fails for long path
Summary: In RHEL 9 /usr/bin/which fails for long path
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: which
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 9.3
Assignee: Than Ngo
QA Contact: CS System Management SST QE
Šárka Jana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-27 06:46 UTC by Pradeep Jagtap
Modified: 2023-11-07 11:17 UTC (History)
1 user (show)

Fixed In Version: which-2.21-29.el9
Doc Type: Bug Fix
Doc Text:
.The `which` command no longer fails for a long path Previously, when you executed the `which` command in a directory with a path longer than 256 characters, the command failed with the `Can't get current working directory` error message. With this fix, the `which` command now uses the `PATH_MAX` value for the path length limit. As a result, the command no longer fails.
Clone Of:
Environment:
Last Closed: 2023-11-07 08:51:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-153132 0 None None None 2023-03-27 06:49:04 UTC
Red Hat Issue Tracker RHELPLAN-153133 0 None None None 2023-03-27 06:49:07 UTC
Red Hat Product Errata RHBA-2023:6599 0 None None None 2023-11-07 08:51:25 UTC

Description Pradeep Jagtap 2023-03-27 06:46:19 UTC
Description of problem:
=======================
/usr/bin/which fails for long path

Version-Release number of selected component (if applicable):
which-2.21-28.el9.x86_64

How reproducible:
====================
Steps to Reproduce:
-------------------
1. Create Directory with long path
      # mkdir -p /tmp/1111111111222222222233333333334444444444555555555566666666667777777777888888888899999999990000000000/1111111111222222222233333333334444444444555555555566666666667777777777888888888899999999990000000000/11111111112222222222333333333344444444445555555555

2. Change directory to the created one
     # cd !$

3. Execute which command 
     # which cd

Actual results:
=================
Fails with error:
Can't get current working directory

Expected results:
===================
Should show below results
$ which cd
/usr/bin/cd


Additional info:
=================
In RHEL 7,8 and 9)
-------------------
The buffer is 256 in which.c

static char home[256];
static char cwd[256];
  static char result[256];

Comment 11 errata-xmlrpc 2023-11-07 08:51:24 UTC
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 (which bug fix and enhancement 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/RHBA-2023:6599


Note You need to log in before you can comment on or make changes to this bug.