On Friday, October 14, 2016 05:50:40 PM Andriy Gapon wrote:
> On 14/10/2016 00:39, Lewis Donzis wrote:
> > After upgrading to FreeBSD 11.0 and changing source code to use the new
> > version of “struct smbcmd”, some commands are not working as documented,
> > specifically those that read data.
> >
Patch generally lgtm ... just 1 nit comment:
+ } else {
+ if (sbavail(>so_rcv) >= so->so_rcv.sb_lowat)
+ return 1;
+ }
Collapse the else and the block inside to just make it an `else if`
for less branching.
On
> On Oct 14, 2016, at 9:50 AM, Andriy Gapon wrote:
> Could you please open a bugzilla issue for the bug?
> https://bugs.freebsd.org/bugzilla/
Sure, will do. I was unsure of the effectiveness of that, because I filed a
much more serious report about a different issue a couple
On 14/10/2016 18:11, Michael Gmelin wrote:
> For some history on these changes, please see also [1] and [2] (there
> were a few discussions and the revision was bumped, I also tried to
> get some attention, but not enough it seems).
>
> Given your recent changes to iicbus in HEAD, I think it
On Fri, 14 Oct 2016 17:50:40 +0300
Andriy Gapon wrote:
> On 14/10/2016 00:39, Lewis Donzis wrote:
> > After upgrading to FreeBSD 11.0 and changing source code to use the
> > new version of “struct smbcmd”, some commands are not working as
> > documented, specifically those
On 14/10/2016 00:39, Lewis Donzis wrote:
> After upgrading to FreeBSD 11.0 and changing source code to use the new
> version of “struct smbcmd”, some commands are not working as documented,
> specifically those that read data.
>
> As an example, SMB_READW is documented as returning the word read
On Fri, Oct 14, 2016 at 09:21:52AM +, hartmut.bra...@dlr.de wrote:
> Hi all,
>
> here is the 2nd try taking into account the comments I received. Since I'm
> not familiar with the locking in the sockets area I ask somebody with that
> knowledge to check it before I commit it.
I have only
On Fri, 14 Oct 2016 00:19-0700, Julian Elischer wrote:
> I attempted to add a second partition to an existing FS pool in FreeBSD 10.3
> and the result was a crash..
>
> is there anyone out there with a scratch system (10.3) (or two spare drives)
> who can show me this working?
>
> Does it look
Hi all,
here is the 2nd try taking into account the comments I received. Since I'm not
familiar with the locking in the sockets area I ask somebody with that
knowledge to check it before I commit it.
Thanks,
harti
From: Scott Mitchell [mailto:scott.k.mit...@gmail.com]
Sent: Friday,
Systems I updated to recent CURRENT start crashing spontaneously.
recent crashing system is on
12.0-CURRENT FreeBSD 12.0-CURRENT #11 r307305: Fri Oct 14 08:37:59 CEST 2016
other (no access since it is remote and not accessible until later the day) has
been updated ~ 12 hours ago and it is alos
I have a fix that works and is better and simpler than the previous and will
try to put it together in the next few days.
harti
From: Scott Mitchell [mailto:scott.k.mit...@gmail.com]
Sent: Friday, October 14, 2016 2:16 AM
To: freebsd-current@freebsd.org
Cc: sepher...@gmail.com;
I attempted to add a second partition to an existing FS pool in
FreeBSD 10.3 and the result was a crash..
is there anyone out there with a scratch system (10.3) (or two spare
drives) who can show me this working?
Does it look familiar to anyone?
The drive 'boot0' is being used as the root
12 matches
Mail list logo