linux-kernel - Re: Google Summer-of-Code 2023

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAM9d7ci_1Luc-VKPztNuw1seBA4akB8_2s4uJ5MaROuUtQUFWg@mail.gmail.com>
Date:   Mon, 27 Mar 2023 19:03:44 -0700
From:   Namhyung Kim <namhyung@...nel.org>
To:     Ian Rogers <irogers@...gle.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-perf-users <linux-perf-users@...r.kernel.org>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        paranlee <p4ranlee@...il.com>,
        Madhu patel <patelmadhu06@...il.com>,
        Anup Sharma <anupnewsmail@...il.com>,
        Lukas Molleman <lukas.molleman@...il.com>,
        n2 h9 <n2h9z4@...il.com>
Subject: Re: Google Summer-of-Code 2023

On Mon, Mar 27, 2023 at 7:00 PM Namhyung Kim <namhyung@...nel.org> wrote:
>
> Hello,
>
> On Mon, Mar 27, 2023 at 3:01 PM Ian Rogers <irogers@...gle.com> wrote:
> >
> > On Mon, Mar 27, 2023 at 2:22 PM Ian Rogers <irogers@...gle.com> wrote:
> > >
> > > On Mon, Mar 13, 2023 at 9:38 AM Ian Rogers <irogers@...gle.com> wrote:
> > > >
> > > > On Wed, Feb 22, 2023 at 7:58 PM Ian Rogers <irogers@...gle.com> wrote:
> > > > >
> > > > > The Linux Foundation was selected as a GSoC organization for 2023!
> > > > > https://summerofcode.withgoogle.com/programs/2023/organizations/the-linux-foundation
> > > > >
> > > > > This means we're looking for contributors until March 19th:
> > > > > https://developers.google.com/open-source/gsoc/timeline
> > > >
> > > > A reminder of the GSoC timeline. Applications open in a week;
> > > >
> > > > * February 22 - March 19
> > > > Potential GSoC contributors discuss application ideas with mentoring
> > > > organizations
> > > >
> > > > * March 20 - 18:00 UTC
> > > > GSoC contributor application period begins
> > > >
> > > > * April 4 - 18:00 UTC
> > > > GSoC contributor application deadline
> > > >
> > > > Thanks,
> > > > Ian
> > >
> > > A reminder that the application period closes in just over a week:
> > > https://developers.google.com/open-source/gsoc/timeline
> > > April 4 - 18:00 UTC
> > > GSoC contributor application deadline
> > >
> > > Thanks,
> > > Ian
> >
> > If you are looking for ideas on how to write a good proposal, PSF has
> > a collection of previously accepted proposals:
> > https://blogs.python-gsoc.org/en/
> >
> > You can also see the final report of Riccardo Mancini:
> > https://lore.kernel.org/lkml/3c4f8dd64d07373d876990ceb16e469b4029363f.camel@gmail.com/
>
> I have a proposal about the build without libtraceevent.
> Now it disables many perf commands if it doesn't have the
> library.  But part of sub-commands would work without it.
>
> For example, perf lock contention has two different modes
> one is to use tracepoints (using the libtraceevent) and
> the other is just use BPF.  The latter should work require
> anything from the libtraceevent so we can enable such
> usecase.
>
> Others like perf sched, kmem and so on might want to run
> only record part like in a small embedded machine (without
> libtraceevent).  Then we can copy the saved data to a host
> and run the report or other sub-commands to analyze the
> data (again, using libtraceevent).

Please let me know, if anyone is interested. :)

Thanks,
Namhyung