linux-kernel - Re: Maintainers / Kernel Summit 2021 planning kick-off

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210618184545.33ea3d47@coco.lan>
Date:   Fri, 18 Jun 2021 18:45:45 +0200
From:   Mauro Carvalho Chehab <mchehab@...nel.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     Steven Rostedt <rostedt@...dmis.org>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        James Bottomley <James.Bottomley@...senpartnership.com>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>,
        Shuah Khan <skhan@...uxfoundation.org>,
        Konstantin Ryabitsev <konstantin@...uxfoundation.org>,
        "Enrico Weigelt, metux IT consult" <lkml@...ux.net>,
        David Hildenbrand <david@...hat.com>, Greg KH <greg@...ah.com>,
        Christoph Lameter <cl@...two.de>,
        Theodore Ts'o <tytso@....edu>, Jiri Kosina <jikos@...nel.org>,
        ksummit@...ts.linux.dev,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-block@...r.kernel.org,
        Linux FS Devel <linux-fsdevel@...r.kernel.org>,
        Linux MM <linux-mm@...ck.org>, netdev <netdev@...r.kernel.org>,
        Linux-Arch <linux-arch@...r.kernel.org>,
        Linux API <linux-api@...r.kernel.org>
Subject: Re: Maintainers / Kernel Summit 2021 planning kick-off

Em Fri, 18 Jun 2021 16:58:29 +0100
Mark Brown <broonie@...nel.org> escreveu:

> On Fri, Jun 18, 2021 at 10:32:14AM -0400, Steven Rostedt wrote:
> > On Fri, 18 Jun 2021 16:28:02 +0200
> > Geert Uytterhoeven <geert@...ux-m68k.org> wrote:  
> 
> > > What about letting people use the personal mic they're already
> > > carrying, i.e. a phone?  
> 
> > Interesting idea.  
> 
> > I wonder how well that would work in practice. Are all phones good
> > enough to prevent echo?  
> 
> Unless you get the latency for the WebRTC<->in room speaker down lower
> than I'd expect it to be I'd expect echo cancellation to have fun,
> though beam forming might reject a lot of in room noise including that -
> higher end modern phones are astonishingly good at this stuff.  I'd not
> trust it to work reliably for all attendees though, it's the sort of
> thing where you'll get lots of per device variation.

The local audience should be listening to the in-room audio, in order
to avoid echo. Also, all local mics should be muted, if someone is 
speaking from a remote location. 

Yet, echo is unavoidable if a remote participant is speaking while 
listening to the audio without headphones. If this ever happens, I
guess the moderator should cut the remote audio and ask the remote
participant to lower their speakers or use a headphone.


Thanks,
Mauro