Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Chet Ramey <chet.ramey@case.edu>
Newsgroups: gnu.bash.bug
Subject: Re: Seg fault on "echo ~nosuchuser"
Date: Tue, 2 Jun 2020 08:56:57 -0400
Organization: ITS, Case Western Reserve University
Lines: 34
Approved: bug-bash@gnu.org
Message-ID: <mailman.974.1591102629.2541.bug-bash@gnu.org>
References: <CAAHpriPmaDcTYQLkyGqA6fM_AyVQkfN_f7p1qzkoqj-2-G1xBA@mail.gmail.com> <0c4fcd5b-3ac6-ea8c-e537-b4bfc9215de4@case.edu> <CAAHpriN1QYMAHOqAKHr=yOJF-0tiiKDnzqawXh+DYxP7=wrDiA@mail.gmail.com> <81924c39-6cde-617b-c5a7-5e3605e0c3b8@case.edu> <CAAHpriP=25drsYLtrOti2-fYEFjNpm76sAVskiVxUdthEB0vjw@mail.gmail.com> <6e7b8282-c41a-15b8-0dbf-9f811f6c3eee@case.edu> <1591055912.1057.9.camel@16bits.net> <d816520f-b4b2-aa5c-e4bb-bfd1b94714d3@case.edu>
Reply-To: chet.ramey@case.edu
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Cc: chet.ramey@case.edu
To: =?UTF-8?B?w4FuZ2Vs?= <angel@16bits.net>, bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
Autocrypt: addr=chet.ramey@case.edu; prefer-encrypt=mutual; keydata= mQGiBEEOsGwRBACFa0A1oa71HSZLWxAx0svXzhOZNQZOzqHmSuGOG92jIpQpr8DpvgRh40Yp AwdcXb8QG1J5yGAKeevNE1zCFaA725vGSdHUyypHouV0xoWwukYO6qlyyX+2BZU+okBUqoWQ koWxiYaCSfzB2Ln7pmdys1fJhcgBKf3VjWCjd2XJTwCgoFJOwyBFJdugjfwjSoRSwDOIMf0D /iQKqlWhIO1LGpMrGX0il0/x4zj0NAcSwAk7LaPZbN4UPjn5pqGEHBlf1+xDDQCkAoZ/VqES GZragl4VqJfxBr29Ag0UDvNbUbXoxQsARdero1M8GiAIRc50hj7HXFoERwenbNDJL86GPLAQ OTGOCa4W2o29nFfFjQrsrrYHzVtyA/9oyKvTeEMJ7NA3VJdWcmn7gOu0FxEmSNhSoV1T4vP2 1Wf7f5niCCRKQLNyUy0wEApQi4tSysdz+AbgAc0b/bHYVzIf2uO2lIEZQNNt+3g2bmXgloWm W5fsm/di50Gm1l1Na63d3RZ00SeFQos6WEwLUHEB0yp6KXluXLLIZitEJLQwQ2hldCBSYW1l eSAoQ2FzZSBzdGFuZGFyZCkgPGNoZXQucmFtZXlAY2FzZS5lZHU+iF8EExECAB8FAkPi19EC GwMHCwkIBwMCAQMVAgMDFgIBAh4BAheAAAoJELtYafBk6nSrelkAn31Gsuib7GcCZHbv5L5t VKYR9LklAJ4hzUHKA49Z0QXR+qCb80osIcmPSbkBDQRBDrBvEAQAkK6TAOKBEM+EC4j6V/7o /riVZqcgU5cid2qG9TXdwNtD9a3kvA/ObZBO93sX59wc6Bnwo4VJxsOmMlpGrAjJsxNwg3QH akEtf8LXRbVpj5xStdmBdQZUhIQyalo/2/TZq5OijtddUQcL5cs70hTv/FpT3wUvr2Xr8rjF 41IFEz8AAwcD/A0CZEGlzIrT5WCBnl6xBog/8vKiUCbarByat3d1mL6DbizvKNXQRTC9E/vE dENAWCQCjr75Bu55xT8n3SXGtWdDC5xmZ/P3OBYORP8yl8H8I1FIosWOFirbIeYdZPq8SPD1 HL+EXo9zSiHVrrZRJ19ooCKKbSdXHFCY+aJG+0KZiEkEGBECAAkFAkEOsG8CGwwACgkQu1hp 8GTqdKvjcACfZlkVCDwaz/NTO9cy3t69oWpVPNwAnRwe0qk/WL/gfhH346xh5B3HFbFN
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.8.1
In-Reply-To: <1591055912.1057.9.camel@16bits.net>
Content-Language: en-US
Received-SPF: pass client-ip=129.22.103.226; envelope-from=chet.ramey@case.edu; helo=mpv1-2015.case.edu
X-Spam_score_int: -43
X-Spam_score: -4.4
X-Spam_bar: ----
X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN
X-Spam_action: no action
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <d816520f-b4b2-aa5c-e4bb-bfd1b94714d3@case.edu>
X-Mailman-Original-References: <CAAHpriPmaDcTYQLkyGqA6fM_AyVQkfN_f7p1qzkoqj-2-G1xBA@mail.gmail.com> <0c4fcd5b-3ac6-ea8c-e537-b4bfc9215de4@case.edu> <CAAHpriN1QYMAHOqAKHr=yOJF-0tiiKDnzqawXh+DYxP7=wrDiA@mail.gmail.com> <81924c39-6cde-617b-c5a7-5e3605e0c3b8@case.edu> <CAAHpriP=25drsYLtrOti2-fYEFjNpm76sAVskiVxUdthEB0vjw@mail.gmail.com> <6e7b8282-c41a-15b8-0dbf-9f811f6c3eee@case.edu> <1591055912.1057.9.camel@16bits.net>
Xref: csiph.com gnu.bash.bug:16351

On 6/1/20 7:58 PM, Ángel wrote:
> On 2020-06-01 at 15:12 -0400, Chet Ramey wrote:
>> I finally found a case where 16-byte alignment for memory returned by
>> malloc() is required. But it's only on Linux systems that use systemd.
>> I bet it's trying to marshal arguments for IPC and uses instructions
>> that require 16-byte alignment.
>>
>> Thanks for your help verifying this.
>>
>> Chet
> 
> You mean that with systemd getpwnam() crashes if using a malloc() that
> returns addresses not 16-byte aligned?

Yes, that's what I mean. The only significant change between the bash
version that worked and the one(s) that did not is making the memory
the bash malloc returns 16-byte aligned.

Other systems not using glibc or systemd could not reproduce the issue.

> Cornercase, surely, but it seems like a bug in whatever is assuming such
> alignment. That's not even pointer-size alignment.

If systemd or its support libraries are using copy instructions that
require 16-byte alignment, though it's not documented, it's arguably not
a bug.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/