> and sparc32 come to mind, though I might be mistaken.
On m68k we don't allow addresses above 0xF000.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 827
be mistaken.
On m68k we don't allow addresses above 0xF000.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different
if (result != 6) {
> - cmd_end();
> - return;
> - }
I'd rather guess that (result != 6 || result == 0x0E) is borken, since
it's equivalent to (result != 6).
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Produ
();
- return;
- }
I'd rather guess that (result != 6 || result == 0x0E) is borken, since
it's equivalent to (result != 6).
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B
FUNCTION,
>> +.read_fnct = jiffies_read,
>> +.mask = (cycle_t)~0,
>
> Not sure this is right. The type of 0 is 'int' and the ~ will happen
> before the cast to a potentially longer type.
If you want an all-one value for any unsigned type then (type)-1 is the
most reliable
= (cycle_t)~0,
Not sure this is right. The type of 0 is 'int' and the ~ will happen
before the cast to a potentially longer type.
If you want an all-one value for any unsigned type then (type)-1 is the
most reliable way.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products
Tom Horsley <[EMAIL PROTECTED]> writes:
> If I exec a setuid program under ptrace, I can read the image via
> PEEKDATA requests.
Only CAP_SYS_PTRACE capable processes get suid/sgid semantics under
ptrace, or can attach to a privileged processes.
Andreas.
--
Andreas Schwab, SuSE
Tom Horsley [EMAIL PROTECTED] writes:
If I exec a setuid program under ptrace, I can read the image via
PEEKDATA requests.
Only CAP_SYS_PTRACE capable processes get suid/sgid semantics under
ptrace, or can attach to a privileged processes.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL
4bit kernels.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
To unsubscribe from this list: send
is different between struct stat and struct stat64) overflows ino_t.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something com
Andi Kleen <[EMAIL PROTECTED]> writes:
> On Tue, Mar 01, 2005 at 11:10:38PM +0100, Andreas Schwab wrote:
>> That's because there are some values in the stat64 buffer delivered by the
>> kernel which cannot be packed into the stat buffer that you pass to stat.
>> Use sta
r nfs-mount points? Hmm, I
>> will tomorrow compare the tcp-packges sent by the server.
>
> So I still think thats a kernel bug.
This has nothing to do with the kernel.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürn
with the kernel.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different.
-
To unsubscribe from this list: send the line
Andi Kleen [EMAIL PROTECTED] writes:
On Tue, Mar 01, 2005 at 11:10:38PM +0100, Andreas Schwab wrote:
That's because there are some values in the stat64 buffer delivered by the
kernel which cannot be packed into the stat buffer that you pass to stat.
Use stat64 or _FILE_OFFSET_BITS=64
struct stat and struct stat64) overflows ino_t.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different
.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different.
-
To unsubscribe from this list: send the line unsubscribe linux
On ppc32 cur_cpu_spec is an array of pointers, not just a pointer like on
ppc64.
drivers/md/raid6altivec1.c: In function `raid6_have_altivec':
drivers/md/raid6altivec1.c:111: error: request for member `cpu_features' in
something not a structure or union
Andreas.
--
Andreas Schwab, SuSE Labs
On ppc32 cur_cpu_spec is an array of pointers, not just a pointer like on
ppc64.
drivers/md/raid6altivec1.c: In function `raid6_have_altivec':
drivers/md/raid6altivec1.c:111: error: request for member `cpu_features' in
something not a structure or union
Andreas.
--
Andreas Schwab, SuSE Labs
Linus Torvalds <[EMAIL PROTECTED]> writes:
> That's clearly not the case, and I haven't looked into exactly what
> termios settings "forkpty()" uses
If no termios is passed then the defaults are unchanged.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
Su
tty_write) from 4096 to 2048?
Yes, that helps.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
Alex Davis <[EMAIL PROTECTED]> writes:
> Problem does not exist on 2.6.8.1.
Yes, it is a pretty recent regression, reproducable since 2.6.10.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint =
Alex Davis [EMAIL PROTECTED] writes:
Problem does not exist on 2.6.8.1.
Yes, it is a pretty recent regression, reproducable since 2.6.10.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7
.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different.
-
To unsubscribe from this list: send the line unsubscribe linux
Linus Torvalds [EMAIL PROTECTED] writes:
That's clearly not the case, and I haven't looked into exactly what
termios settings forkpty() uses
If no termios is passed then the defaults are unchanged.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH
0)
bytes_read -= bytes_written, p += bytes_written;
}
exit (0);
}
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for somet
, p += bytes_written;
}
exit (0);
}
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
And now for something completely different.
-
To unsubscribe
Andi Kleen <[EMAIL PROTECTED]> writes:
> They worked fine forever - and suddenly you define them as buggy.
Working fine does not imply non-buggy, never has, never will.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg
Andi Kleen [EMAIL PROTECTED] writes:
They worked fine forever - and suddenly you define them as buggy.
Working fine does not imply non-buggy, never has, never will.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key
linux-os <[EMAIL PROTECTED]> writes:
> When I compile and run the following program:
>
> #include
> int main(int x, char **y)
> {
> pause();
> }
> ... as:
>
> ./xxx `yes`
This is roughly equivalent to this:
#include
int main(void) { while (1) malloc
linux-os [EMAIL PROTECTED] writes:
When I compile and run the following program:
#include stdio.h
int main(int x, char **y)
{
pause();
}
... as:
./xxx `yes`
This is roughly equivalent to this:
#include stdlib.h
int main(void) { while (1) malloc(1); }
Andreas.
--
Andreas Schwab
look in Documentation/power/swsusp.txt
>*/
>
> +#define DEBUG
> +
> #include
> #include
> #include
Another leftovers?
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58C
ructure object the compiler can actually put the parts of it anywhere it
likes, because you couldn't notice the difference.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECT
notice the difference.
Andreas.
--
Andreas Schwab And now for something
SuSE Labscompletely different.
[EMAIL PROTECTED]
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4E
.
--
Andreas Schwab And now for something
SuSE Labscompletely different.
[EMAIL PROTECTED]
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
-
To unsubscribe from
Perhaps the shell didn't close the filedescriptor on the script.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Ke
the filedescriptor on the script.
Andreas.
--
Andreas Schwab And now for something
SuSE Labscompletely different.
[EMAIL PROTECTED]
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3
he parent died memory for its task_struct was released.
|> >This is ungood.
|>
|> Wrap the reference to the parent task structure with exception table
|> recovery code, like copy_from_user().
Exception tables only protect accesses to user virtual memory. Kernel
memory references m
the reference to the parent task structure with exception table
| recovery code, like copy_from_user().
Exception tables only protect accesses to user virtual memory. Kernel
memory references must always be valid in the first place.
Andreas.
--
Andreas Schwab And now
a problem, since kernel and user address space are
strictly distinct, even in the kernel. The luser will get an EFAULT
eventually.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
space are
strictly distinct, even in the kernel. The luser will get an EFAULT
eventually.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzcker
|> I get the same on my Sun Ultra 1, and various x86 boxes. I'm sure this is
|> normal, I'm just not sure how you would change that label. I know gcc
|> compiles everything with a target of gcc-linux-unkown on my machines, so
|> the uknown may be coming from there...
. I'm sure this is
| normal, I'm just not sure how you would change that label. I know gcc
| compiles everything with a target of gcc-linux-unkown on my machines, so
| the uknown may be coming from there...
The two things are completely unrelated.
Andreas.
--
Andreas Schwab
|> MODULE_PARM(timid, "1i");
|> +MODULE_PARM(trigger_wait, "i");
|> +MODULE_PARM(nibble_wait, "i");
^^^
The types don't match.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labs
it, "i");
| +MODULE_PARM(nibble_wait, "i");
^^^
The types don't match.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Sc
complaining:
#define foo() { }
#define bar() do { } while (0)
void mumble ()
{
if (1) foo(); else bar();
if (2) bar(); else foo();
}
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely d
e (0)
void mumble ()
{
if (1) foo(); else bar();
if (2) bar(); else foo();
}
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanz
s directly w/o some
|> support library.
Don't use kernel headers in user programs. Just use syscall(3).
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE
rs in user programs. Just use syscall(3).
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzckerstr. 10, D-90443 Nrnberg
Key fingerprint =
ld treat \r
|> as just another whitespace character: it's what most shells do
Do they? Bourne shells don't, tcsh doesn't, zsh doesn't.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely d
Jesse Pollard <[EMAIL PROTECTED]> writes:
|> Andreas Schwab <[EMAIL PROTECTED]>:Andreas Schwab <[EMAIL PROTECTED]>Andreas Schwab
|<[EMAIL PROTECTED]>
|> > Paul Flinders <[EMAIL PROTECTED]> writes:
|> >
|> > |> Andreas Schwab w
Paul Flinders <[EMAIL PROTECTED]> writes:
|> Andreas Schwab wrote:
|>
|> > This [isspace('\r') == 1] has no significance here. The right thing to
|>
|> > look at is $IFS, which does not contain \r by default. The shell only splits
|>
|> > words by &qu
Paul Flinders [EMAIL PROTECTED] writes:
| Andreas Schwab wrote:
|
| This [isspace('\r') == 1] has no significance here. The right thing to
|
| look at is $IFS, which does not contain \r by default. The shell only splits
|
| words by "IFS whitespace", and the kernel should be
Jesse Pollard [EMAIL PROTECTED] writes:
| Andreas Schwab [EMAIL PROTECTED]:Andreas Schwab [EMAIL PROTECTED]Andreas Schwab
|[EMAIL PROTECTED]
| Paul Flinders [EMAIL PROTECTED] writes:
|
| | Andreas Schwab wrote:
| |
| | This [isspace('\r') == 1] has no significance here. The right thing
character: it's what most shells do
Do they? Bourne shells don't, tcsh doesn't, zsh doesn't.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzcker
ou (accd to the manual page)
|>
|> $ man isspace
This has no significance here. The right thing to look at is $IFS, which
does not contain \r by default. The shell only splits words by "IFS
whitespace", and the kernel should be consistent with it:
$ echo -e 'ls foo\r' | sh
ls: foo
: No such
^
|> + char buf[80];
|> + char *interpreter = extract_hash_bang_interpreter (pathname, buf);
|> +
|> + internal_error ("%s: command not found: `%s'", pathname,
|> + interpreter);
|> +
|>
reter (pathname, buf);
| +
| + internal_error ("%s: command not found: `%s'", pathname,
| + interpreter);
| +
|exit (EX_NOTFOUND); /* Posix.2 says the exit status is 127 */
| }
Andreas.
--
Andreas Schwab &q
if [ "${!conf}" != "y" ]; then
|> +if [ "${conf}" != "y" ]; then
|> define $1 y
|> else
|> debug "$1=y"
This is plain wrong. ${!conf} and ${conf} are completely different
things.
Andreas.
--
Andreas Schwab
fine $1 y
| else
| debug "$1=y"
This is plain wrong. ${!conf} and ${conf} are completely different
things.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EM
Peter Samuelson <[EMAIL PROTECTED]> writes:
|> [Admin Mailing Lists]
|> > i have no bits directory
|>
|> Really? What version of libc, and on what Linux distro? I thought all
|> versions of glibc2 had /usr/include/bits/.
No, it was introduced in glibc 2.0.5.
Andr
Peter Samuelson [EMAIL PROTECTED] writes:
| [Admin Mailing Lists]
| i have no bits directory
|
| Really? What version of libc, and on what Linux distro? I thought all
| versions of glibc2 had /usr/include/bits/.
No, it was introduced in glibc 2.0.5.
Andreas.
--
Andreas Schwab
ails of the symlink
|> whereas lstat should return the details of the symlink target.
Nope, check the facts.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTE
.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzckerstr. 10, D-90443 Nrnberg
-
To unsubscribe from this list: send the line "unsubscri
ch is the right thing.
AFAICS, _all_ resource limits are equally applied to root processes. Why
should NPROC be different?
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different.&qu
Andrea Arcangeli <[EMAIL PROTECTED]> writes:
|> On Tue, Nov 28, 2000 at 10:55:06AM +0100, Andreas Schwab wrote:
|> > Alexander Viro <[EMAIL PROTECTED]> writes:
|> >
|> > |> On Tue, 28 Nov 2000, Andrea Arcangeli wrote:
|> > |>
|> > |> > O
|> > > test2.c:
|> > > int a,c;
|> > >
|> > > Which is _stronger_?
|> >
|> > Those won't link together as they aren't declared static.
|>
|> Try it. They _will_ link together.
Not if you compile with -fno-common, which should actually be the d
.
AFAICS, _all_ resource limits are equally applied to root processes. Why
should NPROC be different?
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Scha
link together as they aren't declared static.
|
| Try it. They _will_ link together.
Not if you compile with -fno-common, which should actually be the default
some day, IMHO.
Andreas.
--
Andreas Schwab "And now for something
SuSE
Andrea Arcangeli [EMAIL PROTECTED] writes:
| On Tue, Nov 28, 2000 at 10:55:06AM +0100, Andreas Schwab wrote:
| Alexander Viro [EMAIL PROTECTED] writes:
|
| | On Tue, 28 Nov 2000, Andrea Arcangeli wrote:
| |
| | On Tue, Nov 28, 2000 at 12:10:33PM +0900, [EMAIL PROTECTED] wrote
Igmar Palsenberg <[EMAIL PROTECTED]> writes:
|> > > #define __bad_udelay() panic("Udelay called with too large a constant")
|>
|> Can't we change that to :
|> #error "Udelay..."
No.
Andreas.
--
Andreas Schwab
Igmar Palsenberg [EMAIL PROTECTED] writes:
| #define __bad_udelay() panic("Udelay called with too large a constant")
|
| Can't we change that to :
| #error "Udelay..."
No.
Andreas.
--
Andreas Schwab "And no
ot not_eq or or_eq private protected
public reinterpret_cast static_cast template this throw true try typeid
typename using wchar_t xor xor_eq
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely differen
typename using wchar_t xor xor_eq
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
-
To unsubscribe from this list: sen
trap
|>
|> Wouldn't it be better to use an #error directive?
There is no way to test the condition in the preprocessor.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[
0x10c6ul)) : \
| __udelay(n))
|
| ...
| It seems __bad_udelay is not defined anywhere in the kernel source.
|
| Correct. Its a compile time error trap
|
| Wouldn't it be better to use an #error directive?
There is no way to test the condition in the preprocessor.
Andreas.
--
Andr
t;$$BASH" ]; then echo $$BASH; \
elif [ -x /bin/bash ]; then echo /bin/bash; \
else echo sh; fi)
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[
; \
elif [ -x /bin/bash ]; then echo /bin/bash; \
else echo sh; fi)
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE GmbH, Schanzäckerst
t already does it in all other places. Perhaps
some problem with the patterns in the machine description.
Andreas.
--
Andreas Schwab "And now for something
SuSE Labscompletely different."
[EMAIL PROTECTED]
SuSE G
901 - 979 of 979 matches
Mail list logo
