* why XOR ext2_set_bit?
@ 2001-03-14 22:28 Sébastien Côté
2001-03-15 8:30 ` Geert Uytterhoeven
0 siblings, 1 reply; 2+ messages in thread
From: Sébastien Côté @ 2001-03-14 22:28 UTC (permalink / raw)
To: linuxppc-dev
Hi,
I just had a problem writing to a file on a ext2 filesystem with my port
of kernel 2.4 on powerpc (G4) running in little-endian. When the
function ext2_set_bit was called by ext2_new_block, it returned
something so I got the warning :
"ext2_new_block bit already set for block 161"
and I was stuck in an infinite loop. I found the definition for the
function in include/asm-ppc/bitops.h as follow:
#define ext2_set_bit(nr, addr) test_and_set_bit((nr) ^ 0x18, addr)
Now my question: Why is "nr" XORed with 0x18 ??? I tried to do this
function on paper and with this XOR, they were always trying to change
the wrong bit. Now, since nobody's been reporting this problem before,
I guess this XOR is ok but I'd really like to understand it's utility to
correct things on my side (for now, I just removed it and everything
appears to be fine).
Could someone give me an explanation?
Thanks,
Sébastien Côté
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: why XOR ext2_set_bit?
2001-03-14 22:28 why XOR ext2_set_bit? Sébastien Côté
@ 2001-03-15 8:30 ` Geert Uytterhoeven
0 siblings, 0 replies; 2+ messages in thread
From: Geert Uytterhoeven @ 2001-03-15 8:30 UTC (permalink / raw)
To: Sébastien Côté; +Cc: linuxppc-dev
On Wed, 14 Mar 2001, Sébastien Côté wrote:
>
> I just had a problem writing to a file on a ext2 filesystem with my port
> of kernel 2.4 on powerpc (G4) running in little-endian. When the
> function ext2_set_bit was called by ext2_new_block, it returned
> something so I got the warning :
>
> "ext2_new_block bit already set for block 161"
>
> and I was stuck in an infinite loop. I found the definition for the
> function in include/asm-ppc/bitops.h as follow:
>
> #define ext2_set_bit(nr, addr) test_and_set_bit((nr) ^ 0x18, addr)
>
> Now my question: Why is "nr" XORed with 0x18 ??? I tried to do this
> function on paper and with this XOR, they were always trying to change
> the wrong bit. Now, since nobody's been reporting this problem before,
> I guess this XOR is ok but I'd really like to understand it's utility to
> correct things on my side (for now, I just removed it and everything
> appears to be fine).
>
> Could someone give me an explanation?
Ext2 metadata is little endian. The XOR converts from big endian to little
endian bit numbering inside a 32-bit word in native format.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-03-15 8:30 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-03-14 22:28 why XOR ext2_set_bit? Sébastien Côté
2001-03-15 8:30 ` Geert Uytterhoeven
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).