On Sun, Sep 30, 2018 at 11:58:02PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:17b57b1883c1 Linux 4.19-rc6
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1672d71140
> kernel config:
On Mon, Oct 01, 2018 at 04:04:42PM +0100, Alan Cox wrote:
> > Systems restricted by LSMs to the point where CAP_SYS_ADMIN is not
> > trusted have exactly the same issues. i.e. there's nobody trusted by
> > the kernel to administer the storage stack, and nobody has defined a
> > workable security
On Mon, Sep 24, 2018 at 06:19:02AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:46c163a036b4 Add linux-next specific files for 20180921
> git tree: linux-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=1283fef140
> kernel
On Mon, Sep 10, 2018 at 09:16:12PM +0530, Souptick Joarder wrote:
> Return type of ext4_page_mkwrite and ext4_filemap_fault are
> changed to use vm_fault_t type.
>
> With this patch all the callers of block_page_mkwrite_return()
> are changed to handle vm_fault_t. So converting the return type
>
On Tue, Sep 25, 2018 at 04:44:03PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:846e8dd47c26 Merge tag 'scsi-fixes' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15c874a140
>
On Wed, Oct 10, 2018 at 04:27:58PM +0200, Arnd Bergmann wrote:
> The two new variables are only used in an #ifdef, so they cause a
> warning without CONFIG_QUOTA:
>
> fs/ext4/super.c: In function 'parse_options':
> fs/ext4/super.c:1977:26: error: unused variable 'grp_qf_name'
>
This is fixed with the following patch.
- Ted
>From c4a928ee604e31354c969b461aa9a6171825096a Mon Sep 17 00:00:00 2001
From: Theodore Ts'o
Date: Tue, 2 Oct 2018 01:34:44 -0400
Subject: [PATCH] ext4: fix argument checking in EXT4_IOC_MOVE_EXT
If
On Tue, Sep 11, 2018 at 01:02:00PM +, mario.limoncie...@dell.com wrote:
> > I tried 9370 and it detects the adapter correctly. IIRC I did the same
> > for 5530 and it worked as well.
>
> Thanks for confirming that. Hopefully the same change can be ported to PD
> controller
> firmware then
On Thu, Aug 30, 2018 at 04:35:21PM -0700, Andrew Morton wrote:
>
> The v1->v2 delta (below) reveals unchangelogged ext4 changes?
Souptick, please don't make unrelated changes in a vm_fault_t patch.
Especially please don't make whitespace changes that will cause
checkpatch.pl to whine about line
On Thu, Sep 20, 2018 at 02:16:40AM +0100, Olof Johansson wrote:
> > But there are too many ways this can go wrong, maybe not now or next
> > week but in five or ten years, when maybe a different kind of person
> > is on the TAB, or maybe external pressure is brought to bear on TAB
> > members.
People can decide who they want to respond to, but I'm going to gently
suggest that before people think about responding to a particular
e-mail, that they do a quick check using "git log --author=xy...@example.com"
then decide how much someone appears to be a member of the community
before
On Wed, Sep 26, 2018 at 05:55:18PM +0300, Дмитрий Леонтьев wrote:
> Or: "Why you should not use "kill switch" option proposed by smdy to
> protest against CoC"
>
> Hello.
>
> I'm neither a great software developer nor a lawyer, but I'm not a
> novice and I'm very annoyed whan I see this:
>
>
On Wed, Sep 26, 2018 at 07:10:55PM +0100, Alan Cox wrote:
> In almost all cases you don't care so you wouldn't use it. In those cases
> where it might matter it's almost always the case that a reader won't
> consume it before it hits the media.
>
> That's why I suggested having an fbarrier() so
On Tue, Sep 25, 2018 at 07:35:11PM +0200, Adam Borowski wrote:
> Isn't this what the snippet for O_TMPFILE in "man 2 open" does?:
>
> char path[PATH_MAX];
> fd = open("/path/to/dir", O_TMPFILE | O_RDWR,
> S_IRUSR |
On Tue, Sep 25, 2018 at 12:41:18PM -0400, Jeff Layton wrote:
> That's all well and good, but still doesn't quite solve the main concern
> with all of this. It's suppose we have this series of events:
>
> open file r/w
> write 1024 bytes to offset 0
>
> read 1024 bytes from offset 0
>
> Open,
On Tue, Sep 25, 2018 at 02:36:45PM +0200, Christoph Conrads wrote:
> The CoC is a political document:
> https://web.archive.org/web/20180924234027/https://twitter.com/coralineada/status/1041465346656530432
...
> Here is the author's post-meritocracy manifesto:
> https://postmeritocracy.org/
On Tue, Sep 25, 2018 at 01:52:57PM -0400, Stephen Smalley wrote:
> On 09/25/2018 01:27 PM, Tong Zhang wrote:
> > Kernel Version: 4.18.5
> >
> > Problem Description:
> >
> > When setting nice value, it is checked by LSM function
> > security_task_setnice().
> > see kernel/sched/core.c:3972
On Tue, Sep 25, 2018 at 08:44:39PM -0400, TongZhang wrote:
> Yes, this is exactly what I am saying.
> A process can change its own name using prctl or /proc/self/comm.
> prctl is protected by security_task_prctl, whereas /proc/self/comm is not
> protected by this LSM hook.
>
> A system admin may
On Thu, Sep 27, 2018 at 08:43:10AM -0400, Jeff Layton wrote:
>
> Basically, the problem (as I see it) is that we can end up evicting
> uncleanable data from the cache before you have a chance to call fsync,
> and that means that the results of a read after a write are not
> completely reliable.
On Tue, Sep 25, 2018 at 07:15:34AM -0400, Jeff Layton wrote:
> Linux has dozens of filesystems and they all behave differently in this
> regard. A catastrophic failure (paradoxically) makes things simpler for
> the fs developer, but even on local filesystems isolated errors can
> occur. It's also
On Tue, Nov 27, 2018 at 10:28:36AM +0100, Jan Kara wrote:
> On Fri 23-11-18 16:30:43, Colin King wrote:
> > From: Colin Ian King
> >
> > There are several lines that are indented too far, clean these
> > up by removing the tabs.
> >
> > Signed-off-by: Colin Ian King
>
> The patch looks good.
On Mon, Nov 26, 2018 at 02:56:32PM +0100, Jan Kara wrote:
> On Fri 23-11-18 16:40:53, Colin King wrote:
> > From: Colin Ian King
> >
> > There is a statement that is indented with spaces, replace it with
> > a tab.
> >
> > Signed-off-by: Colin Ian King
>
> Looks good. You can add:
>
>
On Tue, Nov 27, 2018 at 10:14:53AM +0100, Jan Kara wrote:
> On Mon 26-11-18 11:21:06, Pan Bian wrote:
> > The function frees qf_inode via iput but then pass qf_inode to
> > lockdep_set_quota_inode on the failure path. This may result in a
> > use-after-free bug. The patch frees df_inode only when
On Sat, Dec 08, 2018 at 12:56:29PM +0100, Greg KH wrote:
> A nice step forward would have been if someone could have at least
> _told_ the stable maintainer (i.e. me) that there was such a serious bug
> out there. That didn't happen here and I only found out about it
> accidentally by happening
On Mon, Nov 19, 2018 at 11:31:21AM -0800, Randy Dunlap wrote:
>
> Yes, all of that.
> Having some kind of pstore on x86 would be wonderful.
>
> kexec/kdump used to be an option also. I haven't tried it lately.
Sure, but kexec/kdump won't work to debug a boot failure during early
boot. You
On Wed, Nov 28, 2018 at 03:16:33AM +0300, Andrey Jr. Melnikov wrote:
> Corrupted inodes - always directory, not touched at least year or
> more for writing. Something wrong when updating atime?
We're not sure. The frustrating thing is that it's not reproducing
for me. I run extensive regression
On Wed, Nov 28, 2018 at 04:56:51PM +0100, Rainer Fiebig wrote:
>
> If you still see the errors, at least the Ubuntu-kernel could be ruled out.
My impression is that some of the people reporting problems have been
using stock upstream kernels, so I wasn't really worried about the
Ubuntu kernel
On Wed, Nov 28, 2018 at 08:50:39AM +, Willy Wolff wrote:
> I got a Oops when the hard drive was COMPLETELY full using a ext4 fs.
> After it, any command on the directory where the last write should have
> occurred freezes, while any other directory behave just fine.
Was this true after you
On Mon, Nov 19, 2018 at 08:51:17PM +0530, AIAMUZZ wrote:
> Hi,
>
> I have this nagging and frustrating boot freeze i often face on my
> Deepin OS boot ... Deepin OS i think uses 'journalctl' to record logs
> on its system.
>
> 'journalctl' however seems to record boot logs ONLY for successful
>
[ This pull request was originally intended for 4.19-rc4, but some
testing hiccups delayed my sending this earlier. Given Linus's
comments, I'm not sure whether PULL requests should be going to Linus
or Greg, so I'm sending it to both. -- Ted ]
The following changes since commit
Date:Mon, 26 Feb 2001 22:19:20 -0500
From: Jeremy Jackson <[EMAIL PROTECTED]>
I had written a simple program 10-20 lines C to count pulses at rate
of 1 per second give or take. It turned out that the driver disabled
the UART's generation of interrupts completely for
Date:Fri, 1 Sep 2000 12:47:44 +0200 (MESZ)
From: "Dr. Michael Weller" <[EMAIL PROTECTED]>
Sorry, I've no idea about the ext2 and fs implementation.
However did you read the comment below and convince yourself that 'err' is
always set correctly?
I looked at it and was
From: Russell King <[EMAIL PROTECTED]>
Date: Fri, 1 Sep 2000 16:23:39 +0100 (BST)
At the marked line (! - line 647), what if flip.count is equal to
TTY_FLIPBUF_SIZE? Surely we're writing to a character outside the
flag_buf_ptr array? If that is the case, should we not move this
From: Daniel Phillips <[EMAIL PROTECTED]>
Date:Fri, 01 Sep 2000 20:49:14 +0200
Curiously, this field is measured in 512 byte units, giving a 2TB Ext2
filesize limit. That's starting to look uncomfortably small - I can
easily imagine a single database file wanting to be
Date:Fri, 01 Sep 2000 08:47:04 -0700
From: Stephen Satchell <[EMAIL PROTECTED]>
5) Even better would be to obtain the services of a PR firm used to
dealing with high-tech questions -- if you would like a list of potential
sponsors I can poll the IPG to see who might be
From: Ulrich Drepper <[EMAIL PROTECTED]>
Date:01 Sep 2000 14:52:28 -0700
1st Problem: One signal handler process process-wide
What is handled correctly now is sending signals to the group. Also
that every thread has its mask. But there must be exactly one signal
From: Russell Coker <[EMAIL PROTECTED]>
Date:Mon, 4 Sep 2000 15:42:57 +0200
In test7 the stallion.c serial driver is in the drivers/media/video
directory. This means that it won't compile and that compilation will break
if the Stallion driver is enabled.
Could this
Date:Wed, 6 Sep 2000 01:43:47 +0100 (BST)
From: Alex Buell <[EMAIL PROTECTED]>
> Only, with the former, I get to restart the application everytime it
> croaks, with the latter (modules excluded) I have to reboot. This is
> much more time consuming and means you really have
Date:Mon, 11 Sep 2000 13:08:59 +
From: Pravir Chandra <[EMAIL PROTECTED]>
I've been working to change the implementation of /dev/random over to the
Yarrow-160a algorithm created by Bruce Schneier and John Kelsey. We've been
working on parallel development for Linux and
On Mon, 11 Sep 2000, Jeff V. Merkey wrote:
>
> Thanks Ted. I know, but a kernel debugger is one of those nasty pieaces
> of software that can quickly get out of sync if it's maintained
> separately from the tree -- the speed at which changes occur in Linux
> would render it a very difficult
Date: Mon, 11 Sep 2000 17:51:20 -0600
From: "Jeff V. Merkey" <[EMAIL PROTECTED]>
I support source level in the kernel. Based on Andi Klein's review, I
have grabbed ext2utils and am looking at a minimal int 0x13 interface to
load files into memory. hardest problem here for Linux
Date:Mon, 11 Sep 2000 18:27:30 -0700
From: David Ford <[EMAIL PROTECTED]>
> I've told Linus several times about this problems but he puts out one
> test release after the other without this fixed.
This is kinda important, I run DNS tools which are threaded amongst
Date: Tue, 12 Sep 2000 09:56:12 +
From: Pravir Chandra <[EMAIL PROTECTED]>
i agree that the yarrow generator does place some faith on the crypto
cipher and the accumulator uses a hash, but current /dev/random
places faith on a crc and urandom uses a hash.
No, not true. The
Date:Wed, 13 Sep 2000 01:23:30 +0200 (CEST)
From: Igmar Palsenberg <[EMAIL PROTECTED]>
> No, not true. The mixing into the entropy pool uses a twisted LFSR, but
> all outputs from the pool (to either /dev/random or /dev/urandom)
> filters the output through SHA-1 as a
Date: Tue, 12 Sep 2000 23:37:57 -0700
From: David Ford <[EMAIL PROTECTED]>
> > 4. Boot Time Failures
> >
> > * Use PCI DMA 'lost interrupt' problem with some hw [which ?] (NEC
> >Versa LX with PIIX tuning)
>
> If this is a rare version of the BX/LX that has a
Date:Wed, 13 Sep 2000 08:46:00 +0200
From: Harald Dunkel <[EMAIL PROTECTED]>
How can I submit a bug report to be added to this list?
I *try* to follow bug reports sent to Linux-kernel, but if you want to
be sure, send it directly to me ([EMAIL PROTECTED]).
(And now for the
Date: Tue, 12 Sep 2000 23:55:55 -0700
From: David Ford <[EMAIL PROTECTED]>
Please add 'APM resume returns the machine to the first tty, crashes
X' This appeared w/ test8. If this is intended, I'd be very happy to
know if so and I can write in to xfree86 about it. If not
Date: Wed, 13 Sep 2000 10:03:39 +0200
From: Andries Brouwer <[EMAIL PROTECTED]>
On Wed, Sep 13, 2000 at 01:56:39AM -0400, [EMAIL PROTECTED] wrote:
> 8. Fix Exists But Isnt Merged
...
> 9. To Do
> * Mount of new fs over existing mointpoint should return an error
>
Date:Wed, 13 Sep 2000 12:54:49 +0200 (CEST)
From: Trond Myklebust <[EMAIL PROTECTED]>
Don't forget that 2^20 > 10^6, hence if you really want units of
microseconds, you actually only need to save 3 bytes worth of data per
timestamp.
For the purposes of NFS, however the
Date:Wed, 13 Sep 2000 12:56:22 +0100 (BST)
From: Alan Cox <[EMAIL PROTECTED]>
> suggest a unique identifier for your patch? Humans are usually better
> at picking sensible names than a machine, and in discussions, it is
> better to refer to 'ide-foobar-fix3' than KP7562
Date: Wed, 13 Sep 2000 22:35:10 +0200 (CEST)
From: Trond Myklebust <[EMAIL PROTECTED]>
You might be able to steal a couple of bytes and then rewrite ext2fs
to mask those out from the 'i_generation' field, but it would mean that
you could no longer boot your old 2.2.16 kernel
From: "Albert D. Cahalan" <[EMAIL PROTECTED]>
Date:Wed, 13 Sep 2000 19:20:42 -0400 (EDT)
The ext2 inode has 6 obviously free bytes, 6 that are only used
on filesystems marked as Hurd-type, and 8 that seem to be claimed
by competing security and EA projects. So, being
Date: Thu, 14 Sep 2000 15:09:35 +0200 (CEST)
From: Trond Myklebust <[EMAIL PROTECTED]>
Would it perhaps make sense to use one of these last 'free' fields
as a pointer to an 'inode entension'?
If you still want ext2fs to be able to accommodate new projects and
ideas, then it
Date: Thu, 14 Sep 2000 17:12:35 +0200 (MEST)
From: [EMAIL PROTECTED] (Rogier Wolff)
The "right" way to do this is to have a "this spot is in use, but you
don't understand it" indication for an inode (*). The "expansion ptr"
can then normally point to the directly following inode,
Date: Thu, 14 Sep 2000 17:03:11 +0200 (CEST)
From: Trond Myklebust <[EMAIL PROTECTED]>
For the timestamps, yes, but inode caching will take most of that
hit. After all, the only time stat() reads from disk is when the inode
has completely fallen out of the cache.
For commonly
From: "Mike" <[EMAIL PROTECTED]>
Date:Thu, 14 Sep 2000 20:34:42 +0400
Just have compiled 2.4.0-test8 today...
Nothing interesting
Everything goes the same way as 2 test releases before...
All my devices are detected right, but... :-(
Kernel panic again at the file
Date: Wed, 13 Sep 2000 17:17:01 -0400
From: Jeff Garzik <[EMAIL PROTECTED]>
I ran with the idea, and created the attached patch, against
2.4.0-test8. It converts serial.c to the new PCI API (quite compactly,
I might add) It should be possible with this patch to now hotplug
Date: Fri, 15 Sep 2000 01:06:24 +0200 (MEST)
From: [EMAIL PROTECTED] (Rogier Wolff)
My suggestion is indeed effectivly (almost) doubling the inode size.
However, it provides an upgrade path, where you can double-boot with a
kernel that DOESN"T know about the inodes.
The 2.2
Date: Thu, 30 Nov 2000 17:13:27 -0500 (EST)
From: Alexander Viro <[EMAIL PROTECTED]>
* search for appropriate cylinder group had been taken out of the
ext2_new_inode() into helper functions - find_cg_dir(sb, parent_group) and
find_cg_other(sb, parent_group). Bug caught by
From: "Albert D. Cahalan" <[EMAIL PROTECTED]>
Date:Sat, 2 Dec 2000 17:00:32 -0500 (EST)
> Any programmer who has evolved sufficiently from a scriptie
> should take necessary precautions to check how much data was
> transferred. Those who don't..well, there is still
Date:Sat, 2 Dec 2000 17:18:43 + (GMT)
From: Alan Cox <[EMAIL PROTECTED]>
> This is currently happening with lucent winmodem driver: there's
> modified version of serial.c, and customers are asked to compile it
> and (staticaly-)link it against proprietary code to get
Date: Sat, 2 Dec 2000 18:34:44 -0500 (EST)
From: Alexander Viro <[EMAIL PROTECTED]>
Erm... Not that ignoring the return values was a bright idea, but the
lack of reliable ordered datagram protocol in IP family is not a good
thing. It can be implemented over TCP, but it's a big
Date: Sat, 2 Dec 2000 18:21:26 -0700
From: "Jeff V. Merkey" <[EMAIL PROTECTED]>
Under this argument, it is argued that the engineer who had source
code access "inevitably used" negative knowledge he gained from
his study of the Linux sources. Absent the vague descriptions of
From: "Saber Taylor" <[EMAIL PROTECTED]>
Date:Sun, 03 Dec 2000 05:59:47 -
Well that's the last time I run a devel kernel with a nontest
system. sigh.
Had one directory replaced with a different directory
and also a directory replaced with a file. Possible further
Date: Fri, 8 Dec 2000 13:27:51 -0800 (PST)
From: Linus Torvalds <[EMAIL PROTECTED]>
I didn't have time to do more than just quickly apply the patch and leave
in a hurry, but my Vaio certainly recognized the serial port on the combo
cardbus card I have with this patch. Everything
Date: Fri, 8 Dec 2000 23:41:54 -0800 (PST)
From: Linus Torvalds <[EMAIL PROTECTED]>
This is a problem that many drivers have: when the card is removed, the
driver sees an interrupt (which happens to be the CardBus card removal
interrupt, but the serial driver doesn't know that,
Date: Sat, 9 Dec 2000 10:13:50 -0800 (PST)
From: Linus Torvalds <[EMAIL PROTECTED]>
I checked my VAIO's, and they all have a Ricoh cardbus bridge.
Ted claimed he had a TI1311 or something, I think. So his VAIO is
definitely different from the ones I have. That may be enough of a
Date: Sat, 09 Dec 2000 11:13:59 -0500
From: Jeff Garzik <[EMAIL PROTECTED]>
> Note how the "rs_interrupt()" routine _tries_ to avoid this by having a
> pass counter value, but that logic never triggers because we will loop
> forever in receive_chars(), so the rs_interrupt()
Date:Fri, 29 Sep 2000 19:24:01 +0200
From: Frederic Magniette <[EMAIL PROTECTED]>
We would like to do some operations on a ext2 disk while it is
mounted read-only. The problem is that our operations have no
effects because everithing is cached. Is it possible to shrink
Date:Fri, 29 Sep 2000 17:49:04 -0600
From: "Jeff V. Merkey" <[EMAIL PROTECTED]>
This is going to be a continuing problem for non-Unix file systems like
NTFS and NWFS that rely on the ability to read and write variable length
sector runs.
It's not just non-Unix file
Date:Sat, 30 Sep 2000 04:10:59 +0200
From: Marc Lehmann <[EMAIL PROTECTED]>
Do you really think that explicitly supporting broken distributions
(redhat 7.0 comes with a experimental snapshot of gcc which is neither
binary compatible to 2.95 nor to 3.0, cutting binary
Date: Fri, 29 Sep 2000 22:16:53 -0700 (PDT)
From: Andre Hedrick <[EMAIL PROTECTED]>
Basically you can de-stroke a drive with what you let the OS/FS report.
Once this is done there is no way any FS can get to the stuff beyond what
it knows about.
I'm not sure what you mean by
Date: Thu, 14 Sep 2000 15:45:24 -0700
From: Larry McVoy <[EMAIL PROTECTED]>
I'm going to have to respectfully disagree. First of all, having a flag
day where everyone switches to BK just isn't a realistic expectation,
even if the license wasn't an issue. Things just don't work
Date:Wed, 13 Sep 2000 03:30:39 -0700
From: "David S. Miller" <[EMAIL PROTECTED]>
From: Daniel Quinlan <[EMAIL PROTECTED]>
Date: Wed, 13 Sep 2000 03:18:14 -0700 (PDT)
How exactly does a system to tracking patches and bugs/fixes (not to
mention helping
Date:Wed, 13 Sep 2000 02:27:07 -0700
From: "David S. Miller" <[EMAIL PROTECTED]>
rsync [EMAIL PROTECTED]:/home/torvalds/src/linux \
ftp.kernel.org:/pub/linux/kernel/LIVE/linux
would be the real helper for people like me whose only real issue
now is bothering
From: "Dunlap, Randy" <[EMAIL PROTECTED]>
Date: Wed, 13 Sep 2000 09:17:55 -0700
I appreciate Alan and you doing the kernel Status/TODO lists,
but I think that you ought to simplify it for yourself at
least (not that this would help Linus) by having maintainers
do it instead of
Date: Wed, 13 Sep 2000 17:14:57 +0200 (MEST)
From: [EMAIL PROTECTED] (Rogier Wolff)
Today we fixed a problem in a driver we maintain here. We should've
gone ahead and generate the patch and queued it for Linus. However,
in reality we'd like the complaining customer to test the
Date:Fri, 06 Oct 2000 12:01:34 -0500
From: Jeff Dike <[EMAIL PROTECTED]>
tty_register_devfs and tty_unregister_devfs both declare "struct tty_struct" locals.
According to gdb:
(gdb) p sizeof(struct tty_struct)
$20 = 3084
This eats up most of a 4K page, and on UML
Date: Tue, 24 Oct 2000 11:14:13 +0200
From: octave klaba <[EMAIL PROTECTED]>
> Can you actually give me some details of how your system "crashed"? It
> certainly shouldn't have. Kermit will sometimes hang waiting for the
> terminal to flush if it's enabled hardware flow control
Date:Fri, 15 Dec 2000 01:09:29 + (GMT)
From: Alan Cox <[EMAIL PROTECTED]>
> > oWe tell vendors to build RPMv3 , glibc 2.1.x
> Curious HOW do you tell vendors??
When they ask. More usefully Dan Quinlann and most vendors put together a
recommended set of
Date:Mon, 18 Dec 2000 21:38:01 +0100
From: Jamie Lokier <[EMAIL PROTECTED]>
David Schwartz wrote:
> The code does its best to estimate how much actual entropy it is gathering.
A potential weakness. The entropy estimator can be manipulated by
feeding data which looks
Date: Tue, 19 Dec 2000 12:49:48 +0100
From: Kurt Garloff <[EMAIL PROTECTED]>
On Mon, Dec 18, 2000 at 04:33:13PM -0500, Theodore Y. Ts'o wrote:
> Note that writing to /dev/random does *not* update the entropy estimate,
> for this very reason. The assumption is
Date: Wed, 1 Nov 2000 09:46:19 -0500
From: [EMAIL PROTECTED]
On Mon, Oct 30, 2000 at 05:14:34PM +0100, Martin Dalecki wrote:
> Of corse right! BTW. There are tons of places where log2 is calculated
> explicitly in kernel which should be replaced with the corresponding
> built
Date:Thu, 02 Nov 2000 12:31:51 -0700
From: Tim Riker <[EMAIL PROTECTED]>
Me or Alan? I did not mean this as a dig. I feel strongly that one
should have the choice here. I do not choose to enforce my beliefs on
anyone else. I am suggesting only that others should provide
Date: Thu, 02 Nov 2000 13:53:55 -0700
From: Tim Riker <[EMAIL PROTECTED]>
As is being discussed here, C99 has some replacements to the gcc syntax
the kernel uses. I believe the C99 syntax will win in the near future,
and thus the gcc syntax will have to be removed at some point.
Date:Fri, 03 Nov 2000 14:44:17 -0500
From: [EMAIL PROTECTED]
My problem is that pthread_create (glibc 2.1.3, kernel 2.2.17 i686) is
failing because, deep inside glibc somewhere, nanosleep() is returning
EINTR.
Sounds like it might be a bug in pthread_create although
Date:Mon, 6 Nov 2000 09:13:25 -0500 (EST)
From: George Talbot <[EMAIL PROTECTED]>
I respectfully disagree that programs which don't surround some of the
most common system calls with
do
{
rv = __some_system_call__(...);
}
From: Ulrich Drepper <[EMAIL PROTECTED]>
Date: 06 Nov 2000 10:50:37 -0800
> Arguably though the bug is in glibc, in that if it's using signals
> behinds the scenes, it should have passed SA_RESTART to sigaction.
Why are you talking such a nonsense?
The claim was made that
Date:Thu, 9 Nov 2000 13:39:04 + (GMT)
From: Paul Jakma <[EMAIL PROTECTED]>
I actually think Linus has been too loose/vague on modules. The
official COPYING txt file in the tree contains an exception on linking
to the kernel using syscalls from linus and the GPL.
Date:Thu, 09 Nov 2000 08:43:14 -0500
From: Michael Rothwell <[EMAIL PROTECTED]>
And how would a hypothetical Advanced Linux Kernel Project be different?
Set aside the GKHI and the issue of binary-only hook modules; how would
an "enterprise" fork be any different than RT or
Date:Wed, 08 Nov 2000 16:35:33 -0500
From: Michael Rothwell <[EMAIL PROTECTED]>
Sounds great; unfortunately, the core group has spoken out against a
modular kernel.
This is true; that's because a modular kernel means that interfaces have
to be frozen in time, usually
Date: Thu, 9 Nov 2000 14:26:33 + (GMT)
From: Alan Cox <[EMAIL PROTECTED]>
> Actually, he's been quite specific. It's ok to have binary modules as
> long as they conform to the interface defined in /proc/ksyms.
What is completely unclear is if he has the authority to say
From: [EMAIL PROTECTED]
Date:Fri, 10 Nov 2000 11:41:09 +
It has the potential to to make patches easier to re-work for different
kernel versions, and to enable development maintence and fixing of the
patch to be done independently of a kernel build. And it also has the
Date: Fri, 10 Nov 2000 10:36:31 -0800
From: "Matt D. Robinson" <[EMAIL PROTECTED]>
As soon as I finish writing raw write disk routines (not using kiobufs),
we can _maybe_ get LKCD accepted one of these days, especially now that we
don't have to build 'lcrash' against a kernel
On Sat, Mar 24, 2018 at 03:28:24PM +0800, zhenwei.pi wrote:
> "mark_unwritten" in comment and "unwritten" in variable
> argument lists is mismatch.
>
> Signed-off-by: zhenwei.pi
Applied, thanks.
- Ted
On Tue, Mar 27, 2018 at 04:51:08PM +0300, Ilya Smith wrote:
> > /dev/[u]random is not sufficient?
>
> Using /dev/[u]random makes 3 syscalls - open, read, close. This is a
> performance
> issue.
You may want to take a look at the getrandom(2) system call, which is
the recommended way getting
FYI, your patch set doesn't even compile for me without these fixups.
I'm not sure why you were trying to declare inline functions in a
header file without the function body?
- Ted
diff --git a/fs/nova/balloc.c b/fs/nova/balloc.c
index
On Wed, Mar 21, 2018 at 08:40:32AM +0100, Christoph Hellwig wrote:
> The big change is that random_read_wait and random_write_wait are merged
> into a single waitqueue that uses keyed wakeups. Because wait_event_*
> doesn't know about that this will lead to occassional spurious wakeups
> in
On Thu, Mar 29, 2018 at 02:35:44PM -0400, Stephen Smalley wrote:
> >
> > broke a longstanding assumption by SELinux that it could call getxattr with
> > a NULL buffer and 0 size to probe whether the filesystem supports the
> > security xattrs at mount time.
> >
> > Options for fixing:
> > -
On Thu, Mar 15, 2018 at 09:38:29PM +0100, Arnd Bergmann wrote:
>
> You could also have a resolution of less than a nanosecond. Note
> that today, the file time stamps generated by the kernel are in
> jiffies resolution, so at best one millisecond. However, most modern
> file systems go with the
301 - 400 of 886 matches
Mail list logo
