mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Josef Sipek <jsipek@cs.sunysb.edu>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	unionfs@filesystems.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc8-mm1
Date: Tue, 25 Sep 2007 13:39:27 -0400	[thread overview]
Message-ID: <20070925173927.GC352@filer.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <20070925102637.79e1dc75.randy.dunlap@oracle.com>

On Tue, Sep 25, 2007 at 10:26:37AM -0700, Randy Dunlap wrote:
> On Tue, 25 Sep 2007 01:46:25 -0700 Andrew Morton wrote:
> 
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc8/2.6.23-rc8-mm1/
> > 
> > - Various fixes against 2.6.23-rc7-mm1.
> > 
> > 
> >  git-unionfs.patch
> 
> in unionfs debug.c:
> 
> #if BITS_PER_LONG == 32
> #define POISONED_PTR		((void*) 0x5a5a5a5a)
> #elif BITS_PER_LONG == 64
> #define POISONED_PTR		((void*) 0x5a5a5a5a5a5a5a5a)
> #else
> #error Unknown BITS_PER_LONG value
> #endif /* BITS_PER_LONG != known */
> 
> 
> We try to keep all poison values in include/linux/poison.h so that
> when digging around for them, it's easier to locate the one in
> question.
 
Right. I didn't want to introduce this kind of ifdef, the 0x5a pattern is
also the same as POISON_INUSE. I guess, using the 32-bit poison value should
be good enough anyway.

> Also, on x86_64, the 64-bit version wants a L or UL suffix:
> 
> fs/unionfs/debug.c:96:30: warning: constant 0x5a5a5a5a5a5a5a5a is so big it is long
> fs/unionfs/debug.c:264:30: warning: constant 0x5a5a5a5a5a5a5a5a is so big it is long

Strange...I didn't get the warning when I compile tested; but it's valid.

Josef 'Jeff' Sipek.

-- 
Research, n.:
  Consider Columbus:
    He didn't know where he was going.
    When he got there he didn't know where he was.
    When he got back he didn't know where he had been.
    And he did it all on someone else's money.

  reply	other threads:[~2007-09-25 17:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-25  8:46 2.6.23-rc8-mm1 Andrew Morton
2007-09-25 10:39 ` 2.6.23-rc8-mm1 Kamalesh Babulal
2007-09-25 15:46   ` 2.6.23-rc8-mm1 Andrew Morton
2007-09-25 12:19 ` [-mm Patch] fs/udf/balloc.c: mark a variable as uninitialized_var() WANG Cong
2007-09-25 12:52 ` [-mm Patch] drivers/usb/misc/sisusbvga/sisusb.c: kill two unused variables WANG Cong
2007-09-25 12:53 ` 2.6.23-rc8-mm1 - drivers/net/ibm_newemac/mal - broken Kamalesh Babulal
2007-09-25 16:16   ` Andrew Morton
2007-09-25 13:46 ` 2.6.23-rc8-mm1 -- powerpc link failure Andy Whitcroft
2007-09-25 15:23   ` Jiri Kosina
2007-09-27 12:03     ` Andy Whitcroft
2007-09-27 12:13       ` Jiri Kosina
2007-09-27 17:13         ` Andrew Morton
2007-09-27 19:31           ` Sam Ravnborg
2007-09-27 22:13         ` Andrew Morton
2007-09-27 22:17           ` Jiri Kosina
2007-09-25 17:26 ` 2.6.23-rc8-mm1 Randy Dunlap
2007-09-25 17:39   ` Josef Sipek [this message]
2007-09-25 17:45   ` [PATCH 1/1] Unionfs: move poison #define into poison.h Josef 'Jeff' Sipek
2007-09-26  1:02     ` Josef 'Jeff' Sipek
2007-09-25 19:02 ` 2.6.23-rc8-mm1: unscrew UFS Alexey Dobriyan
2007-09-25 20:00 ` 2.6.23-rc8-mm1 - powerpc memory hotplug link failure Kamalesh Babulal
2007-09-25 22:01   ` Badari Pulavarty
2007-09-26  8:18     ` Kamalesh Babulal
2007-09-26  1:32   ` KAMEZAWA Hiroyuki
2007-09-26  1:48     ` KAMEZAWA Hiroyuki
2007-09-26  8:19       ` Kamalesh Babulal
2007-09-25 20:56 ` 2.6.23-rc8-mm1: drivers/kvm/ioapic.o build failure Mariusz Kozlowski
2007-09-26  9:00   ` [kvm-devel] " Avi Kivity
2007-09-26  9:14     ` Andrew Morton
2007-09-26  9:18       ` Avi Kivity
2007-09-25 22:05 ` 2.6.23-rc8-mm1 Badari Pulavarty
2007-09-26 12:28   ` 2.6.23-rc8-mm1 Andy Whitcroft
2007-09-25 22:23 ` 2.6.23-rc8-mm1 : wgt634u.c trem
2007-09-26  7:51 ` black screen after kill X [Was: 2.6.23-rc8-mm1] Jiri Slaby

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=20070925173927.GC352@filer.fsl.cs.sunysb.edu \
    --to=jsipek@cs.sunysb.edu \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=unionfs@filesystems.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

all inboxes | Powered by JetHome®