Hello,
while booting a latest -net.git kernel on s390x test machine, I've hit this one
below, just in case it was not reported yet:
[...]
[3.317031] qeth 0.0.1000: Outbound TSO not supported on eth0
[3.317123] qeth 0.0.1000: MAC address 02:a1:11:0e:bf:f0 successfully
registered on devic
Am Freitag, 18. Dezember 2015, 19:16:57 schrieb Herbert Xu:
Hi Herbert,
> On Fri, Dec 18, 2015 at 04:49:17PM +0800, Herbert Xu wrote:
> > OK turns out I was looking at the wrong WARN_ON line.
> >
> > This particular bug is a legacy of the geniv construct we have
> > for ablkcipher.
> >
> > It s
On Fri, Dec 18, 2015 at 04:49:17PM +0800, Herbert Xu wrote:
>
> OK turns out I was looking at the wrong WARN_ON line.
>
> This particular bug is a legacy of the geniv construct we have
> for ablkcipher.
>
> It should disappear once we remove geniv which I will do as part
> of the skcipher conver
On Mon, Dec 14, 2015 at 11:45:02PM +0100, Stephan Mueller wrote:
>
> But with the given code, when you remove the bogus mask setting (which in
> turn
> leaves it as 0), the code works flawless.
OK turns out I was looking at the wrong WARN_ON line.
This particular bug is a legacy of the geniv co
On Mon, Dec 14, 2015 at 11:45:02PM +0100, Stephan Mueller wrote:
>
> But with the given code, when you remove the bogus mask setting (which in
> turn
> leaves it as 0), the code works flawless.
Please find out exactly why this would be triggering the warning
because your previous explanation of
Am Montag, 14. Dezember 2015, 20:52:19 schrieb Herbert Xu:
Hi Herbert,
>On Thu, Dec 10, 2015 at 03:14:24AM +0100, Stephan Mueller wrote:
>> Herbert, alg_bind currently blacklists one bit in the mask and type bit
>> array. Shouldn't we instead white-list the allowed bits?
>
>Well a bogus mask shou
On Thu, Dec 10, 2015 at 03:14:24AM +0100, Stephan Mueller wrote:
>
> Herbert, alg_bind currently blacklists one bit in the mask and type bit
> array.
> Shouldn't we instead white-list the allowed bits?
Well a bogus mask shouldn't lead to the warning anyway.
The warning in question is triggered
Am Dienstag, 8. Dezember 2015, 12:12:27 schrieb Dmitry Vyukov:
Hi Dmitry,
>Hello,
>
>The following program triggers a WARNING in crypto_wait_for_test:
>
>// autogenerated by syzkaller (http://github.com/google/syzkaller)
>#include
>#include
>#include
>
>
Hello,
The following program triggers a WARNING in crypto_wait_for_test:
// autogenerated by syzkaller (http://github.com/google/syzkaller)
#include
#include
#include
int main()
{
long r0 = syscall(SYS_mmap, 0x2000ul, 0x1000ul, 0x3ul,
0x32ul, 0xul, 0x0ul
