Sorry if this question is dumb.
SELinux is included in 2.6. But I think it works by putting LSM hooks a lot
of place in Linux and then it can define its own policy enforcement codes.
However, I cannot find hooks in kernel 2.6.9 and 2.6.11. How can
SELinux work with kernel 2.6 to protect system wi
On 9/7/05, Miloslav Trmac <[EMAIL PROTECTED]> wrote:
> +static int __init map_bios(void)
> +{
> + static const unsigned char __initdata signature[]
> + = { 0x42, 0x21, 0x55, 0x30 };
> +
> + void __iomem *base;
> + size_t offset;
> + uint32_t entry_point;
> +
> + base
On Wed, 2005-09-07 at 23:11 -0700, Martin J. Bligh wrote:
> >> >> CONFIG_NUMA was meant to (and did at one point) support both NUMA and
> >> >> flat
> >> >> machines. This is essential in order for the distros to support it -
> >> >> same
> >> >> will go for sparsemem.
> >> >
> >> > That's a dif
On Mon, 2005-09-05 at 09:06 -0400, Manuel Lauss wrote:
> On Mon, Sep 05, 2005 at 08:54:59AM -0400, Justin Piszcz wrote:
> > I have a box where I keep getting this in dmesg:
> >
> > ACPI: PCI Interrupt :01:00.0[A] -> Link [LNKD] -> GSI 5 (level,
> low)
> > -> IRQ 5
> > ACPI: PCI Interrupt :0
>> >> CONFIG_NUMA was meant to (and did at one point) support both NUMA and flat
>> >> machines. This is essential in order for the distros to support it - same
>> >> will go for sparsemem.
>> >
>> > That's a different issue. The current code works if you boot a NUMA=y
>> > SPARSEMEM=y machine wi
The function prototype for handle_IRQ_event() in include/asm-ppc/irq.h
seems no longer needed because ppc uses GENERIC_HARDIRQ. This patch
removes it.
Signed-off-by: Kenji Kaneshige <[EMAIL PROTECTED]>
include/asm-ppc/irq.h |4
1 files changed, 4 deletions(-)
Index: linux-2.6.13/includ
On Thursday 08 September 2005 07:10, Parag Warudkar wrote:
> Andi Kleen wrote:
> >Hmm - not many x86-64 patches in mm1. 2.6.13 definitely works.
>
> 2.6.13-git7 works. So something in -mm has gone bad (if not x86_64, may
> be i386 or arch-independent changes?)
> It seems it has got something to do
The function prototype for handle_IRQ_event() in include/asm-x86_64/irq.h
seems no longer needed because x86_64 uses GENERIC_HARDIRQ. This patch
removes it.
Signed-off-by: Kenji Kaneshige <[EMAIL PROTECTED]>
include/asm-x86_64/irq.h |4
1 files changed, 4 deletions(-)
Index: linux-2.6.
The function prototype for handle_IRQ_event() in include/asm-sh/irq.h
seems no longer needed because sh uses GENERIC_HARDIRQ. This patch
removes it.
Signed-off-by: Kenji Kaneshige <[EMAIL PROTECTED]>
include/asm-sh/irq.h |4
1 files changed, 4 deletions(-)
Index: linux-2.6.13/include/a
This patch adds subcpusets framework code to the CPUSETS.
Subcpusets are meant for subdividing cpuset resources.
A few files are added in order to control the guarantee and the limit
of the resource amount to the cpuset filesystem. Also, interfaces
for the specific resource controller like CPU and
This patch adds a document of the SUBCPUSETS.
Signed-off-by: KUROSAWA Takahiro <[EMAIL PROTECTED]>
--- /dev/null
+++ to-work/Documentation/subcpuset.txt 2005-09-08 11:44:47.994331730 +0900
@@ -0,0 +1,129 @@
+Addition to the cpuset filesystem: "subcpuset"
+
+ "subcpuset" directories are incorpora
This patch adds CPU resource controller. It enables us to control
CPU time percentage of tasks grouped by the cpu_rc structure.
It controls time_slice of tasks based on the feedback of difference
between the target value and the current usage in order to control
the percentage of the CPU usage to
This patch puts the CPU resource controller into SUBCPUSETS framework.
With this patch, we can control the CPU resource from the cpuset
filesystem.
Signed-off-by: KUROSAWA Takahiro <[EMAIL PROTECTED]>
--- from-0005/init/Kconfig
+++ to-work/init/Kconfig2005-09-07 20:49:02.766634348 +0900
The function prototype for handle_IRQ_event() in include/asm-mips/irq.h
seems no longer needed because mips uses GENERIC_HARDIRQ. This patch
removes it.
Signed-off-by: Kenji Kaneshige <[EMAIL PROTECTED]>
include/asm-mips/irq.h |3 ---
1 files changed, 3 deletions(-)
Index: linux-2.6.13/incl
This patch fixes minor problem that the CPUSETS have when files
in the cpuset filesystem are read after lseek()-ed beyond the EOF.
Signed-off-by: KUROSAWA Takahiro <[EMAIL PROTECTED]>
--- from-0001/kernel/cpuset.c
+++ to-work/kernel/cpuset.c 2005-09-05 20:26:18.075772762 +0900
@@ -984,6 +984,
The following patchset adds resource control functionality to the
CPUSETS code by subdividing a cpuset into smaller pieces (SUBCPUSETS).
It is made up from two parts, one for the resource control framework
and another for the specific resource controller. Resource controllers
can be added by usi
Hi,
I think the function prototypes for handle_IRQ_event() in
include/asm-{mips,ppc,sh,x86_64}/irq.h are no longer needed because
these architectures are using GENERIC_HARDIRQ. This series of patches
removes those unnecessary handle_IRQ_event() prototypes.
NOTE: Since I don't have these architect
On Thu, Sep 01, 2005 at 01:35:23PM +0200, Arjan van de Ven wrote:
> +static inline void glock_put(struct gfs2_glock *gl)
> +{
> + if (atomic_read(&gl->gl_count) == 1)
> + gfs2_glock_schedule_for_reclaim(gl);
> + gfs2_assert(gl->gl_sbd, atomic_read(&gl->gl_count) > 0,);
> + a
Miloslav Trmac <[EMAIL PROTECTED]> wrote:
>
> +static void call_bios(struct regs *regs)
> +{
> +unsigned long flags;
> +
> +preempt_disable();
> +local_irq_save(flags);
> +asm volatile ("pushl %%ebp;"
> + "movl %[data], %%ebp;"
> + "call *%[
Thanks Michal for your response,
I forgot to mention that I am using linux 2.4.26,
and STACKOVERFLOW option is not available here.
regards,
Nazim
--- Michal Schmidt <[EMAIL PROTECTED]>
wrote:
> nazim khan wrote:
> > I suspect that one of my module that I am
> inserting in
> > the kernel may be
On Wed, 2005-09-07 at 22:18 -0400, Jeff Garzik wrote:
> Alejandro Bonilla Beeche wrote:
>
> Wanna post a URL to your .config?
Jeff,
Sorry, I did not paste it in the ML because this has always worked for
me, but hell, maybe I got something wrong! :|
Attached...
.Alejandro
> Jeff
Andi Kleen wrote:
Hmm - not many x86-64 patches in mm1. 2.6.13 definitely works.
2.6.13-git7 works. So something in -mm has gone bad (if not x86_64, may
be i386 or arch-independent changes?)
It seems it has got something to do with the sys_set_tid_address as
evident from the strace output b
On Mon, 5 Sep 2005 13:55:46 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
> Re: Elitegroup K7S5A + usb_storage problem
> [linux-usb-devel] Fw: Re: Elitegroup K7S5A + usb_storage problem
This appears to be stuck. It has to have someone with a lot of patience
to play with the device.
Martin coll
On Wed, Sep 07, 2005 at 10:05:30PM -0500, Brian King wrote:
> I reverted the patch to use a spinlock and added a comment.
> How does this look?
Fine with me. Ball is in akpm/Paul's court.
grant
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [
On Thursday 08 September 2005 05:54, Parag Warudkar wrote:
> I am clueless as to what's going on but just raising a flag in case it
> is a not yet known problem.
> Thunderbird, 32bit Sun Java and Opera are the ones I tried. They all
> work fine with the Fedora 2.6.12-x kernel but
> consistently seg
I am clueless as to what's going on but just raising a flag in case it
is a not yet known problem.
Thunderbird, 32bit Sun Java and Opera are the ones I tried. They all
work fine with the Fedora 2.6.12-x kernel but
consistently seg fault with 2.6.13-mm1.
Parag
Sample stack trace for jav
Grant Grundler wrote:
On Thu, Sep 08, 2005 at 08:39:15AM +1000, Paul Mackerras wrote:
Grant Grundler writes:
I would argue it more obvious. People looking at the code
are immediately going to realize it was a deliberate choice to
not use a spinlock.
It achieves exactly the same effect as s
On Wednesday 07 September 2005 06:50, Andrew Morton wrote:
> Marko Kohtala <[EMAIL PROTECTED]> wrote:
> >
> > > You just sent ten patches, all with the same name. This causes me grief
> > > (See http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt, section
> > 2a).
> >
> > I used "quilt mai
CUNANAN MAPHOUSE (CMH)
#4930 A.S. Arnaiz Ave.,
Pio del Pilar, Makati City
Tel. 888-0199
TeleFax. 888-0199
Cel. 0916-2560182
0920-4725175
OFFER TO SELL
SPECIAL MAPS
GLAD TIDINGS!
It is with special gladness to invite your early investments in handmade,
hand-colored and updated Cunanan Stat
Kalin KOZHUHAROV thinrope.net> writes:
> ata1: dev 0 configured for UDMA/100
> ata2: dev 0 configured for UDMA/100
> scsi1 : sata_sil
>Vendor: ATA Model: WDC WD360GD-00FL Rev: 21.0
>Type: Direct-Access ANSI SCSI revision: 05
>Vendor: ATA Model: ST33
Thanks Chris and Nick for your feedback. I am investigating the issues
that you raised. Hopefully I will address them by COB tomorrow.
-Janak
Chris Wright wrote:
* Janak Desai ([EMAIL PROTECTED]) wrote:
diff -Naurp linux-2.6.13-mm1/kernel/fork.c
linux-2.6.13-mm1+unshare-patch1/kernel/fork.
On Wed, Sep 07, 2005 at 03:33:57AM -0400, rob wrote:
> Is there some way to change the sowftware suspend2 scripts to work with the
> unpatched kernel software suspend
Yes. Just comment out everything in the suspend2 section, and enable
"UseSysfsPowerState disk". It really should get a less ugly na
Alejandro Bonilla Beeche wrote:
Hi,
Where does one report this? I was building Linus Git tree as per I
updated it at 09/07/2005 7:00PM PDT and got this while compiling.
Where do I report this?
Debian unstable updated at same time.
it looks like ipw2200 is thinking that ieee80211 is no
Linux Kernel Mailing List wrote:
diff --git a/drivers/scsi/qla1280.c b/drivers/scsi/qla1280.c
--- a/drivers/scsi/qla1280.c
+++ b/drivers/scsi/qla1280.c
@@ -1546,7 +1546,7 @@ qla1280_return_status(struct response *
int host_status = DID_ERROR;
uint16_t comp_status = le16_to_cpu(sts->co
On 9/2/05, Richard Hayden <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> It appears there is no protection in badness() (called by
> out_of_memory() for each process) when it reads p->mm->total_vm. Another
> processor (or a kernel preemption) could presumably run do_exit and then
> exit_mm, freeing the
On 9/8/05, Andrew Morton <[EMAIL PROTECTED]> wrote:
> "Martin J. Bligh" <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > --On Wednesday, September 07, 2005 11:27:54 -0700 Dave Hansen <[EMAIL
> > PROTECTED]> wrote:
> >
> > > On Wed, 2005-09-07 at 11:22 -0700, Martin J. Bligh wrote:
> > >> CONFIG_NUMA was
On 9/8/05, Dave Hansen <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-09-07 at 11:22 -0700, Martin J. Bligh wrote:
> > CONFIG_NUMA was meant to (and did at one point) support both NUMA and flat
> > machines. This is essential in order for the distros to support it - same
> > will go for sparsemem.
>
>
Linux Kernel Mailing List wrote:
tree 1771b690cdee80312ace3fe046e29e965a0b30eb
parent c8d127418d78aaeeb1a417ef7453dc09c9118146
author Tommy S. Christensen <[EMAIL PROTECTED]> Wed, 07 Sep 2005 05:17:28 -0700
committer Linus Torvalds <[EMAIL PROTECTED]> Thu, 08 Sep 2005 06:57:30 -0700
[PATCH] 3c59
On 9/8/05, Martin J. Bligh <[EMAIL PROTECTED]> wrote:
> --On Wednesday, September 07, 2005 10:28:36 -0700 Dave Hansen <[EMAIL
> PROTECTED]> wrote:
>
> > On Tue, 2005-09-06 at 12:56 +0900, Magnus Damm wrote:
> >> This patch for 2.6.13-git5 fixes single node sparsemem support. In the case
> >> when
On 9/8/05, Dave Hansen <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-09-06 at 12:56 +0900, Magnus Damm wrote:
> > This patch for 2.6.13-git5 fixes single node sparsemem support. In the case
> > when multiple nodes are used, setup_memory() in arch/i386/mm/discontig.c
> > calls
> > get_memcfg_numa() whi
Hi,
Where does one report this? I was building Linus Git tree as per I
updated it at 09/07/2005 7:00PM PDT and got this while compiling.
Where do I report this?
Debian unstable updated at same time.
it looks like ipw2200 is thinking that ieee80211 is not compiled in, but
I did select it
Janak Desai wrote:
- tsk->min_flt = tsk->maj_flt = 0;
- tsk->nvcsw = tsk->nivcsw = 0;
+ /*
+* If the process memory is being duplicated as part of the
+* unshare system call, we are working with the current process
+* and not a newly allocated task stru
-stable review patch. If anyone has any objections, please let us know.
--
[IPV4]: Reassembly trim not clearing CHECKSUM_HW
This was found by inspection while looking for checksum problems
with the skge driver that sets CHECKSUM_HW. It did not fix the
problem, but it looks like
-stable review patch. If anyone has any objections, please let us know.
--
[CRYPTO] Fix boundary check in standard multi-block cipher processors
Fixes Bug 5194 (IPSec related Oops in 2.6.13).
The boundary check in the standard multi-block cipher processors are
broken when nbyte
-stable review patch. If anyone has any objections, please let us know.
--
I had some time to think about PCI assign issues in 2.6.13-rc series.
The major problem here is that we call pci_assign_unassigned_resources()
way too early - at subsys_initcall level. Therefore we give n
-stable review patch. If anyone has any objections, please let us know.
--
[NET]: 2.6.13 breaks libpcap (and tcpdump)
Patrick McHardy says:
Never mind, I got it, we never fall through to the second switch
statement anymore. I think we could simply break when load_pointer
-stable review patch. If anyone has any objections, please let us know.
--
I wish I had seen this before 2.6.13 was released... I guess this only
goes to show that there haven't been any testers using saa7134-hybrid
dvb/v4l boards that depend on the tda1004x module, during the
-stable review patch. If anyone has any objections, please let us know.
--
This fixes a problem with pci_map_rom() which doesn't properly
update the ROM BAR value with the address thas allocated for it by the
PCI code. This problem, among other, breaks boot on Mac laptops.
It'ss
-stable review patch. If anyone has any objections, please let us know.
--
Based upon a report from Jason Wever.
Signed-off-by: "David S. Miller" <[EMAIL PROTECTED]>
Signed-off-by: Chris Wright <[EMAIL PROTECTED]>
---
drivers/char/rtc.c |5 ++---
1 files changed, 2 insertio
-stable review patch. If anyone has any objections, please let us know.
--
When we copy 32bit ->msg_control contents to kernel, we walk the same
userland data twice without sanity checks on the second pass.
Second version of this patch: the original broke with 64-bit arches
runn
This is the start of the stable review cycle for the 2.6.13.1 release.
There are 9 patches in this series, all will be posted as a response to
this one. If anyone has any issues with these being applied, please let
us know. If anyone is a maintainer of the proper subsystem, and wants
to add a sig
-stable review patch. If anyone has any objections, please let us know.
--
This was noticed by Doug Bazamic and the fix found by Mark Salyzyn at
Adaptec.
There was an error in the BUG_ON() statement that validated the
calculated fib size which can cause the driver to panic.
Sig
On Wednesday 07 September 2005 08:34 pm, Mr. Liam Johnson wrote:
> Dear Sir,
>
> Please accept my sincere apologies if my email does not meet
> your business or personal ethics.
Apology accepted.
--
Patrick "Diablo-D3" McFarland || [EMAIL PROTECTED]
"Computer games don't affect kids; I mean if P
On Thu, Sep 08, 2005 at 08:39:15AM +1000, Paul Mackerras wrote:
> Grant Grundler writes:
>
> > I would argue it more obvious. People looking at the code
> > are immediately going to realize it was a deliberate choice to
> > not use a spinlock.
>
> It achieves exactly the same effect as spin_lock/
On Sat, Sep 03, 2005 at 09:54:45PM -0700, Joel Becker wrote:
> Finally, assuming that the sysfs_dirent/configfs_dirent
> arrangement is pretty fleshed out, I think that perhaps this backing
> store could be joined. Again, no more magic could be added, and it
> would have to handle the sysfs
On Thu, 8 Sep 2005 01:25:20 +0200, Jan Kiszka <[EMAIL PROTECTED]> said:
Jan> Yes, I can provide some numbers around atheros devices (10-20%
Jan> speed-up). And yes, I can explain why ndiswrapper suffers from
Are you comparing atheros Windows driver with ndiswrapper or madwifi
with ndiswrappe
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
>
>
> On Wed, 7 Sep 2005, Linus Torvalds wrote:
> >
> > Quite frankly, what's the point in asking people to pull a tree that is
> > known to not compile?
James was assuming you'd merged the klist patch whcih I'd sent beforehand.
> Btw, I see the pat
On Wed, 7 Sep 2005 06:04:36 -0500 Milton Miller <[EMAIL PROTECTED]> wrote:
>
> Does anything actually break without this patch?
Yes, an iSeries box will not boot.
> My reading of unregister_console says we will acquire
> the console semaphore, walk the list, fail to find the
> console, relase the
On Wed, 2005-09-07 at 17:49 -0700, Linus Torvalds wrote:
> > Quite frankly, what's the point in asking people to pull a tree that is
> > known to not compile?
>
> Btw, I see the patch that is supposed to fix it, but I'm in no position to
> know whether it's even acceptable to basically double the
On Wed, 2005-09-07 at 17:41 -0700, Linus Torvalds wrote:
> And also, this fails to compile due to the klist problem.
>
> Quite frankly, what's the point in asking people to pull a tree that is
> known to not compile?
>
> Now I made the mistake of pushing the thing out before I realized that the
David S. Miller wrote:
From: Ingo Oeser <[EMAIL PROTECTED]>
Date: Wed, 7 Sep 2005 15:39:08 +0200
Jeff Garzik wrote:
I find them useful in my own drivers; they are definitely not pure noise.
gcc -finstrument-functions
I was going to mention this as well, and also the idea to
enable CONFI
On Wed, 7 Sep 2005, Linus Torvalds wrote:
>
> Quite frankly, what's the point in asking people to pull a tree that is
> known to not compile?
Btw, I see the patch that is supposed to fix it, but I'm in no position to
know whether it's even acceptable to basically double the size of the
"struct
--- Bill Davidsen <[EMAIL PROTECTED]> wrote:
> Alex Davis wrote:
> >>Please don't tell me to "care for closed-source drivers".
> >
> > ndiswrapper is NOT closed source. And I'm not asking you to "care".
> >
> >
> >>I don't want the pain of debugging crashes on the machines which run
> >>unk
On Wed, 7 Sep 2005, Linus Torvalds wrote:
>
> You meant
>
> master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-for-linus-2.6.git
>
> I do believe,
And also, this fails to compile due to the klist problem.
Quite frankly, what's the point in asking people to pull a tree that is
known to
On Wed, 2005-09-07 at 17:31 -0700, Linus Torvalds wrote:
> On Tue, 6 Sep 2005, James Bottomley wrote:
> >
> > master.kernel.org:/pub/linux/kernel/scm/jejb/scsi-for-linus-2.6.git
>
> No it isn't.
>
> You meant
>
> master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-for-linus-2.6.git
>
> I
Serge Noiraud wrote:
mercredi 17 Août 2005 02:53, George Anzinger wrote/a écrit :
I have put a version of KGDB for x86 RT kernels here:
http://source.mvista.com/~ganzinger/
The common_kgdb_cfi_ stuff creates debug records for entry.S and
friends so that you can "bt" through them. Apply in
On Tue, 6 Sep 2005, James Bottomley wrote:
>
> master.kernel.org:/pub/linux/kernel/scm/jejb/scsi-for-linus-2.6.git
No it isn't.
You meant
master.kernel.org:/pub/scm/linux/kernel/git/jejb/scsi-for-linus-2.6.git
I do believe,
Linus
-
To unsubscribe from this list: send the
On Wed, 07 Sep 2005 22:55:18 +0200, Jiri Slaby <[EMAIL PROTECTED]> wrote:
>>
>>drivers/media/video/zr36120.c: At top level:
>>drivers/media/video/zr36120.c:1821: error: unknown field 'open'
>>specified in initializer
>>> Being discussed on the V4L list
>> It seems that nobody are interested on
"Martin J. Bligh" <[EMAIL PROTECTED]> wrote:
>
>
>
> --On Wednesday, September 07, 2005 11:27:54 -0700 Dave Hansen <[EMAIL
> PROTECTED]> wrote:
>
> > On Wed, 2005-09-07 at 11:22 -0700, Martin J. Bligh wrote:
> >> CONFIG_NUMA was meant to (and did at one point) support both NUMA and flat
> >> ma
2005/9/7, Giridhar Pemmasani <[EMAIL PROTECTED]>:
> Jan Kiszka wrote:
>
> > Ndiswrapper is already slower than native drivers are, also due to
> > horribly implemented Windows drivers btw (the ndis model itself isn't
> > that bad, though).
>
> Do you have any evidence to back your claims? What te
On Wed, Sep 07, 2005 at 03:44:44PM -0700, Andrew Morton wrote:
> Matt Porter <[EMAIL PROTECTED]> wrote:
> >
> > This is the rionet cleanup patch previously posted in reply to Jeff's
> > concerns with this driver. It depends on the rapidio messaging interface
> > updates patch.
>
> Thanks. So are
Hi,
upon insertion of my new 2048 MB usb flash drive, the kernel
(vanilla 2.6.13) spat out the following errors:
usb 4-2: new high speed USB device using ehci_hcd and address 7
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 7
usb-storage: waiting for device to se
On Wed, 2005-09-07 at 17:35 -0500, linas wrote:
> On Fri, Sep 02, 2005 at 01:39:13PM -0700, Dave Hansen was heard to remark:
> > I noticed that my cross-compilation 'make install' broke with 2.6.13 (I
> > don't use it horribly often). It's from this commit:
> >
> > Which added CROSS_COMPILE to ea
Matt Porter <[EMAIL PROTECTED]> wrote:
>
> This is the rionet cleanup patch previously posted in reply to Jeff's
> concerns with this driver. It depends on the rapidio messaging interface
> updates patch.
Thanks. So are there any outstanding issues with the rapidio patches?
-
To unsubscribe from
On Wed, 7 Sep 2005, Kristis Makris wrote:
>> To kill a kernel thread, you need to make __it__ call exit(). It must be
>
> There must be another way to do it. Perhaps one could have another
> process effectively issue the contents of do_exit for the kswapd
> task_struct ?
>
>> CODED to do that! Yo
Grant Grundler writes:
> I would argue it more obvious. People looking at the code
> are immediately going to realize it was a deliberate choice to
> not use a spinlock.
It achieves exactly the same effect as spin_lock/spin_unlock, just
more verbosely. :)
> > and it precludes the sorts of optimi
On Fri, Sep 02, 2005 at 01:39:13PM -0700, Dave Hansen was heard to remark:
> I noticed that my cross-compilation 'make install' broke with 2.6.13 (I
> don't use it horribly often). It's from this commit:
>
> Which added CROSS_COMPILE to each arch's install.sh:
>
> if [ -x ~/bin/${CROSS_COMPILE}i
On Sep 7, 2005, at 17:07:12, Kristis Makris wrote:
To kill a kernel thread, you need to make __it__ call exit(). It
must be
There must be another way to do it. Perhaps one could have another
process effectively issue the contents of do_exit for the kswapd
task_struct ?
Umm, so then the kerne
Now that asm-powerpc/* is using ifdefs on __powerpc64__ we need to add it
to CHECKFLAGS on ppc64.
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-simserial/arch/ppc64/Makefile
RC13-git7-ppc64-sparse/arch/ppc64/Makefile
--- RC13-git7-simserial/arch/ppc64/Makefile 2005-09-05
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-hamachi/drivers/scsi/NCR53c406a.c
RC13-git7-ncr53c406/drivers/scsi/NCR53c406a.c
--- RC13-git7-hamachi/drivers/scsi/NCR53c406a.c 2005-08-28 23:09:45.0
-0400
+++ RC13-git7-ncr53c406/drivers/scsi/NCR53c406a.c 2005-09-0
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-hisax/drivers/net/smc91x.h
RC13-git7-smc-undef/drivers/net/smc91x.h
--- RC13-git7-hisax/drivers/net/smc91x.h2005-08-28 23:09:44.0
-0400
+++ RC13-git7-smc-undef/drivers/net/smc91x.h2005-09-07 13:55:44.0
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-xfs/arch/ia64/hp/sim/simserial.c
RC13-git7-simserial/arch/ia64/hp/sim/simserial.c
--- RC13-git7-xfs/arch/ia64/hp/sim/simserial.c 2005-08-28 23:09:39.0
-0400
+++ RC13-git7-simserial/arch/ia64/hp/sim/simserial.c2005-09
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-ppc64-sparse/arch/um/kernel/mem.c
RC13-git7-uml-mem/arch/um/kernel/mem.c
--- RC13-git7-ppc64-sparse/arch/um/kernel/mem.c 2005-08-28 23:09:40.0
-0400
+++ RC13-git7-uml-mem/arch/um/kernel/mem.c 2005-09-07 13:55:42.
NDEBUG and NDEBUG_ABORT are almost always used as integers in NCR5380; added
define to 0 if they are not defined, switched lone ifdef NDEBUG into if.
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-smc-undef/drivers/scsi/NCR5380.c
RC13-git7-ncr5380/drivers/scsi/NCR5380.c
--- R
CARD_... in hisax are all used with #if; CARD_FN_ENTERNOW_PCI lacks define
to 0 if corresponding config option is not set.
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-uml-mem/drivers/isdn/hisax/hisax.h
RC13-git7-hisax/drivers/isdn/hisax/hisax.h
--- RC13-git7-uml-mem/driver
All uses of ADDRLEN are comparisons with 64 (it's an address width).
added define to 32 (again, we only care about comparisons with 64)
if not defined.
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
diff -urN RC13-git7-ncr5380/drivers/net/hamachi.c
RC13-git7-hamachi/drivers/net/hamachi.c
--- RC1
Jan Kiszka wrote:
> Ndiswrapper is already slower than native drivers are, also due to
> horribly implemented Windows drivers btw (the ndis model itself isn't
> that bad, though).
Do you have any evidence to back your claims? What tests did you do to say
that ndiswrapper is slower than native dri
Hi Tony,
On Wed, Sep 07, 2005 at 02:45:49PM -0700, Luck, Tony wrote:
> I see a lot (90) of warnings when building xfs on ia64. The
Christoph has a patch pending (slightly different approach to
yours) that should resolve this.
cheers.
--
Nathan
-
To unsubscribe from this list: send the line "un
Serge Noiraud wrote:
mercredi 17 Août 2005 02:53, George Anzinger wrote/a écrit :
I have put a version of KGDB for x86 RT kernels here:
http://source.mvista.com/~ganzinger/
The common_kgdb_cfi_ stuff creates debug records for entry.S and
friends so that you can "bt" through them. Apply in
* Janak Desai ([EMAIL PROTECTED]) wrote:
> diff -Naurp linux-2.6.13-mm1/kernel/fork.c
> linux-2.6.13-mm1+unshare-patch1/kernel/fork.c
> --- linux-2.6.13-mm1/kernel/fork.c2005-09-07 13:25:01.0 +
> +++ linux-2.6.13-mm1+unshare-patch1/kernel/fork.c 2005-09-07
> 13:40:11.0
Hi!
> It would seem that swsusp doesn't properly suspend devices, or more
> precisely it wakes them up again before suspending the machine.
Yes, and that's okay.
What happens to devices during swsusp? They seem to be resumed
during system suspend?
A: That's correct. We need to resume them if w
> To kill a kernel thread, you need to make __it__ call exit(). It must be
There must be another way to do it. Perhaps one could have another
process effectively issue the contents of do_exit for the kswapd
task_struct ?
> CODED to do that! You can't do it externally although you can send
I'm cl
John Richard Moser napsal(a):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I get lots of warnings building my kernel. I've attached my .config;
I'm using a kernel I downloaded from kernel.org, unpatched.
[snip]
. . . one of the V4L drivers failed to build too, I turned it off.
drivers
[AIO] kiocb locking to serialise retry and cancel
Implement a per-kiocb lock to serialise retry operations and cancel. This
is done using wait_on_bit_lock() on the KIF_LOCKED bit of kiocb->ki_flags.
Also, make the cancellation path lock the kiocb and subsequently release
all references to it if t
From: Wendy Cheng <[EMAIL PROTECTED]>
Note that other than few exceptions, most of the current filesystem and/or
drivers do not have aio cancel specifically defined (kiob->ki_cancel field
is mostly NULL). However, sys_io_cancel system call universally sets
return code to -EAGAIN. This gives appl
On Wednesday, 7 of September 2005 22:17, Pierre Ossman wrote:
> Rafael J. Wysocki wrote:
>
> >On Wednesday, 7 of September 2005 13:20, Pierre Ossman wrote:
> >
> >
> >>It would seem that swsusp doesn't properly suspend devices, or more
> >>precisely it wakes them up again before suspending the m
On Wed, Sep 07, 2005 at 10:17:49PM +0200, Kars de Jong wrote:
> Yes, you are right. I am working on rewriting the driver a bit to use a
> platform device for the APCI driver, I'll take your bug report into
> account as well.
Thanks.
> On a related note: can I use the "serial8250" platform driver
2005/9/7, Daniel Phillips <[EMAIL PROTECTED]>:
> On Wednesday 07 September 2005 15:52, Daniel Phillips wrote:
> Ah, there's another issue: an interrupt can come in when esp is on the ndis
> stack and above THREAD_SIZE, so do_IRQ will not find thread_info. Sorry,
> this one is nasty.
>
Oh, you al
2005/9/7, Daniel Phillips <[EMAIL PROTECTED]>:
> > > Is there a technical reason ("hard to implement" is a practical reason)
> > > why all stacks need to be the same size?
> >
> > Because of
> >
> > static inline struct thread_info *current_thread_info(void)
> > {
> > struct thread_info *ti
Rafael J. Wysocki wrote:
>On Wednesday, 7 of September 2005 13:20, Pierre Ossman wrote:
>
>
>>It would seem that swsusp doesn't properly suspend devices, or more
>>precisely it wakes them up again before suspending the machine.
>>
>>
>
>Yes, it does. By design.
>
>
>
That seems counter-p
1 - 100 of 281 matches
Mail list logo
