On Wed, Jan 16, 2019 at 11:52:37AM +0100, Stefan Sperling wrote:
> On Wed, Jan 16, 2019 at 11:20:43AM +0100, Stefan Sperling wrote:
> > On Tue, Jan 15, 2019 at 04:36:18PM -0800, Mike Larkin wrote:
> > > I have th USB bwfm(4), and I don't see anything different in ifconfig
> > > bwfm0.
> > >
> > >
On Wed, Jan 16, 2019 at 09:17:33PM +0100, Anton Lindqvist wrote:
> + idx = kd->kd_buf[0];
> + if (idx * 4 + 4 + 1 >= kd->kd_nmemb)
> + return;
> +
> + kd->kd_buf[idx * 4 + 1] = type;
> + kd->kd_buf[idx * 4 + 2] = arg1;
> + kd->kd_buf[idx * 4 + 3] = arg2;
> + kd->
Hi,
This diff add supports for an additional trace mode to kcov where
comparison instructions and switch statements can be traced. The actual
comparison operands ends up in the coverage buffer, with some additional
data. See the manual bits for further info. This mode will generate even
more useful
On 2019/01/16 19:09, Otto Moerbeek wrote:
> On Wed, Jan 16, 2019 at 01:25:25PM +, Stuart Henderson wrote:
>
> > On 2019/01/04 08:09, Otto Moerbeek wrote:
> > > On Thu, Dec 27, 2018 at 09:39:56AM +0100, Otto Moerbeek wrote:
> > >
> > > >
> > > > Very little feedback so far. This diff can only
On Wed, Jan 16, 2019 at 01:25:25PM +, Stuart Henderson wrote:
> On 2019/01/04 08:09, Otto Moerbeek wrote:
> > On Thu, Dec 27, 2018 at 09:39:56AM +0100, Otto Moerbeek wrote:
> >
> > >
> > > Very little feedback so far. This diff can only give me valid feedback
> > > if the coverage of systems
On Wed, Jan 16, 2019 at 06:14:49PM +0100, Anton Lindqvist wrote:
> Comments? OK?
OK bluhm@
> Index: dev/kcov.c
> ===
> RCS file: /cvs/src/sys/dev/kcov.c,v
> retrieving revision 1.9
> diff -u -p -r1.9 kcov.c
> --- dev/kcov.c3
Hi,
When a kcov fd is in an enabled state, disallow mmap() calls using the
same fd. Sometimes, syzkaller manages to create a device node using
mknod() with major=22 and minor=X where X maps to an already open kcov
fd in the current process; it then mmap() the kcov coverage buffer which
is used as i
On 2019/01/04 08:09, Otto Moerbeek wrote:
> On Thu, Dec 27, 2018 at 09:39:56AM +0100, Otto Moerbeek wrote:
>
> >
> > Very little feedback so far. This diff can only give me valid feedback
> > if the coverage of systems and use cases is wide. If I do not get
> > more feedback, I have to base my d
Here is an attempt to make video(1) work with the modesetting driver.
See https://marc.info/?l=openbsd-bugs&m=152231686416039&w=2
The general idea:
If there is no common encoding for input (device) and output (Xv), the
encoding is converted to something supported by the output.
No conversion is do
On Wed, Jan 16, 2019 at 11:20:43AM +0100, Stefan Sperling wrote:
> On Tue, Jan 15, 2019 at 04:36:18PM -0800, Mike Larkin wrote:
> > I have th USB bwfm(4), and I don't see anything different in ifconfig bwfm0.
> >
> > The hotel wifi is only 11g though... Would I see anything different here?
>
> Yo
On Tue, Jan 15, 2019 at 04:36:18PM -0800, Mike Larkin wrote:
> I have th USB bwfm(4), and I don't see anything different in ifconfig bwfm0.
>
> The hotel wifi is only 11g though... Would I see anything different here?
You should see changes occuring on this line:
media: IEEE802.11 autoselect (
On Wed, Jan 16 2019 11:00:04 +0100, Ingo Schwarze wrote:
> Lauri Tirkkonen wrote on Mon, Jan 07, 2019 at 08:13:09PM +0200:
>
> > Hi, it seems install(1) has a race condition: in create_newfile, it
> > first unlinks the target file and then tries to open it with
> > O_CREAT|O_EXCL.
> >
> > Normall
Hi,
Lauri Tirkkonen wrote on Mon, Jan 07, 2019 at 08:13:09PM +0200:
> Hi, it seems install(1) has a race condition: in create_newfile, it
> first unlinks the target file and then tries to open it with
> O_CREAT|O_EXCL.
>
> Normally this would not be a problem,
A race condition is almost always
13 matches
Mail list logo
