x27;t clear it some of your zero-initialized
variables won't be zero initialized at all.
In the linked message, set_brk is passed elf_bss so its actual
arguments are set_brk (0xa3801, 0x000a4ec8). It should map one
page. 0xa3801 should be an already mapped page, and clear_user should
succe
8k, s390, vax - but don't quote
me on that, I had to guess from the configure script.
--
Daniel Jacobowitz
CodeSourcery
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.
til the kernel is fixed,
verify it, and then probably adjust the GDB test to pass on either
patched or unpatched kernels.
--
Daniel Jacobowitz
CodeSourcery
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
eturn vma->vm_file->f_dentry->d_inode->i_nlink == 0;
>
> - /* If it hasn't been written to, don't write it out */
> - if (!vma->anon_vma)
> + /* If it is executable and hasn't been written to,
> + * don't write it out.
> +
From: Daniel Jacobowitz <[EMAIL PROTECTED]>
Do not implement CLONE_PARENT_SETTID until we know that clone will succeed.
If we do it too early NPTL's data structures temporarily reference a
non-existant TID.
Signed-off-by: Daniel Jacobowitz <[EMAIL PROTECTED]>
---
On Tue, Sep
nd this _seems_ to fix it too:
>
> taskset -p 1 `ps axo comm,pid|awk '$1=="X"{print $2}'`
>
> I haven't seen this problem on the console.
This is probably the same problem as the earlier one you reported. If
you take a look at bugzilla, you'll see t
> 15 251 + 0 = 251
> 16 147 + 1 = 148 <==
> 17 0 + 252 = 252
Hmm, very interesting.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAI
like I'd expect, although there are still a handful of
kernel-related failures (vsyscall related?).
Signed-off-by: Daniel Jacobowitz <[EMAIL PROTECTED]>
diff -r -p -u z/linux-2.6.11/arch/x86_64/ia32/ptrace32.c
linux-2.6.11/arch/x86_64/ia32/ptrace32.c
--- linux-2.6.12.3.orig/arch/x86_64
the kernel has done
something clever to the value of %ebp.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
37MB worth of patch-code ? I would expect something about
> 2MB but 40MB ?
Try interdiff -p1?
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at h
> *word* size...
While true, this is easily fixable. There is even an interface
precedent on OpenBSD (and possibly other platforms as well).
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
currently patching?
Even with hundreds of kilobytes of patch, I have trouble imagining this
takes a substantial amount of time.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Mor
ism for mmap/munmap/mprotect in a debugged
process, also.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
is running) makes no
> sense, does it?
That argument doesn't make much sense to me. But we're at the end of
my useful contributions to this discussion; I'm going to be quiet now
and hope some folks who know more about filesystems have more useful
responses.
--
Daniel Jacobowitz
Co
les that the user has requested no
other users be able to write as unwritable by group/other? Sure, it
makes your tarfs a little less mapped onto the tar file. But that's
one of the recurring objections to implementing archivers as
filesystems: the ownership in the archive is _not_ relevant t
eems not unreasonable - provided the
> administrator can delete the directory (which is possible with
> detachable mount points).
Because then they could mount over /tmp. "and (is not sticky || is
owned by the user)" may be more appropriate.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To
ault_permissions".
But why does the kernel need to know anything about this? Why can't
the userspace library present the permissions appropriately to the
kernel? I'm going to be pretty confused if I see a mode 666 file that
I can't even read. So will various programs.
Ex
otherwise.
I can think of plenty of uses for this.
> 4) Access should not be further restricted for the owner of the
> mount, even if permission bits, uid or gid would suggest
> otherwise
Similar questions.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list
with LINUX_REBOOT_CMD_RESTART.
LINUX_REBOOT_CMD_CAD_OFF
(RB_DISABLE_CAD, 0). CAD is disabled. This means that the CAD
keystroke will cause a SIGINT signal to be sent to init
(process 1), whereupon this process may decide upon a
proper ac
ter be...
My impression is that the MIPS story isn't so simple, because the
architecture only offers very weak coherency guarantees. Most of the
SMP implementations offer strong coherency in practice, but at least
one (RM9000) doesn't.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe
ot;if (!card)" can not be
reached without passing through "card->amplifier", and a pointer which
is dereferenced can not be NULL in a valid program.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
27;t open. Hmm, server is x86_64 2.6.7, client is 2.6.10
MIPS. I should upgrade them and see if that helps.
Unfortunately I haven't found any smaller testcases than installing an
entire root FS.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "
On Sun, Mar 13, 2005 at 03:42:29PM -0500, Trond Myklebust wrote:
> su den 13.03.2005 Klokka 15:04 (-0500) skreiv Daniel Jacobowitz:
>
> > I can't find any documentation about this, but it seems like the same
> > problem that has been causing me headaches lately; when I rep
macro, which is called
> before the ptrace stop for whatever signal results from whatever kind of
> fault in that instruction (or asynchronous signal). With that, the
> handle_signal check is still needed only for the case of PTRACE_SINGLESTEP
> with a handled signal.
>
>
&
hen I replace glibc
from the server side of an nfsroot, the client has a couple of
variously wrong reads before it sees the new files. If it breaks NFS
so badly, why is it the default for the Linux NFS server?
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ally for Fedora's flavor, but no writing is ever
> possible to the fixmap page.
Blech. I assume that there is no way to map a normal VMA over top of
the fixed page, for a particular process? This makes debugging the
vsyscall DSO a real pain.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
T
gt;
> I don't know what that one is about, but it was KFAIL before the change too.
That is an inability to set breakpoints in the vsyscall page. Andrew
told me (last May, wow) that he thought this worked in Fedora, but I
haven't seen any signs of the code. It would certainly be a Go
doesn't occur because the
debugger cancelled a signal, it occurs because a bogus TF bit was saved
to the signal context. I like keeping solutions close to their
problems. But that's just aesthetic.
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
e to clear it when creating a
signal context. Otherwise, TF will be incorrectly restored by
sigreturn.
Signed-off-by: Daniel Jacobowitz <[EMAIL PROTECTED]>
= arch/i386/kernel/signal.c 1.53 vs edited =
--- 1.53/arch/i386/kernel/signal.c 2005-01-31 01:20:14 -05:00
+++ edited/arch/
On Sun, Mar 06, 2005 at 02:38:41PM -0500, Daniel Jacobowitz wrote:
> The reason this happens is that when the inferior hits a breakpoint, the
> first thing GDB will do is remove the breakpoint, single-step past it, and
> reinsert it. So GDB does a PTRACE_SINGLESTEP, and the kernel in
We need to know when we restore the trap bit in sigreturn
whether it was set by ptrace or by the application (possibly including by
the signal handler).
Andrew, serious kudos for GDB's sigstep.exp, which uncovered this problem
(through a much more complicated test - I may add the smalle
or it.
I know several ARM kernel developers who are using tools with this
patch applied already. Also, I anticipate the release of binutils 2.16
including the fix in about a month.
> And yes, the toolchain peoples point of view is "fix the kernel".
Huh? Obviously the kernel
t sysn32_waitid.
Ralf, I'll let you sort it out :-)
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
"pipe failed");
return 1;
}
size_t len2 = fpathconf (fds[1], _PC_PIPE_BUF);
size_t page_size = sysconf (_SC_PAGESIZE);
len2 = (len2 < page_size ? page_size : len2) + 1 + 1;
char *mem2 = malloc (len2);
pthread_create (&th, NULL, tf, fds);
write (fds[1], mem2, len2);
I think
about it I can see why this is a problem - the kernel probably assumes
that any segment with MemSiz > FileSiz will be writable. Certainly
it's a bit weird for the app to request unwritable zeroed pages.
clear_user's probably not the right way to provide the extra zeroing.
--
Dan
clearing the BSS fail? Are the program headers bogus?
(readelf -l).
--
Daniel Jacobowitz
CodeSourcery, LLC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.ht
GCC - and it fell down like this on a constant basis.
You might want to take a look at 'xcvs', by Jun Sun. It's much more
reliable and does everything I used to use cvsps for. And generally
faster too.
--
Daniel Jacobowitz
-
To unsubscribe from this list: send the line "un
at runtime. I suppose you could change this with chrpath,
> but why bother? What if you want to test out two versions of relative
> libraries side by side?
You might want to take a look at Richard's suggestion again. The
string '$ORIGIN' gets hardcoded into the binary and ha
jail, so I added a feature to ptrace()
> that remedies the situation.
This has since been done in 2.5.x; see PTRACE_EVENT_FORK. GDB even
uses it nowadays. I'm not sure if strace does.
--
Daniel Jacobowitz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
g PCI regs\n", d->name);
+ return;
+ }
+ }
+#endif
if (!(pcicmd & PCI_COMMAND_IO)) { /* is device disabled? */
/*
* PnP BIOS was *supposed* to have set this device up for us,
Dan
/--
40 matches
Mail list logo
