Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: =?ISO-8859-1?Q?=C1ngel?= <angel@16bits.net>
Newsgroups: gnu.bash.bug
Subject: Re: Seg fault on "echo ~nosuchuser"
Date: Tue, 02 Jun 2020 01:58:32 +0200
Lines: 18
Approved: bug-bash@gnu.org
Message-ID: <mailman.962.1591055923.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>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
X-Trace: usenet.stanford.edu 1591055924 6947 209.51.188.17 (1 Jun 2020 23:58:44 GMT)
X-Complaints-To: action@cs.stanford.edu
To: bug-bash@gnu.org
Envelope-to: bug-bash@gnu.org
In-Reply-To: <6e7b8282-c41a-15b8-0dbf-9f811f6c3eee@case.edu>
Received-SPF: pass client-ip=199.195.249.9; envelope-from=angel@16bits.net; helo=mailer.hiddenmail.net
X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/01 19:58:38
X-ACL-Warn: Detected OS   = Linux 3.11 and newer [fuzzy]
X-Spam_score_int: -18
X-Spam_score: -1.9
X-Spam_bar: -
X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-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: <1591055912.1057.9.camel@16bits.net>
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>
Xref: csiph.com gnu.bash.bug:16348

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.
>=20
> Thanks for your help verifying this.
>=20
> Chet

You mean that with systemd getpwnam() crashes if using a malloc() that
returns addresses not 16-byte aligned?

Cornercase, surely, but it seems like a bug in whatever is assuming such
alignment. That's not even pointer-size alignment.

Cheers