public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Andy Isaacson <adi@hexapodia.org>
Cc: linux-kernel@vger.kernel.org, hch@lst.de
Subject: Re: [2.6.34 regression] utsname.domainname not set in x86_32 processes
Date: Tue, 20 Apr 2010 05:22:00 +0200	[thread overview]
Message-ID: <20100420032200.GA13131@lst.de> (raw)
In-Reply-To: <20100419192147.GP11130@hexapodia.org>

On Mon, Apr 19, 2010 at 12:21:47PM -0700, Andy Isaacson wrote:
> 2.6.34-rc4 uname(2) from a x86_32 process copies out 325 bytes rather
> than the 390 bytes that 2.6.31 copied out (and that userland expects):

Which means we're missing exactly the domainname field in new_utsname,
which differenciates it from the old utsname structure.  Looks like we
end up calling the old uname sscall instead of the new one for some
reason. 


      parent reply	other threads:[~2010-04-20  3:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 19:21 [2.6.34 regression] utsname.domainname not set in x86_32 processes Andy Isaacson
2010-04-19 21:46 ` Andy Isaacson
2010-04-20  3:22 ` Christoph Hellwig [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100420032200.GA13131@lst.de \
    --to=hch@lst.de \
    --cc=adi@hexapodia.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox