I've been seeing a build error when trying to build User Mode Linux on
an x86-32 host (Athlon, fwiw). The kernel I'm building is a 1-day old
pull from git. This error is not new, though. I thought it was merely
an artifact of a patch stuck in a queue at first so I didn't mention it
right away.
On Saturday 23 April 2005 08:57 am, Blaisorblade wrote:
> > By the way, I've toyed with the idea of running this sucker in an
> > otherwise empty chroot environment (/proc/self/fd is likely to exist and
> > have fairly uninteresting contents. As a chroot environment, it just has
> > symlinks that
[EMAIL PROTECTED] wrote:
>
> linux-2.6.12-paolo/arch/i386/kernel/entry.S | 292
>
> linux-2.6.12-paolo/arch/i386/kernel/syscall_table.S | 291
> +++
gack. Any time anyone touches the syscall tables I have to delicately
rework 8,000 perfctr patches
Blaisorblade wrote:
Other issues follow, which refer to copied code going out-of-date wrt. my
local tree (which I have snapshotted some time ago, after I started writing
this mail). This is the problem with copying code - and you're starting
experiencing it!
* important changes for TLS support,
Blaisorblade wrote:
This is the first of a series of 7 invasive patches for the -mm tree, which
are to be reviewed (not only by UML folks), and possibly merged for the
2.6.13 cycle.
The first one splits the i386 syscall table out of entry.S, without any real
change for them (the file is include
Hi Alexander
On Mon, 2005-04-25 at 21:57 +0200, Alexander Nyberg wrote:
> mån 2005-04-25 klockan 21:12 +0200 skrev [EMAIL PROTECTED]:
> > From: Andree Leidenfrost <[EMAIL PROTECTED]>, Paolo 'Blaisorblade'
> > Giarrusso <[EMAIL PROTECTED]>
> >
> > Fix the error path, which is triggered when the p
From: Jeff Dike <[EMAIL PROTECTED]>, Paolo 'Blaisorblade' Giarrusso <[EMAIL
PROTECTED]>
In short: avoid that the kernel oopses during the extable sorting, as it can
do now, because the extable is in the readonly section of the binary.
>From Jeff: The exception table turned RO in 2.6.11-rc3-mm1
CC: Jens Axboe <[EMAIL PROTECTED]>
Use the set_disk_ro() API when the backing file is read-only, to mark the disk
read-only, during the ->open(). The current hack does not work when doing a
mount -o remount.
Also, mark explicitly the code paths which should no more be triggerable (I've
removed t
On Mon, Apr 25 2005, Blaisorblade wrote:
> On Monday 25 April 2005 12:16, Jens Axboe wrote:
> > On Sun, Apr 24 2005, [EMAIL PROTECTED] wrote:
> > > @@ -1099,6 +1104,7 @@ static int prepare_request(struct reques
> > > if((rq_data_dir(req) == WRITE) && !dev->openflags.w){
> > > printk("Wr
