Andi Kleen <[EMAIL PROTECTED]> wrote:
>> couldn't this be fixed by bumping idle tasks to middle while they hold a
>
> Usually to high.
Then use the lowest non-idle priority. The result will not be more b0rken
than nice -n 19.
> But it's all complicated and hasn't been done consistently
> (there
Jerry Jiang <[EMAIL PROTECTED]> wrote:
> On Wed, 8 Aug 2007 21:18:25 -0700 (PDT)
>> On Wed, 8 Aug 2007, Chris Snook wrote:
>> > Some architectures currently do not declare the contents of an atomic_t to
>> > be
>> > volatile. This causes confusion since atomic_read() might not actually
>> > read
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> On Aug 9 2007 11:31, Stephen Hemminger wrote:
>>Since the network device documentation needs a rewrite, I was thinking
>>of using basic html format instead of just plain text. But since this would
>>be starting an new precedent for kernel documentation,
On Thu, 9 Aug 2007, Jan Engelhardt wrote:
> On Aug 9 2007 14:34, Bodo Eggert wrote:
> >I don't think and should be used, instead you should use styles
> >( etc).
>
> does the same as , and the latter is much
> more verbose for the same thing.
You shoud use neith
Eric Sandeen <[EMAIL PROTECTED]> wrote:
> This attempts to address CVE-2006-6058
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6058
>
> first reported at http://projects.info-pull.com/mokb/MOKB-17-11-2006.html
>
> Essentially a corrupted minix dir inode reporting a very large
> i_siz
Miklos Szeredi <[EMAIL PROTECTED]> wrote:
>> > This is needed to be able to correctly implement open-unlink-fsetattr
>> > semantics in some filesystem such as sshfs, without having to resort
>> > to "silly-renaming".
>>
>> How do you plan to do that?
>
> Easy: the SFTP protocol has stateful open
Rene Herman <[EMAIL PROTECTED]> wrote:
> I must say I've been wondering about relatime a bit as well. Are there
> actually users who do really want atime, but not badly enough to want real
> atime?
Anyone using /var/spool/mail.
--
Programming is an art form that fights back.
Friß, Spammer: [EM
On Mon, 13 Aug 2007, Eric Sandeen wrote:
> Bodo Eggert wrote:
> > Warning: I'm only looking at the patch.
> >
> > You are supposed to print an error message for a user, not to write in a
> > chat window to a 1337 script kiddie. OK, you just matched the current styl
Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> On 15/08/07, Zoltan Boszormenyi <[EMAIL PROTECTED]> wrote:
>> I noticed that a bad CD of mine makes DMA disabled:
[...]
>> hda: cdrom_decode_status: error=0x40 { LastFailedSense=0x04 }
>> ide: failed opcode was: unknown
>> hda: DMA disabled
>> hda: i
Miguel Botón <[EMAIL PROTECTED]> wrote:
> This patch fixes the warnings "passing argument 1 of '__memcpy' discards
> qualifiers from pointer target type" and "passing argument 2 of '__memcpy'
> discards qualifiers from pointer target type" when compiling some files.
>
> I don't really know if thi
Andi Kleen <[EMAIL PROTECTED]> wrote:
> Stefan Monnier <[EMAIL PROTECTED]> writes:
>> The main use for me is to deal with dangling connections due to taking
>> network interfaces up&down with different IP addresses (typically the wlan0
>> interface where the IP is different because I've modes from
Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> On 10/16/07, Kristoffer Ericson <[EMAIL PROTECTED]> wrote:
>> Is the suggested approach on handling powerbutton (in keyboard driver) to
>> simply push out the event and let userland handle it?
>
> Yes.
>
>> The reason Im asking this is because as you
Al Viro <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 26, 2007 at 11:23:53AM -0700, John Johansen wrote:
>> In the current code, both vfsmounts are always identical, and so one of
>> the two should go, agreed.
>>
>> The thought behind passing both vfsmounts was that they could differ but
>> point to t
On Sat, 13 Jan 2007, Bill Davidsen wrote:
> Bodo Eggert wrote:
>
> > (*) This would allow fadvise_size(), too, which could reduce fragmentation
> > (and give an early warning on full disks) without forcing e.g. fat to
> > zero all blocks. OTOH, fadvise_size() woul
Bill Davidsen <[EMAIL PROTECTED]> wrote:
> My point is, that there is code to handle sparse data now, without
> O_DIRECT involved, and if O_DIRECT bypasses that, it's not a problem
> with the idea of O_DIRECT, the kernel has a security problem.
The idea of O_DIRECT is to bypass the pagecache, and
Helge Hafting <[EMAIL PROTECTED]> wrote:
> Michael Tokarev wrote:
>> But seriously - what about just disallowing non-O_DIRECT opens together
>> with O_DIRECT ones ?
>>
> Please do not create a new local DOS attack.
> I open some important file, say /etc/resolv.conf
> with O_DIRECT and just sit
On Tue, 16 Jan 2007, Arjan van de Ven wrote:
> On Tue, 2007-01-16 at 21:26 +0100, Bodo Eggert wrote:
> > Helge Hafting <[EMAIL PROTECTED]> wrote:
> > > Michael Tokarev wrote:
> > >> But seriously - what about just disallowing non-O_DIRECT open
Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
> On 1/18/07, Russell King <[EMAIL PROTECTED]> wrote:
>> On Thu, Jan 18, 2007 at 01:58:52PM +0100, Bernhard Walle wrote:
>> > 2. Set command_line as __initdata.
>> You can't.
>>
>> > -static char command_line[COMMAND_LINE_SIZE];
>> > +static char __initdata
Tony Foiani <[EMAIL PROTECTED]> wrote:
>> "David" == David Schwartz <[EMAIL PROTECTED]> writes:
> Just last night I formatted some new "500GB" drives, and they
> eventually came back with 465GB as the displayed capacity. Wouldn't
> it make more sense to display that as "465GiB"?
[...]
> Dav
On Mon, 22 Jan 2007, Tony Foiani wrote:
> > "Jan" == Jan Engelhardt <[EMAIL PROTECTED]> writes:
>
> Jan> For "F"s sake, when you gotta use abbreviations, then just use
> Jan> k=1000 and K=1024 already, b for bits and B for bytes. Problem
> Jan> gone.
>
>The one-letter abbreviations are i
Scott Preece <[EMAIL PROTECTED]> wrote:
> My own hot button is making sure that the definition of what
> constitutes user activity is managed in exactly one place, whether in
> the kernel or not. My naive model would be to put the response at user
> level, but to provide a single point of definiti
Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-01-24 at 22:22 +0800, Aubrey Li wrote:
>> On 1/24/07, Peter Zijlstra <[EMAIL PROTECTED]> wrote:
>> > He wants to make a nommu system act like a mmu system; this will just
>> > never ever work.
>>
>> Nope. Actually my nommu system works grea
Jörn Engel <[EMAIL PROTECTED]> wrote:
> On Wed, 20 December 2006 20:32:20 +0200, Yakov Lerner wrote:
>> Is it easily possible to build two architectures in
>> the same source tree (so that intermediate fles
>> and resut files do not interfere ) ?
>
> I'd try something like this:
> make O=../foo A
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> On Dec 29 2006 07:57, Daniel Marjamäki wrote:
>> It was my goal to improve the readability. I failed.
>>
>> I personally prefer to use standard functions instead of writing code.
>> In my opinion using standard functions means less code that is easier to
David Weinehall <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 02, 2007 at 08:22:21AM -0500, Robert P. J. Day wrote:
>> 1) mcdonald's was not merely serving their coffee "hot," but
>> *scalding* hot (180 to 190 degrees Fahrenheit), a temperature that
>> will produce third-degree burns almost immediately
Dave Jones <[EMAIL PROTECTED]> wrote:
> Shrink the held_lock struct by using bitfields.
> This shrinks task_struct on lockdep enabled kernels by 480 bytes.
> * The following field is used to detect when we cross into an
> * interrupt context:
> */
> - int irq_co
Rik van Riel <[EMAIL PROTECTED]> wrote:
+++ linux-2.6.20.noarch/mm/swap.c2007-02-20 06:44:17.0 -0500
@@ -420,6 +420,26 @@ void pagevec_strip(struct pagevec *pvec)
> +if (printk_ratelimit())
> +printk("kswapd freed a swap spac
On Sat, 3 Feb 2007, Alan wrote:
> Bodo Eggert <[EMAIL PROTECTED]> wrote:
> > This patch changes the module license handling code to:
> > - allow modules to have multiple licenses
>
> NAK
I still think it would be a good idea, but if too many people misinterpret
my
Al Boldi <[EMAIL PROTECTED]> wrote:
> Doing the following results in an incomplete vmlinuz:
> # make bzlilo
>
> objcopy: arch/i386/boot/compressed/vmlinux.bin: File truncated
> make[2]: *** [arch/i386/boot/compressed/vmlinux.bin] Error 1
> make[1]: *** [arch/i386/boot/compressed/vmlinux] Error 2
v j <[EMAIL PROTECTED]> wrote:
> On 2/14/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
>> On Wed, 2007-02-14 at 21:16 -0800, v j wrote:
>> > This is in reference to the following thread:
>> >
>> > http://lkml.org/lkml/2006/12/14/63
>> >
>> > I am not sure if this is ever addressed in LKML, but l
Andi Kleen <[EMAIL PROTECTED]> wrote:
> Now if it's better to set up a empty node or use a nearby node
> for a memory less cpu can be further discussed. I still think
> I lean towards the later.
Worst case: Only slot 0 is used. Plug your memoryless CPU card into the last
slot before your plug the
Sergei Organov <[EMAIL PROTECTED]> wrote:
> Linus Torvalds <[EMAIL PROTECTED]> writes:
>> Exactly because "char" *by*definition* is "indeterminate sign" as far as
>> something like "strlen()" is concerned.
>
> Thanks, I now understand that you either don't see the difference
> between "indetermin
v j <[EMAIL PROTECTED]> wrote:
> So far I have heard nothing but, "if you don't contribute, screw you."
That's exactly what you tell to the linux community: If they don't contribute
to your project *FOR*NOTHING*IN*RETURN*, you'll punish them by - stamping
your feet, crying out loud and *paying* f
On Fri, 16 Feb 2007, Sergei Organov wrote:
> Bodo Eggert <[EMAIL PROTECTED]> writes:
> > Sergei Organov <[EMAIL PROTECTED]> wrote:
> >> Linus Torvalds <[EMAIL PROTECTED]> writes:
> [...]
> > Using signed chars for strings is wrong in most countries on
On Fri, 16 Feb 2007, Sergei Organov wrote:
> Bodo Eggert <[EMAIL PROTECTED]> writes:
> > Sergei Organov <[EMAIL PROTECTED]> wrote:
> >> Linus Torvalds <[EMAIL PROTECTED]> writes:
> > If you don't code for a specific compiler with specific settin
Roman Zippel <[EMAIL PROTECTED]> wrote:
> On Thu, 15 Feb 2007, David Howells wrote:
>> > This is really the weak point - it offers no advantage over an equivalent
>> > implementation in user space (e.g. in the module tools). So why has to be
>> > done in the kernel?
>>
>> Because the init_module(
Fengguang Wu <[EMAIL PROTECTED]> wrote:
> The new/old ra class were implicitly stored in low bits of
> file_ra_state.flags. Now make the data structure obvious, and remove the
> coding tricks.
> +++ linux-2.6.20-rc4-mm1/include/linux/fs.h
> - unsigned long flags;/* RA_FLAG_xxx | ra_class
Denis Vlasenko <[EMAIL PROTECTED]> wrote:
> On Friday 26 January 2007 19:23, Bill Davidsen wrote:
>> Denis Vlasenko wrote:
>> > On Thursday 25 January 2007 21:45, Michael Tokarev wrote:
>> >> But even single-threaded I/O but in large quantities benefits from
>> >> O_DIRECT significantly, and I poi
Eriberto <[EMAIL PROTECTED]> wrote:
> I am trying understand the swap. I would like to know which is the
> maximum swap size on i386. Is 64 MB? If yes, how to know the origin of
> this "magic" number? I don't found it (Internet).
Look into the manpage of mkswap. It's 2 G x 32 swap partitions,
min
Dave Jones <[EMAIL PROTECTED]> wrote:
> On Fri, Jan 12, 2007 at 05:58:41PM -0500, [EMAIL PROTECTED] wrote:
> > jengelh> What: RAW driver (CONFIG_RAW_DRIVER)
> > jengelh> When: December 2005
> > jengelh> Why:declared obsolete since kernel 2.6.3
> > jengelh> O_DIRECT can
Jeff Layton <[EMAIL PROTECTED]> wrote:
> This patch updates pipefs to do defer assigning an i_ino value to its inodes
> until someone actually tries to stat it. This allows us to have unique i_ino
> values for the inodes here, without the performance impact for anyone who
> doesn't actually care a
change pipefs to use a unique inode number equal to the memory
address unless it would be truncated.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
---
Tested on i386.
--- 2.6.19/fs/pipe.c.ori2007-01-30 22:02:46.0 +0100
+++ 2.6.19/fs/pipe.c2007-01-30 23:22:27.0
es)
- move the ndiswrapper check into the new license checking routine
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
---
The license handling code was kind of strange:
- The kernel itself would only consider the first license, while modpost
looks at all of them.
- If you offer your mo
On Sat, 3 Feb 2007, Jan Engelhardt wrote:
> On Feb 3 2007 03:08, Bodo Eggert wrote:
> >This patch changes the module license handling code to:
> >- allow modules to have multiple licenses
> >- access GPL symbols if at least one license is GPL-compatible
>
> I strong
Alan <[EMAIL PROTECTED]> wrote:
> On Fri, 01 Dec 2006 16:20:46 +0100
> Jan Glauber <[EMAIL PROTECTED]> wrote:
>> Yes, a user can just symlink urandom to prandom and will have a faster
>> generator.
>
>
> More usefully they can use it as an entropy source with an entropy
> daemon to feed it into
Michael Tokarev <[EMAIL PROTECTED]> wrote:
> I wonder why open() with O_DIRECT (for example) bit set is
> disallowed on a tmpfs (again, for example) filesystem,
> returning EINVAL.
>
> Yes, the question may seems strange a bit, because of two
> somewhat conflicting reasons. First, there's no rea
Eric Sandeen <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
>> +++ a/fs/bad_inode.c
>> -static int return_EIO(void)
>> +static long return_EIO(void)
> What about ops that return loff_t (64 bits) on 32-bit arches and stuff
> it into 2 registers
*If* it uses an additional register for the
Pavel Machek <[EMAIL PROTECTED]> wrote:
>> Another idea is to export the filesystem internal ID as an arbitray
>> length cookie through the extended attribute interface. That could be
>> stored/compared by the filesystem quite efficiently.
>
> How will that work for FAT?
> Or maybe we can relax
Miklos Szeredi <[EMAIL PROTECTED]> wrote:
>> > Well, sort of. Samefile without keeping fds open doesn't have any
>> > protection against the tree changing underneath between first
>> > registering a file and later opening it. The inode number is more
>>
>> You only need to keep one-file-per-har
Amit Choudhary <[EMAIL PROTECTED]> wrote:
> --- Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>> On Sun, Jan 07, 2007 at 12:46:50AM -0800, Amit Choudhary wrote:
>> > Well, I am not proposing this as a debugging aid. The idea is about correct
>> > programming,
>> atleast
>> > from my view. Ideally,
Nick Piggin <[EMAIL PROTECTED]> wrote:
> Aubrey wrote:
>> On 1/11/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
>>> What you _really_ want to do is avoid large mallocs after boot, or use
>>> a CPU with an mmu. I don't think nommu linux was ever intended to be a
>>> simple drop in replacement for a no
Linus Torvalds <[EMAIL PROTECTED]> wrote:
> On Sat, 13 Jan 2007, Michael Tokarev wrote:
>> (No, really - this load isn't entirely synthetic. It's a typical database
>> workload - random I/O all over, on a large file. If it can, it combines
>> several I/Os into one, by requesting more than a sing
Michael Kerrisk <[EMAIL PROTECTED]> wrote:
> ./man2/ioperm.2
> FIXME is the following ("Only the first 0x3ff I/O ports can be
> specified in this manner") still true? Looking at changes in
> include/asm-i386/processor.h between 2.4 and 2.6 suggests
> that the limit is differen
alan <[EMAIL PROTECTED]> wrote:
> I just wish that people would learn from the mistakes of others. The
> MacOS is a prime example of why you do not want to use a forked
> filesystem, yet some people still seem to think it is a good idea.
> (Forked filesystems tend to be fragile and do not play we
Egmont Koblinger <[EMAIL PROTECTED]> wrote:
> 2. My patch introduced "question mark with inverted color attributes" as a
>last resort fallback glyph. Though it perfectly works on VGA console, on
>framebuffer you may end up with question marks that are highlighed but
>shouldn't be, and
On Tue, 19 Jun 2007, Egmont Koblinger wrote:
> On Tue, Jun 19, 2007 at 03:54:52PM +0200, Bodo Eggert wrote:
>
> > Does the FLUSH DTRT by design, or does it just shrink and hide the original
> > race?
> But you may be right: yes, it might be a bug (or misfeature) in the
Albert Cahalan <[EMAIL PROTECTED]> wrote:
> On 6/19/07, William Lee Irwin III <[EMAIL PROTECTED]> wrote:
>> On Fri, Jun 08, 2007 at 02:35:22AM -0400, Albert Cahalan wrote:
>>> Right now, Linux isn't all that friendly to JIT emulators.
>>> Here are the problems and suggestions to improve the situat
Rene Herman <[EMAIL PROTECTED]> wrote:
> The point was that real mode could only access the first 1M, not
> the first 16... :-)
The real mode on i386+ can actually access the whole 4GB address range due to
a former-bug-now-feature in the i386+. This "bug" causes the segment limit
to not be reset
Jesse Barnes <[EMAIL PROTECTED]> wrote:
> On some machines, buggy BIOSes don't properly setup WB MTRRs to
> cover all available RAM, meaning the last few megs (or even gigs)
> of memory will be marked uncached. Since Linux tends to allocate
> from high memory addresses first, this causes the mach
Since your (William) patch will change the kconfig files my proposed patch
would change, could you please add those changes?
I hand-updated the patch below as recommended by the original discussion
on LKML. It won't aply as-is because of that (and because of your changes).
--- 2.6.21/arch/i386
On Fri, 6 Jul 2007, Andi Kleen wrote:
> Bodo Eggert <[EMAIL PROTECTED]> writes:
>
> > If the boot process failes to find init or the root fs, the cause has
> > usually scrolled off the screen, and because of the panic, it can't be
> > reached anym
On Thu, 5 Jul 2007, H. Peter Anvin wrote:
> Bodo Eggert wrote:
> > This patch adds the option to not mount another root filesystem
> > by specifying root=initramfs.
>
> Uhm, the kernel doesn't mount anything if you're using an initramfs.
Yes, instead it panics t
On Sat, 7 Jul 2007, Jan Engelhardt wrote:
> On Jul 5 2007 19:08, H. Peter Anvin wrote:
> >> BTW: Is it possible to mount a tmpfs on / before extracting the cpio?
> >
> >Not in the stock kernel. There have been some patches floating around
> >for that, I think.
>
> What would it buy? rootfs is a
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> vfat does not know about ownership, hence the files are always owned by the
> vfat mounter (or whatever the uid= option specified). Which brings
> a problem to userspace programs trying to utime() but which do not
> run as the same user as the vfat mount
that should happen is a wrongly set keyboard LED.
This patch adds 48 bytes of init-text on x86_32.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
diff -X dontdiff -pruN linux-2.6.22/drivers/char/keyboard.c
linux-2.6.22.changed/drivers/char/keyboard.c
--- linux-2.6.22/drivers/char/keyboa
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:
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 chang
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> On May 25 2007 14:14, David Miller wrote:
>>"!!" is used in contexts where pointers might be being
>>tested as well as plain integers, the "!!" turns a pointer
>>into the equivalent integer boolean for testing.
>>
>>NULL pointers become 0
>>non-NULL poin
On Sat, 26 May 2007, Al Viro wrote:
> On Sat, May 26, 2007 at 06:38:07PM +0200, Bodo Eggert wrote:
> > Not exactly, if(foo) is the same as if( (int) foo), which is not
> > guaranteed to result in non-null values for non-null pointers.
>
> RTFStandard.
... and don´t forget
Uncle George <[EMAIL PROTECTED]> wrote:
> i am using the GARMIN_GPS/usb driver to read a gps receiver.
> In testing the ability of my software to recover from various errors, I
> try this: unplug the gps/USB cable from the usb hub.
>
> Interestingly enough the thread spins.
> the SELECT() waits f
Tejun Heo <[EMAIL PROTECTED]> wrote:
> David Greaves wrote:
>> I have 2 ide disks. If I enable SMART and hibernate/suspend2disk, SMART is
>> disabled when I resume.
Maybe it's disabled by the BIOS?
> According to the ATA standard, the device (drive) itself is responsible
> for preserving SMART
On Wed, 11 Jul 2007, H. Peter Anvin wrote:
> 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 issu
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:
I toyed with setting up a diskless system in initramfs. In the process, I
came across some things:
1) There is no way to have the kernel not mount a filesystem,
unless you use /init or rdinit=.
1a) In the process of writing these patches, I found prepare_namespace not to
be called if /in
Disable mounting a root filesystem if root=rootfs is supplied.
If you put a rescue system on an initramfs, you should be able to boot it
without using tricks like an additional /init script.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
diff -X dontdiff -pruN linux-2.6.22/Documentation/
.
This is a rework of Al Boldi's "[PATCH] initramfs: Allow rootfs to use
tmpfs instead of ramfs". All the fame belongs to him, the bugs belong to me.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
diff -Xdontdiff -pruN linux-2.6.22.base/fs/Kconfig
linux-2.6.22.tmpfsroot/fs/Kco
This patch adds an option to disables the kernel's capability of mounting a
root device other than the ramfs. If you use initramfs, you don't need to
have this legacy feature anymore.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
diff -X dontdiff -pruN linux-2.6.22.base/init/do
On Fri, 13 Jul 2007, H. Peter Anvin wrote:
> Bodo Eggert wrote:
> > I toyed with setting up a diskless system in initramfs. In the process, I
> > came across some things:
> >
> > 1) There is no way to have the kernel not mount a filesystem,
> > unless y
On Fri, 13 Jul 2007, H. Peter Anvin wrote:
> Bodo Eggert wrote:
> > On Fri, 13 Jul 2007, H. Peter Anvin wrote:
> >> Bodo Eggert wrote:
> >>> I toyed with setting up a diskless system in initramfs. In the process, I
> >>> came across some things:
> >
Al Boldi <[EMAIL PROTECTED]> wrote:
> Bodo Eggert wrote:
Please reply-to-all, I'm not subscribed, but reading through a news gateway.
>> This is a rework of Al Boldi's "[PATCH] initramfs: Allow rootfs to use
>> tmpfs instead of ramfs". All the fame
On Sat, 14 Jul 2007, H. Peter Anvin wrote:
> Bodo Eggert wrote:
> > Setting the name of the rdinit process to the name of the init process
> > in order to select the root device should not be the right knob.
> >
>
> What's wrong with it?
rdinit is supposed to
On Sat, 14 Jul 2007, H. Peter Anvin wrote:
> Bodo Eggert wrote:
> > On Sat, 14 Jul 2007, H. Peter Anvin wrote:
> >> Bodo Eggert wrote:
> >>> Setting the name of the rdinit process to the name of the init process
> >>> in order to select th
Matt Mackall <[EMAIL PROTECTED]> wrote:
> On Fri, Jul 13, 2007 at 03:20:54PM +0200, Rene Herman wrote:
>> As far as I'm aware, the actual reason for 4K stacks is that after the
>> system has been up and running for some time getting "1 physically
>> contiguous pages" becomes significantly easier t
Satyam Sharma <[EMAIL PROTECTED]> wrote:
[zillions of ways to do -X dontdiff]
> Or just "cp -al" to create multiple trees at (almost) no disk cost
> that won't interfere with each other in any way, and makes the
> development process / generating patchsets trifle easier as well ...
Beware, some
On Sun, 15 Jul 2007, Rene Herman wrote:
> On 07/15/2007 07:17 PM, Bodo Eggert wrote:
> > Matt Mackall <[EMAIL PROTECTED]> wrote:
> >> On Fri, Jul 13, 2007 at 03:20:54PM +0200, Rene Herman wrote:
> >>> As far as I'm aware, the actual reason for 4K stacks i
On Tue, 17 Jul 2007, Jesper Juhl wrote:
> Please note that I was not trying to remove the 8K stack option right
> now - heck, I didn't even add anything to feature-removal-schedule.txt
> - all I wanted to accomplish with the patch that started this threas
> was; a) indicate that the 4K option is
On Tue, 17 Jul 2007, Rene Herman wrote:
> On 07/17/2007 12:37 AM, Ray Lee wrote:
> > On 7/16/07, Rene Herman <[EMAIL PROTECTED]> wrote:
> > If at some point one of the pro-4k stacks crowd can prove that all
> > code paths are safe
>
> I'll do that the minute you prove the current shared 8K stacks
On Tue, 17 Jul 2007, Rene Herman wrote:
> On 07/17/2007 01:45 AM, Bodo Eggert wrote:
> > On Tue, 17 Jul 2007, Rene Herman wrote:
> >> On 07/17/2007 12:37 AM, Ray Lee wrote:
> >>> If at some point one of the pro-4k stacks crowd can prove that all
> >>>
On Tue, 17 Jul 2007, Rene Herman wrote:
> On 07/17/2007 12:06 PM, Bodo Eggert wrote:
> > On Tue, 17 Jul 2007, Rene Herman wrote:
> >> On 07/17/2007 01:45 AM, Bodo Eggert wrote:
> >>> You claim 4k+4k is safe, therefore 8k must be safe, too.
> >>
> >&
Alan Cox <[EMAIL PROTECTED]> wrote:
> On Thu, 19 Jul 2007 03:33:58 +0200
> Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
>> > 8K stacks without IRQ stacks are not "safer" so I don't understand your
>> > comment ?
>>
>> Ouch, see the reports about 4k stack crashes. I agree they're not
>> safe w/o ir
On Wed, 18 Jul 2007, Rob Landley wrote:
> On Friday 13 July 2007 2:56:00 pm Bodo Eggert wrote:
> > I toyed with setting up a diskless system in initramfs. In the process, I
> > came across some things:
> >
> > 1) There is no way to have the kernel not mount a filesys
On Wed, 18 Jul 2007, Rene Herman wrote:
> On 07/18/2007 01:19 AM, Bodo Eggert wrote:
> > Please post a list of things you have designed, so I can avoid them.
>
> - The ability to read
> - The ability to understand
>
> You're doing a hell of a job already.
If you
On Tue, 17 Jul 2007, Arjan van de Ven wrote:
> > 1) It all can be reduced to 4K + 4K by asuming all IRQ happen on one CPU.
>
> no it's separate stacks for soft and hard irqs, so it's really 4+4+4
Thanks, I missed that information. Unfortunately this change still does
not help if one of these st
On Thu, 19 Jul 2007, Stephen Smalley wrote:
> Not wanting to get into any flamewars here about selinux, but just FYI:
> security_sb_post_mountroot is obsolete and can be removed without harm
> to selinux; it is a leftover of selinux before we moved the initial
> policy load to userspace. These da
Daniël Mantione <[EMAIL PROTECTED]> wrote:
> Op Thu, 19 Jul 2007, schreef Dmitry Torokhov:
>> On 7/14/07, Daniel Mantione <[EMAIL PROTECTED]> wrote:
> To make this discussion productive, I want to work towards a solution. I
> don't mind how I can make the keyboard work as it should, I just want it
Albert Cahalan <[EMAIL PROTECTED]> wrote:
> On 5/9/07, Andrey Borzenkov <[EMAIL PROTECTED]> wrote:
>> 3. this still does not answer how can I *create* long name from within Linux.
>
> WTF? These names are too annoying to use, even if there
> weren't this limit. Anything over about 29 characters i
Satyam Sharma <[EMAIL PROTECTED]> wrote:
> In fact you can't really say the same for
> volatile. We already assume the compiler _actually_ took some
> pains to stuff meaning into C's (lack of) definition of volatile and
> implement it -- but in what sense, nobody knows (the C standard
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote:
> On Mon, 04 Jun 2007, Dmitry Torokhov wrote:
>> >...but I'm not quite sure it is a buggy keyboard. It happens _way_ too
>> >often. Launch the line above and try to do some typing...
>>
>> This used to work fine on my box last time I tried it
Change the description of CONFIG_*HIGHMEM* to reflect "lost" memory due to
PCI space and the existence of the NX flag.
Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
---
I made this quick patch using the information from LKML as I remembered
it. Please verify.
--- 2.6.21/arch/
(not CCing security, since it's not a security bug and it's too late to
verify if they should be on cc. Will do later.)
Anand Jahagirdar <[EMAIL PROTECTED]> wrote:
> This patch Warns the administrator about the fork bombing attack
> (whenever any user is crossing its process limit). I have used
201 - 300 of 371 matches
Mail list logo
