Andrew Morton wrote:
On Wed, 11 Jul 2007 15:30:31 +
"Huang, Ying" <[EMAIL PROTECTED]> wrote:
1. Boot a kernel A
2. Work under kernel A
3. Kexec another kernel B in kernel A
4. Work under kernel B
5. Jump from kernel B to kernel A
6. Continue work under kernel A
This is the first step to
Yinghai Lu wrote:
> Stefan Richter wrote:
>> Yinghai Lu wrote:
>>> original default is -1, and this patch just try to use parent's node as
>>> default.
>>
>> But in many cases, the patch does so at a time when the parent is not
>> yet known.
> then it will use -1.
Yes.
The patch does nothing for
Rusty Russell wrote:
> On Wed, 2007-07-11 at 18:55 +0300, Avi Kivity wrote:
>
>> +fire_sched_out_preempt_hooks(current);
>> prepare_lock_switch(rq, next);
>> prepare_arch_switch(next);
>>
>
> Damn, I just found a use for this in lguest.
>
> Any chance of handing "next" to the
Luca wrote:
> On 7/11/07, Avi Kivity <[EMAIL PROTECTED]> wrote:
>> Current kvm disables preemption while the new virtualization
>> registers are
>> in use. This of course is not very good for latency sensitive
>> workloads (one
>> use of virtualization is to offload user interface and other
Teach do_mpage_readpage() about unwritten extents so we can
always map them in get_blocks rather than they are are holes on
read. Allows setup_swap_extents() to use preallocated files on XFS
filesystems for swap files without ever needing to convert them.
Signed-Off-By: Dave Chinner <[EMAIL
Chuck Ebbert wrote:
> On 07/11/2007 03:08 AM, Avi Kivity wrote:
>
>> Linus, please do your usual thing from the repository and branch at
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git for-linus
>>
>> This contains kvm updates for the 2.6.23 merge window, including
>>
>> -
>> [*] Does someone have an alternative for
>> /proc/acpi/battery/BAT1/{state,info}?
I'm working on it. Should have proto by the end of week.
Regards,
Alex
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Wed, Jul 11, 2007 at 12:44:42PM -0700, Paul Menage wrote:
> >I'm inclined to take the cautious route here - I don't think people will be
> >dying for the CFS thingy (which I didn't even know about?) in .23, and it's
> >rather a lot of infrastructure to add for a CPU scheduler configurator
>
>
Lets run a thought experiment on this notion...
Let's say that the file you want to hide is "/etc/dangerous".
One of your fellows decides to create a file for other purposes
and decides to call it "/etc/dangerous", having looked in /etc
and seeing no file with that name. What should happen
On Wed, 2007-07-11 at 18:55 +0300, Avi Kivity wrote:
> + fire_sched_out_preempt_hooks(current);
> prepare_lock_switch(rq, next);
> prepare_arch_switch(next);
Damn, I just found a use for this in lguest.
Any chance of handing "next" to the sched_out hook so we can optimize
the
On Wed, 2007-07-11 at 20:58 -0400, Gregory Haskins wrote:
> Note also that we find that the resulting kernel does not boot on some
> T60p thinkpads without "acpi=off". We are still investigating the root
> cause here.
Try "nohpet" for now. I'm investigating it on the -hrt side as well.
On 7/11/07, Jesper Juhl <[EMAIL PROTECTED]> wrote:
I'm wondering if it's time to make 4K stacks the default and to start
considering removing the 8K stack option alltogether soon?
Why? Leaving the option for 8k stacks isn't killing any kittens, AFAICS.
-
To unsubscribe from this list: send the
On Jul 11, 2007 16:04 -0400, J. Bruce Fields wrote:
> A 32-bit i_version could in theory wrap pretty quickly, couldn't it?
> That's not a problem in itself--the problem would only arise if two
> subsequent client queries of the change attribute happened a multiple of
> 2^32 i_version increments
On Wed, 2007-07-11 at 21:24 -0700, Andrew Morton wrote:
> We seem to be taking the reference against the wrong thing here. It should
> be against the mm, not against a task_struct?
This is solely for the wakeup: you don't wake an mm 8)
The mm reference is held as well under the big lguest_mutex
Roland McGrath wrote:
This change passes the --build-id when linking the kernel and when
linking modules, if ld supports it. This is a new GNU ld option that
synthesizes an ELF note section inside the read-only data. The note in
this section contains unique identifying bits called the "build
Implement ->page_mkwrite in XFS.
Signed-Off-By: Dave Chinner <[EMAIL PROTECTED]>
---
fs/xfs/linux-2.6/xfs_file.c | 16
1 file changed, 16 insertions(+)
Index: 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_file.c
===
---
Generic page_mkwrite functionality.
Filesystems that make use of the VM ->page_mkwrite() callout will generally use
the same core code to implement it. There are several tricky truncate-related
issues that we need to deal with here as we cannot take the i_mutex as we
normally would for these
Upcoming XFS functionality [1] we plan to merge in 2.6.23-rc1 uses
radix trees and uses the preload functions. XFS can be built as a
module and hence we need radix_tree_preload() exported.
radix_tree_preload_end() is a static inline, so it doesn't need
exporting.
[1]
On Thu, 12 Jul 2007 12:48:41 +1000 Rusty Russell <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-07-11 at 19:28 -0700, David Miller wrote:
> > From: Rusty Russell <[EMAIL PROTECTED]>
> > Date: Thu, 12 Jul 2007 11:21:51 +1000
> >
> > > To do inter-guest (ie. inter-process) I/O you really have to make
On Wed, Jul 11, 2007 at 07:16:34PM +0200, Jesper Juhl wrote:
> Hi,
>
> I'm wondering if it's time to make 4K stacks the default and to start
> considering removing the 8K stack option alltogether soon?
>
> One of the big problem spots was XFS, but that got some stack usage
> fixes recently,
Hi people,
I've looked around on how to hide inodes in a Linux filesystem but
surprisingly the kernel lacks this functionality. It would be desirable
for me to add an ACL to a file in order not to be seen in the directory
contents but only for some users.
Some Selinux experts point out that
From: Rusty Russell <[EMAIL PROTECTED]>
Date: Thu, 12 Jul 2007 13:15:18 +1000
> Sure, the process has /dev/lguest open, so I can do something in the
> close routine. Instead of keeping a reference to the tsk, I can keep a
> reference to the struct lguest (currently it doesn't have or need a
>
Tejun Heo writes:
Please give a shot at the attached patch on top of 2.6.22. Thanks.
Patch applied, but still getting the corruption.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
This is an updated set of 2.6.23 SELinux changes, rebased & tested against
current git. The vmsplice patch has been dropped from this and will be
resubmitted via Jens. Also added an ack from Chris Wright for the mmap
null dereference hooks (which I'd forgotten to add to my tree some time
On Wednesday 11 July 2007 15:09, Neil Brown wrote:
> > > Has anyone fixed the infrequent crashes with 4K stacks and ext3
> > > -> LVM snapshot -> LVM -> DM mirror -> libata?
> >
> > Ahem: ext3 -> LVM snapshot -> LVM -> DM mirror -> DM crypt -> md ->
> > libata, or worse.
> >
> > No, it's not
On Wed, 2007-07-11 at 19:51 -0700, David Miller wrote:
> From: Rusty Russell <[EMAIL PROTECTED]>
> Date: Thu, 12 Jul 2007 12:48:41 +1000
>
> > We drop the lock after I/O, and then do this wakeup. Meanwhile the
> > other task might have exited.
>
> I already understand what you're doing.
>
> Is
Mark Lord wrote:
> I'm not even sure how to interpret those numbers.
> It seems rather odd that nearly all fields are either "100" or "253",
> so those are probably pre-programmed numbers rather than actual counts.
> The raw value at the end of the line (for the various "Reallocated*"
> fields)
>
Nigel Cunningham wrote:
> You'll see from the above numbers that the freezer is not nearly as
> intrusive as you were thinking (~10% of what you wrote above). It is
> limited to code related to kernel threads, and then to either setting a
> flag when the thread is started to say "I don't need to
On Wed, 11 Jul 2007 17:37:31 -0700 Greg KH wrote:
> On Wed, Jul 11, 2007 at 06:01:49PM -0600, Matthew Wilcox wrote:
> > On Wed, Jul 11, 2007 at 04:31:40PM -0700, Greg Kroah-Hartman wrote:
> > > As suggested by Andrew, add pci_try_set_mwi(), which does not require
> > > return-value checking.
> >
Miles Lane wrote:
> Does this patch replace or add to the last patch you sent me?
> I'll try applying them with --dry-run and assume that if #1 + #2
> doesn't apply cleanly, then you only want me to test with this
> latest patch.
This replaces the old one. Just revert the old one and apply this
YOSHIFUJI Hideaki / 吉藤英明 wrote:
> In article <[EMAIL PROTECTED]> (at Wed, 11 Jul 2007 16:55:29 -0700), Greg KH
> <[EMAIL PROTECTED]> says:
>
>> On Thu, Jul 12, 2007 at 08:50:47AM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@
>> wrote:
>>> In article <[EMAIL PROTECTED]> (at Wed, 11 Jul 2007 16:31:43
Stefan Richter wrote:
Yinghai Lu wrote:
original default is -1, and this patch just try to use parent's node as
default.
But in many cases, the patch does so at a time when the parent is not
yet known.
then it will use -1.
YH
-
To unsubscribe from this list: send the line "unsubscribe
On Wed, 2007-07-11 at 18:55 +0300, Avi Kivity wrote:
> +config PREEMPT_HOOKS
> + bool
> + depends on X86
> + default y
Hmm, I would have thought that having CONFIG_KVM "select PREEMPT_HOOKS"
would be a little clearer.
> +static void fire_sched_in_preempt_hooks(struct task_struct
On Wed, 2007-07-11 at 15:58 -0700, Linus Torvalds wrote:
>
> On Wed, 11 Jul 2007, Chris Wright wrote:
> >
> > That's not quite right. Leaving the code unchanged caused breakage
> > already. The PIT is damn stupid and can be sensitive to how quickly it's
> > programmed. So code that
From: Rusty Russell <[EMAIL PROTECTED]>
Date: Thu, 12 Jul 2007 12:48:41 +1000
> We drop the lock after I/O, and then do this wakeup. Meanwhile the
> other task might have exited.
I already understand what you're doing.
Is it possible to use exit notifiers to handle this case?
That's what I'm
On Wed, 2007-07-11 at 19:28 -0700, David Miller wrote:
> From: Rusty Russell <[EMAIL PROTECTED]>
> Date: Thu, 12 Jul 2007 11:21:51 +1000
>
> > To do inter-guest (ie. inter-process) I/O you really have to make sure
> > the other side doesn't go away.
>
> You should just let it exit and when it
Yinghai Lu wrote:
> original default is -1, and this patch just try to use parent's node as
> default.
But in many cases, the patch does so at a time when the parent is not
yet known.
--
Stefan Richter
-=-=-=== -=== -==--
http://arcgraph.de/sr/
-
To unsubscribe from this list: send the line
David Chinner wrote:
On Thu, Jul 12, 2007 at 10:54:57AM +1000, Nick Piggin wrote:
Andrew Morton wrote:
The fault-vs-invalidate race fix. I have belatedly learned that these
need
more work, so their state is uncertain.
The more work may turn out being too much for you (although it is
Roland McGrath wrote:
The earlier patches in this series change the linker script to place it
appropriately and set the phdr. It's allocated when its input sections are
allocated. Current builds I've seen don't have any input note sections at
all. My motivation is for the ld --build-id
On Thu, Jul 12, 2007 at 10:54:57AM +1000, Nick Piggin wrote:
> Andrew Morton wrote:
> > The fault-vs-invalidate race fix. I have belatedly learned that these
> > need
> > more work, so their state is uncertain.
>
> The more work may turn out being too much for you (although it is nothing
>
From: Miklos Szeredi <[EMAIL PROTECTED]>
Date: Wed, 04 Jul 2007 11:49:41 +0200
> Throw out the old mark & sweep garbage collector and put in a
> refcounting cycle detecting one.
>
> The old one had a race with recvmsg, that resulted in false positives
> and hence data loss. The old algorithm
Mike Christie wrote:
I think you needed some other bits in there. See this patch
I tried just setting the bufflen first, and that still had problems.
Could you try the patch here
http://marc.info/?l=linux-scsi=117392208211297=2
I just read the thread.. I didn't see any strange retries with
From: Rusty Russell <[EMAIL PROTECTED]>
Date: Thu, 12 Jul 2007 11:21:51 +1000
> To do inter-guest (ie. inter-process) I/O you really have to make sure
> the other side doesn't go away.
You should just let it exit and when it does you receive some kind of
exit notification that resets your
On Thu, 2007-07-12 at 00:58 +, Gregory Haskins wrote:
> Hi Ingo, Thomas, and the greater linux-rt community,
>
> I just wanted to let you guys know that our team has a port of the
> 21.5-rt20 patch for the 2.6.22 kernel available.
FYI: Due to an internal mis-communication I thought
On Wed, 2007-07-11 at 14:23 +0200, Christoph Hellwig wrote:
> > lguest-export-symbols-for-lguest-as-a-module.patch
>
> __put_task_struct is one of those no way in hell should this be exported
> things because we don't want modules messing with task lifetimes.
>
> Fortunately I can't find
Bodo Eggert wrote:
>
>> That being said, one could argue that since this is a BIOS interface it
>> should be queried via INT 16h, AH=02h and stuffed in the zeropage
>> structure. This would also solve the issue of it not being supported by
>> non-BIOS firmware.
>
> This is an interesting
On Sun, 8 Jul 2007, James Morris wrote:
> Revalidate read/write permissions for splice(2) and vmslice(2), in case
> security policy has changed since the files were opened.
This patch clashes with changes which came in via Jens (who I'll submit
the patch via once it's fixed).
I'll send an
On Thu, 12 Jul 2007 03:40:04 +0200 (CEST) Bodo Eggert wrote:
> If you build using O=builddir ARCH=bar, you'll currently need to supply
> ARCH= on builds from the builddir, too. With this patch, the generated
> Makefile will do that instead.
>
> make ARCH= will still override the Makefile
On Thu, Jul 12, 2007 at 03:40:04AM +0200, Bodo Eggert wrote:
> If you build using O=builddir ARCH=bar, you'll currently need to supply
> ARCH= on builds from the builddir, too. With this patch, the generated
> Makefile will do that instead.
> diff -X dontdiff -pruN
On Wed, 2007-07-11 at 18:54 -0600, Matthew Wilcox wrote:
> On Wed, Jul 11, 2007 at 05:39:23PM -0700, Greg KH wrote:
> > > This seems like a regression. We go from having an empty inline
> > > function that gets optimised away to 0 to having a function call to a
> > > trivial function. And on any
On Wed, 11 Jul 2007, H. Peter Anvin wrote:
> Bodo Eggert wrote:
> > Instead of the byte at 0x497 as suggested in that thread, I'm using the
> > byte at 0x417, which reflects the intended LED state. In order to change
> > the keyboard LED, DOS programs would change this byte and call INT 5
> >
If you build using O=builddir ARCH=bar, you'll currently need to supply
ARCH= on builds from the builddir, too. With this patch, the generated
Makefile will do that instead.
make ARCH= will still override the Makefile default, allowing existing
scripts to work correctly.
Signed-Off-By: Bodo
It happened that this weird behavior was caused by gcc-4.2 compiler.
After recompiling the kernel with gcc-4.1 all troubles have gone.
Max
On 7/11/07, Max Alekseyev <[EMAIL PROTECTED]> wrote:
Hello!
I have trouble with booting linux kernel 2.6.22 from kernel.org on my
AMD dual-Opteron 250
On Thu, 12 Jul 2007 01:56:32 +0200
Michael Buesch <[EMAIL PROTECTED]> wrote:
> This fixes
>
> drivers/char/rocket.c: In function ‘rp_write’:
> drivers/char/rocket.c:1705: warning: ignoring return value of
> ‘mutex_lock_interruptible’, declared with attribute warn_unused_result
>
>
On Wed, 11 Jul 2007 17:37:31 -0700 Greg KH wrote:
> On Wed, Jul 11, 2007 at 06:01:49PM -0600, Matthew Wilcox wrote:
> > On Wed, Jul 11, 2007 at 04:31:40PM -0700, Greg Kroah-Hartman wrote:
> > > As suggested by Andrew, add pci_try_set_mwi(), which does not require
> > > return-value checking.
> >
Jeremy Linton wrote:
Any function which use scsi_execute_async() and transfers "odd" sized
data that doesn't align correctly with the segment sizes may have its
transfer length padded out to the closest segment size.
For writes, this results in unnecessary data being transfered to the
SCSI
On Wed, 2007-07-11 at 16:45 +0300, Muli Ben-Yehuda wrote:
> Andi, please consider applying for 2.6.23. Applies on top of the
> Calgary update I just sent out ("Calgary: more updates for 2.6.23").
>
> This patch introduces struct pci_sysdata to x86 and x86-64, and
> converts the existing two users
On Wed, 2007-07-11 at 14:42 +0200, Richard Mittendorfer wrote:
> Greetings *!
>
> I'm looking for a way to disable (PM low power mode) some devices I
> rarely/never use on my laptop to save some more power. With 2.6.17,
> IIRC, I was able to echo -n 2 > /sys/bus/pci/../power to put things
> into
On Wed, 2007-07-11 at 20:58 -0400, Gregory Haskins wrote:
> Hi Ingo, Thomas, and the greater linux-rt community,
>
> I just wanted to let you guys know that our team has a port of the
> 21.5-rt20 patch for the 2.6.22 kernel available. It in no way should be
> construed as a substitute
Andrew,
Attached is the patch that addresses all your comments except moving the
lock around blk_execute_rq_nowait(). Moving the lock ahead makes the
function to return more than one place (which is what I was trying to
avoid earlier). Let me now if you prefer it that way.
Thanks,
chandra
On
Christoph Lameter wrote:
>
> This may be a leftover from earlier times when the logic was different in
> throttle vm writeout?
Sorry -- my merge error when looking at an earlier kernel, no issue
with mainline or -mm.
-- Ethan
-
To unsubscribe from this list: send the line
In article <[EMAIL PROTECTED]> (at Wed, 11 Jul 2007 16:55:29 -0700), Greg KH
<[EMAIL PROTECTED]> says:
> On Thu, Jul 12, 2007 at 08:50:47AM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@
> wrote:
> > In article <[EMAIL PROTECTED]> (at Wed, 11 Jul 2007 16:31:43 -0700), Greg
> > Kroah-Hartman <[EMAIL
Remove the rmb() from mce_log(), since the immunized version of
rcu_dereference() makes it unnecessary.
Signed-off-by: Paul E. McKenney <[EMAIL PROTECTED]>
---
mce.c |3 ---
1 file changed, 3 deletions(-)
diff -urpNa -X dontdiff linux-2.6.22-volrcud/arch/x86_64/kernel/mce.c
The OPEN_MAX macro in limits.h should not be there. It claims to be the
limit on file descriptors in a process, but its value is wrong for that.
There is no constant value, but a variable resource limit (RLIMIT_NOFILE).
Nothing in the kernel uses OPEN_MAX except things that are wrong to do so.
Turns out that compiler writers are a bit more aggressive about optimizing
than one might expect. This patch prevents a number of such optimizations
from messing up rcu_deference(). This is not merely a theoretical
problem, as evidenced by the rmb() in mce_log().
Signed-off-by: Paul E. McKenney
The CHILD_MAX macro in limits.h should not be there. It claims to be the
limit on processes a user can own, but its value is wrong for that.
There is no constant value, but a variable resource limit (RLIMIT_NPROC).
Nothing in the kernel uses CHILD_MAX.
The proper thing to do according to POSIX
The OPEN_MAX constant is an arbitrary number with no useful relation to
anything. Nothing should be using it. SCM_MAX_FD is just an arbitrary
constant and it should be clear that its value is chosen in net/scm.h
and not actually derived from anything else meaningful in the system.
Bodo Eggert wrote:
>
> Instead of the byte at 0x497 as suggested in that thread, I'm using the
> byte at 0x417, which reflects the intended LED state. In order to change
> the keyboard LED, DOS programs would change this byte and call INT 5
> (which is the keyboard software interrupt).
>
Any function which use scsi_execute_async() and transfers "odd" sized
data that doesn't align correctly with the segment sizes may have its
transfer length padded out to the closest segment size.
For writes, this results in unnecessary data being transfered to the
SCSI target. For reads, it
Alessandro Zummo wrote:
On Wed, 11 Jul 2007 22:53:01 +
Alex Maclean <[EMAIL PROTECTED]> wrote:
I'm unsure just what hardware you're working with, but try using the
option nolapic_timer.
it worked, thanks!
hw is a Dell Inspiron 1501, AMD Turion TL52 based.
drop me a note if you need
Andrew Morton wrote:
mm-fix-fault-vs-invalidate-race-for-linear-mappings.patch
mm-merge-populate-and-nopage-into-fault-fixes-nonlinear.patch
mm-merge-nopfn-into-fault.patch
convert-hugetlbfs-to-use-vm_ops-fault.patch
mm-remove-legacy-cruft.patch
* Andi Kleen ([EMAIL PROTECTED]) wrote:
> Ok by me, although I suspect a lot of the cases where the hpet one
> was needed got resolved with the PCI HPET resource fix But it's still
> safer to check.
>
> However I don't think patches should go into stable before they
> hit Linus' tree.
Agreed,
On Wed, Jul 11, 2007 at 05:39:23PM -0700, Greg KH wrote:
> > This seems like a regression. We go from having an empty inline
> > function that gets optimised away to 0 to having a function call to a
> > trivial function. And on any architecture that *does* define this,
> > (unless I
> Is .notes an allocated section? I didn't think it necessarily appeared
> in any of the PT_LOAD segments, because the linux/elfnote.h macros don't
> necessarily set "a" on the section.
The earlier patches in this series change the linker script to place it
appropriately and set the phdr.
On Thursday 12 July 2007 02:04, Thomas Gleixner wrote:
> Andrew,
>
> On Wed, 2007-07-11 at 16:57 -0700, Andrew Morton wrote:
> > They all look pretty innocuous to me.
> >
> > Could you please take a second look, decide if any of them should also be
> > in 2.6.22.x and let me know?
>
>
Linus has decreed the evil of typedefs in the kernel, and the DRM is
the proud winner of the "HEY MA: I CAN USE TYPEDEF" award,
So I've cleaned up most of the typedefs in the Linux drm core (I did
this in the kernel tree as I'd like to push it there first and
backport it to the hell of the DRM
Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 11 Jul 2007 22:01:59 +0100
> Alasdair G Kergon <[EMAIL PROTECTED]> wrote:
>
> > From: Mike Anderson <[EMAIL PROTECTED]>
> >
> > This patch adds support for the dm_path_event dm_send_event funtions which
> > create and send netlink attribute
On Wed, Jul 11, 2007 at 06:01:49PM -0600, Matthew Wilcox wrote:
> On Wed, Jul 11, 2007 at 04:31:40PM -0700, Greg Kroah-Hartman wrote:
> > As suggested by Andrew, add pci_try_set_mwi(), which does not require
> > return-value checking.
>
> Seems like a daft suggestion. What's wrong with just
On Wed, Jul 11, 2007 at 05:49:22PM -0600, Matthew Wilcox wrote:
> On Wed, Jul 11, 2007 at 04:31:19PM -0700, Greg Kroah-Hartman wrote:
> > I'm not sure if this is going to fly, weak symbols work on the compilers I'm
> > using, but whether they work for all of the affected architectures I can't
> >
On Thu, Jul 12, 2007 at 02:18:07AM +0200, Ingo Molnar wrote:
> > > i dont think "clean, modern x86 code" will ever happen - x86_64 has
> > > and is going to have the exact same type of crap. And i'll say a
> > > weird thing
> >
> > Yes, but it will be new crap, but no old crap anymore.
> >
> >
> I'm curios to know what happens if nobody defines __start_notes and
> __end_notes. We'll use the extern-attribute-weak thing, but those two
> locations won't even get instantiated in vmlinux, I think.
>
> And the code relies upon the difference between two non-existent
> attribute-weak
Pekka J Enberg wrote:
Hi Christoph,
On Wed, 11 Jul 2007, Christoph Lameter wrote:
Of course you are the maintainer but you only authored a single patch
which was the original submission in all the time that SLOB was in the
tree. I keep having to clean up the allocator that has--according to
On Thu, 12 Jul 2007 01:59:23 +0200
Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> > Andi, any objections against the above i386 fixlets ?
>
> No, they are fine for me.
>
OK, I queued them up for an akpm->linus transfer. Which will of course be
abandoned if an akpm->andi or andi->linus merge
On Tue, 2007-07-10 at 23:20 -0700, Andrew Morton wrote:
> On Sun, 01 Jul 2007 03:38:59 -0400 Mingming Cao <[EMAIL PROTECTED]> wrote:
>
> > From: Dmitry Monakhov <[EMAIL PROTECTED]>
> > Subject: ext4: extent macros cleanup
> >
> > - Replace math equation to it's macro equivalent
>
>
On Thu, Jul 12, 2007 at 02:09:37AM +0200, Ingo Molnar wrote:
>
> * Paul E. McKenney <[EMAIL PROTECTED]> wrote:
>
> > Hello!
> >
> > Just work in progress, not recommended for inclusion. Seems stable
> > under rigorous rcutorture testing, so should be OK for
> > experimentation.
>
> nice
Pavel Emelianov [EMAIL PROTECTED] wrote:
| We must pass the namespace pointer to the alloc_pid() to
| show what namespace to allocate the pid from and we should
| call this *after* the namespace is copied.
|
| Essentially, the task->pid etc initialization is done after
| the alloc_pid().
|
| To
On Wed, 11 Jul 2007 15:30:31 +
"Huang, Ying" <[EMAIL PROTECTED]> wrote:
> Kexec base hibernation has some potential advantages over uswsusp and
> suspend2. Some most obvious advantages are:
>
> 1. The hibernation image size can exceed half of memory size easily.
> 2. The hibernation image
Christoph H. says this stands on its own and can go in before the
rest of the r/o bind mount set.
---
Some filesystems forego the vfs and may_open() and create their
own 'struct file's.
This patch creates a couple of helper functions which can be
used by these filesystems, and will provide a
This is the first really tricky patch in the series. It
elevates the writer count on a mount each time a
non-special file is opened for write.
This is not completely apparent in the patch because the
two if() conditions in may_open() above the
mnt_want_write() call are, combined, equivalent to
chown/chmod,etc... don't call permission in the same way
that the normal "open for write" calls do. They still
write to the filesystem, so bump the write count during
these operations.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/open.c | 39
Some ioctl()s can cause writes to the filesystem. Take
these, and make them use mnt_want/drop_write() instead.
We need to pass the filp one layer deeper in XFS, but
somebody _just_ pulled it out in February because nobody
was using it, so I don't feel guilty for adding it back.
Signed-off-by:
It is OK to let access() go without using a mnt_want/drop_write()
pair because it doesn't actually do writes to the filesystem,
and it is inherently racy anyway. This is a rare case when it is
OK to use __mnt_is_readonly() directly.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
* Andi Kleen <[EMAIL PROTECTED]> wrote:
> > i dont think "clean, modern x86 code" will ever happen - x86_64 has
> > and is going to have the exact same type of crap. And i'll say a
> > weird thing
>
> Yes, but it will be new crap, but no old crap anymore.
>
> If you always pile the new crap
Some ioctls need write access, but others don't. Make a helper
function to decide when write access is needed, and take it.
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/ncpfs/ioctl.c | 55 +-
1 file changed, 54 insertions(+), 1
* Thomas Gleixner ([EMAIL PROTECTED]) wrote:
> Andrew,
>
> On Wed, 2007-07-11 at 16:57 -0700, Andrew Morton wrote:
> > They all look pretty innocuous to me.
> >
> > Could you please take a second look, decide if any of them should also be
> > in 2.6.22.x and let me know?
>
>
If we depend on the inodes for writeability, we will not
catch the r/o mounts when implemented.
This patches uses __mnt_want_write(). It does not guarantee
that the mount will stay writeable after the check. But,
this is OK for one of the checks because it is just for a
printk().
The other
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/namei.c |4
lxc-dave/ipc/mqueue.c |5 -
2 files changed, 8 insertions(+), 1 deletion(-)
diff -puN fs/namei.c~elevate-mnt-writers-for-vfs-unlink-callers fs/namei.c
---
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/utimes.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
diff -puN fs/utimes.c~elevate-write-count-for-do-utimes fs/utimes.c
--- lxc/fs/utimes.c~elevate-write-count-for-do-utimes 2007-07-10
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/inode.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff -puN fs/inode.c~elevate-write-count-for-do-sys-utime-and-touch-atime
fs/inode.c
---
Signed-off-by: Dave Hansen <[EMAIL PROTECTED]>
---
lxc-dave/fs/open.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff -puN fs/open.c~elevate-writer-count-for-do-sys-truncate fs/open.c
--- lxc/fs/open.c~elevate-writer-count-for-do-sys-truncate 2007-07-10
1 - 100 of 1441 matches
Mail list logo
