On Oct 11 2007 08:01, Rick Niles wrote:
>
> I've been trying to make the driver work with
> Fedora 7 and the 2.6.22 kernel, but the rtc_register() and other RTC functions
> seems to have been removed.
grep -r rtc_device_register drivers/rtc/
Does that help?
> I see they've been replaced by the
On Oct 11 2007 00:13, Russ Dill wrote:
>
>/* only text is profiled */
>> prof_len = (unsigned *) &_etext - (unsigned *) &_stext;
Uh, that's some evil pointer arithmetic :)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a me
On Oct 10 2007 14:36, Alexey Dobriyan wrote:
>> >> --- linux-2.6.23/include/linux/mm.h.vanilla
>> >> +++ linux-2.6.23/include/linux/mm.h
>> >
>> >> +struct super_block;
>> >> extern void drop_pagecache_sb(struct super_block *);
>> >> void drop_pagecache(void);
>> >> void drop_slab(void);
>> >>
On Oct 8 2007 14:55, James Bowes wrote:
> 20: Check that it all passes `make headers_check'.
>
> 21: Has been checked with injection of at least slab and page-allocation
>-fauilures. See Documentation/fault-injection/.
>+failures. See Documentation/fault-injection/.
It was a fault inje
On Oct 9 2007 09:26, Vasily Averin wrote:
>
>On one of our servers timer interrupts (i.e irq0) are stops working. As result
>any kernel timers do not triggers and tasks waiting some signals from timers
>hangs forever.
What kernel.. and tried CONFIG_NO_HZ=n?
-
To unsubscribe from this list: send
On Oct 9 2007 07:12, Antonino A. Daplas wrote:
>>
>> References: http://lkml.org/lkml/2007/4/1/162
>> http://lkml.org/lkml/2007/10/5/199
>
>This is quite a long thread :-)
It was a patch series after all. But as Greg puts it, be persistent.
>> +config VT_PRINTK_COLOR
>> +hex "Colored k
On Oct 8 2007 19:37, Sam Ravnborg wrote:
>snip...
>
>Or maybe we need something much less formal that explain the purpose of the
>four tags we use:
At least formal try:
>Signed-of-by:
* Used by original submitter(s).
* Also used by maintainers to track the patch's path
(ATM, does not imply "I
On Oct 7 2007 17:23, Alan Cox wrote:
>
>>>- If you want to do "pretty" boot up you do it in X or frame buffer
>>>(which is going to get easier and easier with the X shift to kernel side
>>>video support)
>>
>> fb is slow. Feels like a 9600bps serial line.
>
>So fix your fb. There is enough inform
On Oct 8 2007 01:02, Oleg Verych wrote:
>
>If you are not going to see OOPes of new kernels running old distros, ask
>any perl hacker (as they lovely mentioned in lkml) to hack for you
>something like:
>
>sed -u -e '
>/^<1/s_^_'$COLOR1'_
>/^<2/s_^_'$COLOR2'_
>/^<3/s_^_'$COLOR3'_
>/^<4/s_^_'$COLOR4
On Oct 8 2007 00:18, Oleg Verych wrote:
>
>Kind of funny thing with it. One for shell in `mcedit` is much nicer, but
>`emacs` is more powerful as editor(R). But both have highlighting
>problems with non trivial scripts (quoiting, data here, etc). I don't
>know if it will ever be fixed :).
No, it
On Oct 7 2007 22:50, Oleg Verych wrote:
>
>In fact mc config (ini) section is a better way.
Yes, for the default colors. But /usr/share/mc/syntax/ specifies
more of them.
>I use default blue (which is very annoying)
If blue were annoying, it would not be the default Windows background
(since Wi
On Oct 7 2007 21:27, Rene Herman wrote:
>
> I saw you remark on FB console in a reply to Alan just now and I
> quite agree with you. The (current) FB console is slow and I'll add
> "dumb" myself. When you have a 1280x1024 screen available, you get
> to do cool things like put up nice little window
On Oct 7 2007 22:00, Rene Herman wrote:
> On 10/07/2007 09:56 PM, Jan Engelhardt wrote:
>
>> Some is good, as long as it is not excessive. While I could imagine that
>> Knoppix will abuse the feature and use vt.printk_color=9,9,9,9,11,10,12, this
>> is not what serious pe
On Oct 7 2007 21:13, Willy Tarreau wrote:
>There are two distinct populations :
> - those [...]
>who would never have imagined that pressing Escape
>during the boot of windows 3.1/95 provided them with the full text
>messages.
This is news to me. DOS always showed messages, and under
On Oct 7 2007 20:47, Rene Herman wrote:
>
>> > Coloring isn't useful. If it was, it would be implemented ~16 years
>> > ago.
>>
>> Congratulations, this is the most stupid argument i've ever read on lkml.
>
> "Ay. World is finished. Everyone can go home and watch Friends reruns now."
>
> But well
On Oct 7 2007 18:59, Ingo Molnar wrote:
>> > vmlinux:
>> > textdata bss dec hex filename
>> > 7732358 1157269 401408 9291035 8dc51b vmlinux.before
>> > 7732374 1157269 401408 9291051 8dc52b vmlinux.after
>> >
>> >16 bytes, or 0.0002% of the total text size. So there's in
On Oct 7 2007 18:44, Ingo Molnar wrote:
>> This patch makes it possible to give kernel messages a selectable
>> color. It can be chosen at compile time, overridden at boot time, and
>> changed at run time.
>
>here's some (good) text footprint data:
>
>with the feature disabled (which is the defa
On Oct 7 2007 18:38, Ingo Molnar wrote:
>
>minor fix: i had to use the slightly modified patch below instead of the
>one you posted, so that the second patch applies fine.
What is it that you changed? The printk patches are right at the front,
so there should not be any fuzz or offsets (might va
On Oct 7 2007 13:10, Oleg Verych wrote:
>This `scrollback' is usual late boot / console one. If fact useful,
>until first tty switch or if `screen` cannot be used. But for some
>reason if scrolling region (DECSTBM) is less than whole screen, nothing
>works.
Actually, scrolling begins to work onc
On Oct 7 2007 16:12, Alan Cox wrote:
>
>- We run on a lot more than VGA PC consoles
>- We have serial consoles (which may or may not be VT132/ANSI compliant)
Yes, and the serial driver does not usually pass on vc->vc_color to the real
hardware. If it did, it would have to transform it back into a
On Oct 6 2007 20:50, Bill Davidsen wrote:
>>
>>> I start my root xterm in white on blue for identification, so color coding
>>> sounds like a great idea to me.
>>
>> This has nothing to do with xterms, this is "VGA color console" only.
>> xterm config is in /usr/share/X11/app-defaults/XTerm-colo
On Oct 7 2007 00:28, Oleg Verych wrote:
>
>I thought, i was talking about *write() functions, that got one
>additional unrelated, non config removable API change in face of
>`unsigned int loglevel'.
Documentation/stable_api_nonsense.txt ;-)
>Idea. Extend those macro defines before format string
On Oct 6 2007 23:25, Oleg Verych wrote:
>> ---
>> arch/x86_64/kernel/early_printk.c | 11 +++
>> drivers/char/Kconfig |4 +++-
>> drivers/char/vt.c | 32
>> drivers/net/netconsole.c |3 ++-
>> drivers/seria
On Oct 6 2007 23:03, Oleg Verych wrote:
>>
>> (btw., i corrected the subject line to remove the 'NAK'. Why do you
>> think you can 'NAK' a patch in this field?)
>
>I added comment (like this), so anyone can skip reading body, if headers
>are "Oleg Verych && NAK". In case if `NAK' have a magic me
On Oct 5 2007 21:49, Hugh Dickins wrote:
>> > > $ zcat /proc/config.gz | grep TMPFS
>> > > # CONFIG_TMPFS is not set
>> > > $ grep tmpfs /proc/filesystems
>> > > nodev tmpfs
>> >
>> > tmpfs (mm/shmem.c) is used by the kernel to support shared memory
>> > of various kinds even when CONFIG_TMPFS
On Oct 3 2007 10:55, Bodo Eggert wrote:
>
>> [PATCH]: Fill the size of FIFOs
>>
>> Instead of reporting 0 in size when stating() a pipe
>
>FIFO
Yes
-
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
Colored kernel message output (2/2)
By popular request, this patch adds per-loglevel coloring.
The user may set values using vt.printk_color= or by modifying
the sysfs file in the running system.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/early_printk.c
-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
drivers/char/Kconfig | 42 ++
drivers/char/vt.c| 23 +++
2 files changed, 65 insertions(+)
Index: linux-2.6.23/drivers/char/K
On Oct 6 2007 15:53, Bill Davidsen wrote:
> Jan Engelhardt wrote:
>> Colored kernel message output
>>
>> Let's work more on Linux's cuteness! [http://lkml.org/lkml/2007/10/4/431]
>> The following patch makes it possible to give kernel messages a
>> sel
one that vt.c used for all the
past years anyway, so apart from the config option, nothing changes
for the conservative user.
References: http://lkml.org/lkml/2007/4/1/162
http://lkml.org/lkml/2007/10/5/199
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
drivers/char/Kconfig
Colored kernel message output (2/2)
By popular request, this patch adds per-loglevel coloring.
The user may set values using vt.printk_color= or by modifying
the sysfs file in the running system.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/early_printk.c
On Oct 5 2007 17:00, Andrew Morton wrote:
>>
>> It is already possible to deactivate the vc bell on a per-tty basis,
>> by using echo -en "\e[11;0]", but this is reset on reset(1).
>>
>> This adds a sysfs parameter to globally control the vc bell, as well
>> as sysfs parameters for default pitch
On Oct 6 2007 10:55, Alan Cox wrote:
>> >
>> > It is already possible to deactivate the vc bell on a per-tty basis,
>> > by using echo -en "\e[11;0]", but this is reset on reset(1).
>> >
>> > This adds a sysfs parameter to globally control the vc bell, as well
>> > as sysfs parameters for defaul
On Oct 6 2007 02:23, Jan Engelhardt wrote:
>>
>>Not convinced WRT ASCII color codes, though. ASCII doesn't contain
>>codes for changing colors. Perhaps some specific "extended ASCII"?
>
>Start up QBasic, issue
> COLOR 1
>=> blue.
>
&g
On Oct 6 2007 02:10, Krzysztof Halasa wrote:
>Jan Engelhardt <[EMAIL PROTECTED]> writes:
>
>>>I wonder how accurate is it.
>>
>> Since I do not use 512-glyph fonts, I do not know.
>
>Actually I meant "how accurate my remarks are" :-)
>
>Not
On Oct 6 2007 01:22, Krzysztof Halasa wrote:
>Jan Engelhardt <[EMAIL PROTECTED]> writes:
>
>> +The value you need to enter here is the ASCII color value
>
>ASCII color value? ANSI perhaps?
ANSI:
\e[31m R--
\e[32m G--
\e[33m RG- (yellow)
\e[34m --B
\e[35m R-B (magen
On Oct 5 2007 15:11, H. Peter Anvin wrote:
> Jan Engelhardt wrote:
>> 15 partitions (at least for sd_mod devices) are too few.
>
> Now when we have 20-bit minors, can't we simply recycle some of the
> higher bits for additional partitions, across the board? 63
> pa
On Oct 5 2007 15:43, Lennart Sorensen wrote:
>On Fri, Oct 05, 2007 at 09:32:11PM +0200, Jan Engelhardt wrote:
>> Ah you seem to be a proponent of http://www.blackgoogle.com/
>> then :-) Unfortunately, it seems like Xft uses Grayscale AA
>> (http://antigrain.com/resear
On Oct 5 2007 14:35, Timur Tabi wrote:
>>
>> standard x86:
>> ---LSB-- ---2SB-- ---3SB-- ---MSB-- [bytes] LITTLE_ENDIAN
>> M765432L M765432L M765432L M765432L [bits] ?_BITFIELD
>>
>> (Not sure what bitfield type, but I'd guess BIG_ENDIAN_BITFIELD)
>
> Are you sure? I would think that all machi
On Oct 5 2007 15:24, Lennart Sorensen wrote:
>On Fri, Oct 05, 2007 at 09:21:57PM +0200, Jan Engelhardt wrote:
>> Indeed it should be 0x07, should it go in.
>> Otherwise the openbsd camp might start another flamewar.
>>
>> (On a personal note, would 0x1F work better
On Oct 5 2007 15:19, Lennart Sorensen wrote:
>On Fri, Oct 05, 2007 at 09:13:40PM +0200, Jan Engelhardt wrote:
>> +config VT_PRINTK_COLOR
>> +hex "Colored kernel message output"
>> +range 0x00 0xFF
>> +depends on VT_CONSOLE
>> +default 0x1
t, FreeBSD to some
extent, so I think Linux should too.
Inspired by cko (http://freshmeat.net/p/cko/), but independently
written, later contributed forth and back.
Already posted at: http://lkml.org/lkml/2007/4/1/162
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
drivers/cha
On Oct 5 2007 13:27, Timur Tabi wrote:
>
> What's the difference between __LITTLE_ENDIAN and __LITTLE_ENDIAN_BITFIELD?
> Can
> someone give me an example when __BIG_ENDIAN and __LITTLE_ENDIAN_BITFIELD
> would
> both be defined simultaneously?
standard x86:
---LSB-- ---2SB-- ---3SB-- ---MSB-- [b
On Oct 4 2007 20:46, Matthew Wilcox wrote:
>On Tue, Oct 02, 2007 at 08:00:26PM +0200, Jan Engelhardt wrote:
>> Add %S_IWUGO bit for files on ISO-9660 filesystems without RockRidge
>
>Looks to me like you've added S_IWUSR, not S_IWUGO.
Yes, S_IWUSR it should be, and is. When
It is already possible to deactivate the vc bell on a per-tty basis,
by using echo -en "\e[11;0]", but this is reset on reset(1).
This adds a sysfs parameter to globally control the vc bell, as well
as sysfs parameters for default pitch and duration.
Signed-off-by: Jan Engelhar
15 partitions (at least for sd_mod devices) are too few.
So I tried the following: after scanning the disk (sda), when we know
the number of partitions P on a disk, create a new block device
/dev/gd0 that is a copy of sda (in terms of disk->queue, etc.). This
is done using alloc_disk(P).
However
Hi,
I'd like to register a blkdev region, much like
blk_register_region(MKDEV(major, first_minor), number_minors,
xmodule, xprobe, xlock, xdata);
number_minors is known, but how do I decide what first_minor to use?
Module owns the full major number, so I tho
On Oct 4 2007 11:44, Pavel Machek wrote:
>diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
>index 7f1730f..1595a45 100644
>--- a/Documentation/CodingStyle
>+++ b/Documentation/CodingStyle
>@@ -71,6 +71,15 @@ used for indentation, and the above exam
>
> Get a decent editor and do
On Oct 3 2007 09:09, Linus Torvalds wrote:
>On Wed, 3 Oct 2007, Alan Cox wrote:
>>
>> > and btw, there is no question what-so-ever about whether your compiler
>> > might be doing a legal optimization - the compiler really is wrong, and is
>>
>> Pedant: valid. Almost all optimizations are legal,
On Oct 3 2007 14:33, Frans Pop wrote:
>
>I saw top occasionally displaying % CPU usage for a process. The
>first few times it was amarokapp, this last time it was kontact.
>Both applications were basically idle.
Yes this certainly sounds like KDE. Did you try with Gnome,
or perhaps a simple `
On Oct 2 2007 23:49, Jimmy wrote:
>
> Anyway, I've been trying to figure out what purpose the gpl-only code serves.
> What good comes out of disabling people from probing modules that do not have
> a
> gpl-compatible license?
find /lib/modules/`uname -r` -iname '*.ko' | wc -l:
2021
Pro
Hi,
I am using 2.6.23-rc9 with pata_sis. `modprobe -r sd_mod`, which I ran
from initramfs, caused all my disks to spindown - sd even told me so.
I recall there has been talk a while back about whether to spin down
disks on shutdown or not, but I do not think it touched the removal of
sd_mod,
Add %S_IWUGO bit for files on ISO-9660 filesystems without RockRidge
extensions. This allows one to modify the files right after copying,
without having to do an extra recursive chmod if `cp -p` or
`rsync -p` is used.
References: http://lkml.org/lkml/2007/4/1/164
Signed-off-by: Jan Engelhardt
[PATCH]: Fill the size of FIFOs
Instead of reporting 0 in size when stating() a pipe, we give the number of
queued bytes. This might avoid using ioctl(FIONREAD) to get this information.
References: http://lkml.org/lkml/2007/4/2/138
Cc: Eric Dumazet <[EMAIL PROTECTED]>
Signed-off-b
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
fs/pipe.c | 49 -
1 file changed, 36 insertions(+), 13 deletions(-)
Index: linux-2.6.23/fs/pipe.c
===
--- linux-2.6.23.or
On Oct 2 2007 09:03, Joe Perches wrote:
>On Tue, 2007-10-02 at 17:45 +0200, Jan Engelhardt wrote:
>> always use printk("%s", var)
>
>You have to use indirect arguments to log something?
No, you do not have to.
>Don't you think that's a stupid rule?
Not at
On Oct 2 2007 08:41, Joe Perches wrote:
>On Tue, 2007-10-02 at 07:18 +0200, Ingo Molnar wrote:
>> +#define KERN_CONT ""
>
>This doesn't work with printk(char** array[index]) continuations
>or with strings with embedded KERN_ prefixes.
Huh?
...Ah. Yeah, pasting a string literal with a va
Lift the FS menu a bit by moving filesystem-specific
parts into their own menu.
This also moves minix and romfs into the "misc fs" menu,
as per Randy Dunlap's suggestion [http://lkml.org/lkml/2007/9/25/344]
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
f
On Oct 2 2007 13:39, Giuliano Gagliardi wrote:
>>
>> You could write up a LSM that restricts UID changing.
>
>Would you not consider it more useful to let one process have multiple user
>ids? I do not see why they can have multiple group ids, but only (and
>exactly) three user ids.
It would rai
On Oct 2 2007 13:33, Giuliano Gagliardi wrote:
>Date: Tue, 2 Oct 2007 13:33:05 +0200
>From: Giuliano Gagliardi <[EMAIL PROTECTED]>
>To: Jan Engelhardt <[EMAIL PROTECTED]>
>Subject: Re: One process with multiple user ids.
>
>On Tuesday 02 October 2007, Jan Engelhardt
On Oct 2 2007 12:56, Giuliano Gagliardi wrote:
>
>I have a server that has to switch to different user ids, but because it does
>other complex things, I would rather not have it run as root. I only need the
>server to be able to switch to certain pre-defined user ids.
All you need is CAP_SETUID
On Sep 30 2007 01:16, Andrew Morton wrote:
>>
>> Documentation/Smack.txt | 104 +
>> security/Kconfig |1
>> security/Makefile |2
>> security/smack/Kconfig| 10
>> security/smack/Makefile |9
>> security/smack/smack.h| 207
On Sep 30 2007 15:36, Ingo Oeser wrote:
>
>> obj-y-ifn-
>
>This is the only one needed, because it is cumbersome to express
>negative rules in kbuild to include stubs (e.g. nommu stuff).
Perhaps this would work?
ifeq (${CONFIG_NO_MMU},)
obj-m += magic_mmu.o
endif
>But again this can be done wi
On Oct 1 2007 14:39, Bill Nottingham wrote:
>Jan Engelhardt ([EMAIL PROTECTED]) said:
>>
>> Make the vt return to the system default when it is reset.
>> Also make UTF-8 the system default.
>> Derived from http://lkml.org/lkml/2007/8/31/246
>>
>> Tested an
Make the vt return to the system default when it is reset.
Also make UTF-8 the system default.
Derived from http://lkml.org/lkml/2007/8/31/246
Tested and works as expected.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
drivers/char/keyboard.c |2 +-
drivers/char/sysrq.c
On Sep 28 2007 19:03, WANG Cong wrote:
>
>Maybe checkpatch.pl needs an option '-W' to turn on/off those vexed "noise".
>(It seems that 'q|quiet' doesn't do as much as what it hints.)
Make checkpatch.pl a C language parser, then it can handle
all the whitespace violations without false positives.
On Sep 27 2007 23:18, Vegard Nossum wrote:
> * kprint_() is better than kprint(case of the default log-level, the argument can be omitted.
> * Memory allocated for entries and arguments is done in a ring-buffer
>with variable-sized chunks. Arguments are chained with a singly-
>linked
On Sep 27 2007 16:53, linux-os (Dick Johnson) wrote:
>
>If Windows lets you get away with this, then Windows is broken.
>memset(ch,'\0',strlen(ch) );
No, probably just the chance that the memory to which ch points
had a nul in it or in the near bytes.
Use valgrind, move along.
>On Thu, 27 Sep 2
On Sep 27 2007 12:41, mahamuni ashish wrote:
>I have small code
This is not a kernel problem. (Read your C book and/or ask in
a C newsgroup.)
>char ch[4];
>memset(ch,'\0',strlen(ch) );
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAI
On Sep 27 2007 07:51, Stephen Hemminger wrote:
>
>You need every socket to close and all routes to go away including the
>routes through loopback device, and still there probably are control
>sockets buried inside ipv6 that hold ref count.
>
>IMHO the kernel should just admit that IPV6 can't be
On Sep 26 2007 14:06, Stephen Hemminger wrote:
>> >
>> > No, network devices don't do reference counting.
>>
>> Could you explain why, please?
>>
>> After `udevd` on boot loads lots of unused crap, i surrendered, and use
>> $(rmmod `lsmod | just first column`). Networing bravely wipes away. OK,
On Sep 26 2007 18:13, Alan Cox wrote:
>> Hello!
>>
>> Can i get this card working? Hotplug doesn't recognise it, however i
>> know that Linux supports it.
>
>The kernel supports the NinjaSCSI-3 and UltraNinja-16 (you couldn't make
>these names up could you) but not afaik the card you have a du
On Sep 26 2007 11:43, Erez Zadok wrote:
>
>*That's* the information I was looking for, Kyle: what's the estimated
>probability I should be using as my guideline. I used 95% (20/1 ratio), and
;-)
19:1 <=> 95:5 <=> 95% <=> ratio=0.95 != 20.0 (=20/1)
>you're telling me I should use 99% (100/1 ra
On Sep 26 2007 10:01, Erez Zadok wrote:
>>
>> On Sep 25 2007 23:09, Erez Zadok wrote:
>> >--- a/fs/unionfs/commonfops.c
>> >+++ b/fs/unionfs/commonfops.c
>> >@@ -394,8 +394,8 @@ int unionfs_file_revalidate(struct file *file, bool
>> >willwrite)
>> >if (willwrite && IS_WRITE_FLAG(file->f_flag
On Sep 25 2007 23:09, Erez Zadok wrote:
>--- a/fs/unionfs/commonfops.c
>+++ b/fs/unionfs/commonfops.c
>@@ -394,8 +394,8 @@ int unionfs_file_revalidate(struct file *file, bool
>willwrite)
> if (willwrite && IS_WRITE_FLAG(file->f_flags) &&
> !IS_WRITE_FLAG(unionfs_lower_file(file)->
On Sep 25 2007 10:35, Greg KH wrote:
>On Tue, Sep 25, 2007 at 07:03:24PM +0200, Jan Engelhardt wrote:
>> So, here is something that I think should go into the next 2.6.22.
>> A proper fix is already in 2.6.23-git-du-jour.
>
>Feel free to send the patch, with the git comm
On Sep 25 2007 19:21, Oliver Pinter wrote:
>
>the rev is locali declared:
>
>[snap]
>
> ...
>
>static void ali_init_chipset(struct pci_dev *pdev)
>{
>u8 rev, tmp;
>struct pci_dev *north, *isa_bridge;
>
>pci_read_config_byte(pdev, PCI_REVISION_ID, &rev);
>
> ...
>
>[snap]
>
On Sep 25 2007 19:00, Miloslav Semler wrote:
>> > This does not help. Let's try:
>> > chroot somewhere
>> > mkdir foo
>> > fd = open /
>> > chroot foo
>> >
>>
>> ('fd' implicitly closed and chdir to /foo)
>>
> Really? Try it. I am sure, that this works. You can create directory in chroot
>From my point, sorry for thread hijacking, but I did not have
the upper node anymore.
So, here is something that I think should go into the next 2.6.22.
A proper fix is already in 2.6.23-git-du-jour.
/home/build/rt.jengelh.10.2-i386/var/tmp/kernel-source-2.6.22.7-build
/usr/src/linux-2.6.22.7-1
On Sep 25 2007 18:19, Miloslav Semler wrote:
>> > > So what? Just do this: chdir into the root after chroot.
>> > >
>> > I don't think so. His exploit just got me all the way out of a chroot
>> > within a
>> > chroot within a chroot, inclusive of lots of chdirs.
>> >
>>
>> Close all f
On Sep 26 2007 01:11, David Newall wrote:
> Jan Engelhardt wrote:
>> On Sep 26 2007 00:40, David Newall wrote:
>>
>> > Miloslav Semler pointed out that a root process can chdir("..") out of its
>> > chroot.
>> So what? Just do this: chdir into
On Sep 25 2007 16:48, Alan Cox wrote:
>David Newall <[EMAIL PROTECTED]> wrote:
>> Alan Cox wrote:
Marek's loading dynamic libraries, it seems clear that the prime
purpose of chroot is to aid security. Being able to cd your way
out is handy
>>>
>>> Does it - I can't find any ev
d better, safer solutions.
So what? Just do this: chdir into the root after chroot.
It won't conform to SVR4/4.4BSD anymore, but hey, let Linux set some
sane standard ain't bad either. I doubt anyone really relies on the
fact that after chroot, your cwd might be outside the root.
Sign
On Aug 8 2007 16:19, Subbaiah Venkata wrote:
>
>Hello, I fixed and tested a small bug in lib/sort.c file, heap sort
>function.
>
>The fix avoids unnecessary swap of contents when i is 0 (saves few
>loads and stores), which happens every time sort function is called.
>I felt the fix is worth bringi
Lift the FS menu a bit by moving filesystem-specific
parts into their own menu.
This is an idea I had. Comments please, if any.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
fs/Kconfig | 19 ---
fs/gfs2/Kconfig |9 ++---
fs/xfs/Kconfig
Turn Network File Systems into a menuconfig so that it can be
disabled at once.
(Note: I added a "default y". If you do not like that, speak up.)
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
fs/Kconfig | 16 ++--
1 file changed, 14 insertions(+), 2 del
Changes NLS and DLM menus into a 'menuconfig' object
so that it can be disabled at once without having to enter
the menu first to disable the config option.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
fs/dlm/Kconfig |8 ++--
fs/nl
On Sep 24 2007 15:09, Dave Jones wrote:
>
> > +#if defined(__i386__) && defined(CONFIG_DMI)
> > dmi_check_system(acpi_dmi_table);
> > #endif
> >
> > +#ifdef CONFIG_DMI
> > dmi_scan_machine();
> > +#endif
> >
> > +#ifdef CONFIG_DMI
> > /* Check and install the TSC clocksource */
>
On Sep 24 2007 16:25, Jaswinder Singh wrote:
>So it is obsolete for user's point of view, right ?
.config is human-readable and serves as input for kconfig,
and autoconf.h is kconfig's output for the C binding that
you do not mess with.
Neither is obsolete, end of story.
If Linux were to have
On Sep 24 2007 01:35, [EMAIL PROTECTED] wrote:
>On Sun, 23 Sep 2007 00:03:49 +0400, Alexey Dobriyan said:
>
>> -static inline void *kcalloc(size_t n, size_t size, gfp_t flags)
>> -{
>> -if (n != 0 && size > ULONG_MAX / n)
>> -return NULL;
>> -return __kmalloc(n * size, flags |
On Sep 23 2007 11:20, Vegard Nossum wrote:
>> >printk(KERN_INFO "Message.\n");
>> >kprint_info("Message.");
>>
>> I'd rather fix up code to reduce its indent rather than
>> trying microoptimizations at the function name level!
>
>Well, that's a different discussion, really. Is fixing the body of
>
On Sep 23 2007 10:39, Vegard Nossum wrote:
>On 9/23/07, Joe Perches <[EMAIL PROTECTED]> wrote:
>> On Sat, 2007-09-22 at 21:27 +0200, Vegard Nossum wrote:
>> > #define kprint(fmt, ...)
>>
>> Good ideas. Perhaps a prefix of klog or kp_ instead?
>> Given the number of 80 column zealots, character na
On Sep 22 2007 22:10, ben soo wrote:
>
> i used to add proxy arp's on the router when i had problems like this. Dunno
> if it's the recommended fix, but it worked.
There is certainly no Proxy ARP required here since you do not
do subnet sharing or funny games like that.
> http://en.wikipedia.or
On Sep 22 2007 22:52, Sam Ravnborg wrote:
>
>Does the following patch fix it at your end?
>Seems to work for me.
Yes.
>-
>+# Check the OUTPUT directory is not the same as where we have kernel src
>+$(if $(filter-out $(KBUILD_OUTPUT),$(shell /bin/pwd)),, \
>+ $(error Output directory (O=...)
Hi,
You can cause a recursion in kbuild/make with the following:
make O=$PWD kernel/time.o
make mrproper
Of course no one would use O=$PWD (that's just the testcase),
but this happened too often:
/ws/linux/linux-2.6.23$ make O=/ws/linux/linux-2.6.23 kernel/time.o
(Oops - should have been O=/ws
On Sep 22 2007 10:36, Satyam Sharma wrote:
>> from arch/i386/boot/compressed/misc.c:14:
>> include/asm/processor.h: In function ‘cpuid_count’:
> ^^ ^^
>> include/asm/processor.h:615: warning: pointer targets in passing
>
On Sep 21 2007 18:41, Chuck Ebbert wrote:
>On 09/21/2007 06:32 PM, Andi Kleen wrote:
>> From: Pavel Emelyanov <[EMAIL PROTECTED]>
>>
>> Typically the oops first lines look like this:
>>
>> BUG: unable to handle kernel NULL pointer dereference at virtual address
>>
>> printing eip:
>>
On Sep 22 2007 08:57, Sam Ravnborg wrote:
>>
>> This seems like yet another list that will need to be perpetually
>> kept up to date, and given 99% of users don't know the codename
>> of their core, just the marketing name, I question its value.
>
>As a bare minimum requirement the list presented
On Sep 21 2007 22:44, Andi Kleen wrote:
>Subject: [PATCH] [8/45] x86_64: Use string instruction memcpy on AMD Fam11h
>
>--- linux.orig/arch/x86_64/kernel/setup.c
>+++ linux/arch/x86_64/kernel/setup.c
>@@ -575,7 +575,7 @@ static void __cpuinit init_amd(struct cp
> level = cpuid_eax(1);
>
On Sep 21 2007 08:53, Randy Dunlap wrote:
>On Fri, 21 Sep 2007 17:35:43 +0400 Andrey Mirkin wrote:
>
>> From: Andrey Mirkin <[EMAIL PROTECTED]>
>>
>> Right now futexfs and inotifyfs have one magic 0xBAD1DEA, that looks a
>> little
>> bit confusing.
>> Use 0xBAD1DEA as magic for futexfs and 0x2B
501 - 600 of 2191 matches
Mail list logo
