Hi,
Please keep me CC'd.
A multi-threaded program's thread A wants to create a new executable
file with open(O_CLOEXEC), write, close, and then fork and exec it.
Meanwhile, another thread B forks before A's close, carrying a reference
to the open file description with it, thus A's execve fails wi
Hi Luke,
> if i choose to release all copyright code under dual licenses then
> THAT IS MY RIGHT
Sssh! It's a Sunday morning; hangover time for many.
Does the LICENSING section in
http://lxr.free-electrons.com/source/Documentation/development-process/1.Intro#L237
help?
Cheers, Ralph.
--
To un
Hi Ondrej,
Ondrej Zary wrote:
> Ralph Corderoy wrote:
> > As I understand it, an IDE hard drive can be reset in three ways. A
> > power-on reset, a hard reset caused by pin 1 (RESET-) on the IDE
> > connector, and a soft reset (bit SRST in the device control
> > reg
Hi,
As I understand it, an IDE hard drive can be reset in three ways. A
power-on reset, a hard reset caused by pin 1 (RESET-) on the IDE
connector, and a soft reset (bit SRST in the device control register).
RESET- is held low on a power on, but can also be used later to do a
hard reset.
I can
Hi,
Christopher Li wrote:
> On Sat, Apr 09, 2005 at 04:31:10PM -0700, Linus Torvalds wrote:
> > NOTE! This means that each "tree" file basically tracks just a
> > single directory. The old style of "every file in one tree file"
> > still works, but fsck-cache will warn about it. Happily, the git
Hi Paul,
> Ralph wrote:
> > Watch out for when xargs invokes do_something more than once and the
> > `<' is parsed by a different one than the `>'.
>
> It will take a pretty long list to do that. It seems that GNU xargs
> on top of a Linux kernel has a 128 KByte ARG_MAX.
I didn't realise it wa
Hi Linus,
> Btw, the NUL-termination makes this really easy to use even in shell
> scripts, ie you can do
>
> diff-tree | xargs -0 do_something
>
> and you'll get each line as one nice argument to your "do_something"
> script. So a do_diff could be based on something like
>
> #!/
Hi,
Humberto Massa wrote:
> First, there is *NOT* any requirement in the GPL at all that requires
> making compilers available. Otherwise it would not be possible, for
> instance, have a Visual Basic GPL'd application. And yes, it is
> possible.
>From section 3 of the GNU GPL, version 2:
Th
Hi Jesper,
> > > the short version also have the real bennefits of generating
> > > shorter and faster code as well as being shorter "on-screen".
> >
> > Faster code? I'd have thought avoiding the function call outweighed
> > the overhead of checking before calling.
>
> I haven't actually meas
Hi Jesper,
> > Not necessarily. It helps tell the reader that the pointer may be
> > NULL at that point. This has come up before.
> >
> >
> > http://groups-beta.google.com/group/linux.kernel/browse_thread/thread/bd3d6e5a29e43c73/[EMAIL
> > PROTECTED]
> >
>
> I agree that
>
> if
Hi Jesper,
> kfree() handles NULL pointers, so checking a pointer for NULL before
> calling kfree() on it is pointless.
Not necessarily. It helps tell the reader that the pointer may be NULL
at that point. This has come up before.
http://groups-beta.google.com/group/linux.kernel/browse_
Hi Domen,
> On 07/03/05 00:07 +0000, Ralph Corderoy wrote:
> > > - if (db->dict) {
> > > - vfree (db->dict);
> > > - db->dict = NULL;
> > > - }
> > > + vfree (db->dict);
> &g
Hi Domen,
> - if (db->dict) {
> - vfree (db->dict);
> - db->dict = NULL;
> - }
> + vfree (db->dict);
> + db->dict = NULL;
Is it really worth always calling vfree() which calls __vunmap() before
db->dict is de
Hi Corey,
> Here is the documentation for krefs, with the kref_checked stuff
> removed and a few other things cleaned up.
Great, more documentation. :-) A few minor points...
> +To use a kref, add a one to your data structures like:
s/a one/one/
> +You must initialize the kref after you all
Hi,
David Roundy, creator of darcs, wrote:
> On Sat, Feb 19, 2005 at 05:42:13PM +0100, Andrea Arcangeli wrote:
> > I read in the webpage of the darcs kernel repository that they had
> > to add RAM serveral times to avoid running out of memory. They
> > needed more than 1G IIRC, and that was enoug
Hi,
Alan Cox wrote:
> > I'd like to find more detail of the rare corruption so I can see if
> > it matches what we're experiencing, is it more likely with an SMP
> > machine, etc. Is there an archive of patches that go into a
> > particular version anywhere?
>
> No but all pre releases can be
Hi,
> > A two processor SMP machine has been crashing recently, sometimes it
> > manages to Oops before hand. Below is the klogd output with assembly
> > from gdb. The do_generic_file_read+347 Oops occurred once, the dput+77
> > Oops has occurred five times; all five are below.
> >
> > Does
Hi,
> A two processor SMP machine has been crashing recently, sometimes it
> manages to Oops before hand. Below is the klogd output with assembly
> from gdb. The do_generic_file_read+347 Oops occurred once, the dput+77
> Oops has occurred five times; all five are below.
>
> Does anyone recog
Hi,
A two processor SMP machine has been crashing recently, sometimes it
manages to Oops before hand. Below is the klogd output with assembly
from gdb. The do_generic_file_read+347 Oops occurred once, the dput+77
Oops has occurred five times; all five are below.
Does anyone recognise if thes
Hi Keith,
> Your best option is to convert dput+77 back to 8 digit hex and run the
> resulting log through ksymoops. +77/328 is offset 77, the next label
> that klogd knows about is 328 bytes later, ignore the /328. AFAIK
> klogd prints offsets in decimal but check the source code of
> sysklog
Hi,
We've a machine that has been suffering Oops over the last few days
after weeks of stability. I'll post more on that later. My current
problem is a bunch of Oops that klogd has resolved the addresses on.
Problem is, I've just worked out the machine has /boot/System.map as
the wrong map.
G
21 matches
Mail list logo
