Re: 2.6.23-rc3-mm1 -- drivers/ net/wireless/zd1211rw-mac80211/zd_mac.c:822: erro r: ‘IEEE80211_ERP_CHANGE_PREAMBLE ’ undeclared (first use in this function)

2007-08-26 Thread Ulrich Kunitz
Miles Lane wrote: > CC [M] drivers/net/wireless/zd1211rw-mac80211/zd_mac.o > drivers/net/wireless/zd1211rw-mac80211/zd_mac.c: In function > 'zd_op_erp_ie_changed': > drivers/net/wireless/zd1211rw-mac80211/zd_mac.c:822: error: > 'IEEE80211_ERP_CHANGE_PREAMBLE' undeclared (first use in this >

Re: 2.6.23-rc3-mm1 -- drivers/ net/wireless/zd1211rw-mac80211/zd_mac.c:822: erro r: ‘IEEE80211_ERP_CHANGE_PREAMBLE ’ undeclared (first use in this function)

2007-08-26 Thread Ulrich Kunitz
Miles Lane wrote: CC [M] drivers/net/wireless/zd1211rw-mac80211/zd_mac.o drivers/net/wireless/zd1211rw-mac80211/zd_mac.c: In function 'zd_op_erp_ie_changed': drivers/net/wireless/zd1211rw-mac80211/zd_mac.c:822: error: 'IEEE80211_ERP_CHANGE_PREAMBLE' undeclared (first use in this

Re: Is PIE randomization breaking klibc binaries?

2007-08-02 Thread Ulrich Kunitz
H. Peter Anvin wrote: > Yup... it should probably be pointed out the reason the old kernel > worked was nothing but pure dumb luck. This was a GNU ld change which > needed to be undone for klibc. It's unfortunate that stock x86-64 > binaries leave as little of a null pointer range as they

Re: Is PIE randomization breaking klibc binaries?

2007-08-02 Thread Ulrich Kunitz
Sergey Vlasov wrote: > On Wed, 25 Jul 2007 08:32:43 +0200 Ulrich Kunitz wrote: > > [...] > > Here is some output from objdump: > > > > $ objdump -x bin/sleep > > > > bin/sleep: file format elf64-x86-64 > > bin/sleep > > architecture:

Re: Is PIE randomization breaking klibc binaries?

2007-08-02 Thread Ulrich Kunitz
Sergey Vlasov wrote: On Wed, 25 Jul 2007 08:32:43 +0200 Ulrich Kunitz wrote: [...] Here is some output from objdump: $ objdump -x bin/sleep bin/sleep: file format elf64-x86-64 bin/sleep architecture: i386:x86-64, flags 0x0102: EXEC_P, D_PAGED start address

Re: Is PIE randomization breaking klibc binaries?

2007-08-02 Thread Ulrich Kunitz
H. Peter Anvin wrote: Yup... it should probably be pointed out the reason the old kernel worked was nothing but pure dumb luck. This was a GNU ld change which needed to be undone for klibc. It's unfortunate that stock x86-64 binaries leave as little of a null pointer range as they do,

Re: Is PIE randomization breaking klibc binaries?

2007-08-01 Thread Ulrich Kunitz
Jiri Kosina wrote: > On Tue, 31 Jul 2007, H. Peter Anvin wrote: > > > > So it seems to me that either it is something x86_64 specific or > > > initramfs-specific. Will try to reproduce it. > > My guess would be the former, rather than the latter. I haven't had a > > chance to reproduce it

Re: Is PIE randomization breaking klibc binaries?

2007-08-01 Thread Ulrich Kunitz
Jiri Kosina wrote: On Tue, 31 Jul 2007, H. Peter Anvin wrote: So it seems to me that either it is something x86_64 specific or initramfs-specific. Will try to reproduce it. My guess would be the former, rather than the latter. I haven't had a chance to reproduce it myself yet (I'm

Re: Is PIE randomization breaking klibc binaries?

2007-07-25 Thread Ulrich Kunitz
On 07-07-24 15:45 H. Peter Anvin wrote: > Chuck Ebbert wrote: > > > >Okay, I tested with Fedora on x86_64 and it worked there too. > >(Not that that proves much.) > > > >Did you capture any of the error messages, like the address > >of the segfault? > > > > FWIW, on x86-64, this should show up

Re: Is PIE randomization breaking klibc binaries?

2007-07-25 Thread Ulrich Kunitz
On 07-07-24 15:45 H. Peter Anvin wrote: Chuck Ebbert wrote: Okay, I tested with Fedora on x86_64 and it worked there too. (Not that that proves much.) Did you capture any of the error messages, like the address of the segfault? FWIW, on x86-64, this should show up in dmesg.

Re: Is PIE randomization breaking klibc binaries?

2007-07-24 Thread Ulrich Kunitz
On 07-07-24 15:45 H. Peter Anvin wrote: > Chuck Ebbert wrote: > > > >Okay, I tested with Fedora on x86_64 and it worked there too. > >(Not that that proves much.) > > > >Did you capture any of the error messages, like the address > >of the segfault? > > > > FWIW, on x86-64, this should show up

Re: Is PIE randomization breaking klibc binaries?

2007-07-24 Thread Ulrich Kunitz
On 07-07-24 16:57 Chuck Ebbert wrote: > > $ strace ./cat > > execve("./cat", ["./cat"], [/* 55 vars */]) = -1 ENOENT (No such file or > > directory) > > ... Chuck, my binaries run always into a segmentation violation. So ENOENT is not the issue. (Notify it was on an x86-64.) > > $ file cat > >

Re: Is PIE randomization breaking klibc binaries?

2007-07-24 Thread Ulrich Kunitz
On 07-07-24 16:57 Chuck Ebbert wrote: $ strace ./cat execve(./cat, [./cat], [/* 55 vars */]) = -1 ENOENT (No such file or directory) ... Chuck, my binaries run always into a segmentation violation. So ENOENT is not the issue. (Notify it was on an x86-64.) $ file cat cat: ELF 32-bit

Re: Is PIE randomization breaking klibc binaries?

2007-07-24 Thread Ulrich Kunitz
On 07-07-24 15:45 H. Peter Anvin wrote: Chuck Ebbert wrote: Okay, I tested with Fedora on x86_64 and it worked there too. (Not that that proves much.) Did you capture any of the error messages, like the address of the segfault? FWIW, on x86-64, this should show up in dmesg.

Is PIE randomization breaking klibc binaries?

2007-07-20 Thread Ulrich Kunitz
Since this week new linux-2.6/master kernels don't work with my initial ram disks. The sleep binary runs repeatingly into segmentation faults until the Busybox shell starts. My system is a x86-64 with Kubuntu Feisty Fawn. By bisecting I found out that the PIE randomization patch (commit 60bfba7e)

Is PIE randomization breaking klibc binaries?

2007-07-20 Thread Ulrich Kunitz
Since this week new linux-2.6/master kernels don't work with my initial ram disks. The sleep binary runs repeatingly into segmentation faults until the Busybox shell starts. My system is a x86-64 with Kubuntu Feisty Fawn. By bisecting I found out that the PIE randomization patch (commit 60bfba7e)

[PATCH] softmac: Fixed handling of deassociation from AP

2006-12-03 Thread Ulrich Kunitz
In 2.6.19 a deauthentication from the AP doesn't start a reassociation by the softmac code. It appears that mac->associnfo.associating must be set and the ieee80211softmac_assoc_work function must be scheduled. This patch fixes that. Signed-off-by: Ulrich Kunitz <[EMAIL PROTECTED]>

[PATCH] softmac: Fixed handling of deassociation from AP

2006-12-03 Thread Ulrich Kunitz
In 2.6.19 a deauthentication from the AP doesn't start a reassociation by the softmac code. It appears that mac-associnfo.associating must be set and the ieee80211softmac_assoc_work function must be scheduled. This patch fixes that. Signed-off-by: Ulrich Kunitz [EMAIL PROTECTED] --- net

[PATCH] tiny MM performance and typo patches for 2.4.2

2001-03-04 Thread Ulrich Kunitz
typo in asm-i386/pgtable-3level.h. Ciao, Uli Kunitz -- Ulrich Kunitz ([EMAIL PROTECTED]) --- linux-2.4.2/include/asm-i386/pgalloc.h Thu Feb 22 01:09:57 2001 +++ linux/include/asm-i386/pgalloc.hSun Mar 4 20:14:50 2001 @@ -92,9 +92,9 @@ free_page((unsigned long)pte

[PATCH] tiny MM performance and typo patches for 2.4.2

2001-03-04 Thread Ulrich Kunitz
typo in asm-i386/pgtable-3level.h. Ciao, Uli Kunitz -- Ulrich Kunitz ([EMAIL PROTECTED]) --- linux-2.4.2/include/asm-i386/pgalloc.h Thu Feb 22 01:09:57 2001 +++ linux/include/asm-i386/pgalloc.hSun Mar 4 20:14:50 2001 @@ -92,9 +92,9 @@ free_page((unsigned long)pte

2.4.0 i386: Why free_xxx_slow() instead free_xxx_fast()?

2001-01-20 Thread Ulrich Kunitz
) #define pmd_free_kernelpmd_free #define pmd_alloc_kernel pmd_alloc -- Ulrich Kunitz ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/

[PATCH] two comment typos, kernel 2.4.0

2001-01-20 Thread Ulrich Kunitz
_clear to obtain the old pte + * not possible, use ptep_get_and_clear to obtain the old pte * value and then use set_pte to update it. -ben */ static inline void set_pte(pte_t *ptep, pte_t pte) -- Ulrich Kunitz ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line "unsubscribe l

[PATCH] two comment typos, kernel 2.4.0

2001-01-20 Thread Ulrich Kunitz
to obtain the old pte + * not possible, use ptep_get_and_clear to obtain the old pte * value and then use set_pte to update it. -ben */ static inline void set_pte(pte_t *ptep, pte_t pte) -- Ulrich Kunitz ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line "unsubscribe linux-k

2.4.0 i386: Why free_xxx_slow() instead free_xxx_fast()?

2001-01-20 Thread Ulrich Kunitz
) #define pmd_free_kernelpmd_free #define pmd_alloc_kernel pmd_alloc -- Ulrich Kunitz ([EMAIL PROTECTED]) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/