On Mon, 14 Oct 2024 at 14:51, Andrey Konovalov <andreyknvl@xxxxxxxxx> wrote: > > On Mon, Oct 14, 2024 at 10:08 AM Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > > > > On Sun, 13 Oct 2024 at 00:55, <andrey.konovalov@xxxxxxxxx> wrote: > > > > > > From: Andrey Konovalov <andreyknvl@xxxxxxxxx> > > > > > > Add links to the Bugzilla component that's used to track KASAN and KCOV > > > issues. > > > > > > Signed-off-by: Andrey Konovalov <andreyknvl@xxxxxxxxx> > > > --- > > > MAINTAINERS | 2 ++ > > > 1 file changed, 2 insertions(+) > > > > > > diff --git a/MAINTAINERS b/MAINTAINERS > > > index 7ad507f49324a..c9b6fc55f84a6 100644 > > > --- a/MAINTAINERS > > > +++ b/MAINTAINERS > > > @@ -12242,6 +12242,7 @@ R: Dmitry Vyukov <dvyukov@xxxxxxxxxx> > > > R: Vincenzo Frascino <vincenzo.frascino@xxxxxxx> > > > L: kasan-dev@xxxxxxxxxxxxxxxx > > > S: Maintained > > > +B: https://bugzilla.kernel.org/buglist.cgi?component=Sanitizers&product=Memory%20Management > > > > Do we want a link to buglist.cgi, or to enter_bug.cgi, or both? 🤔 > > I think buglist.cgi makes more sense - people can check the list of > existing bugs before filing a new one. Finding a link to the right > enter_bug.cgi page once you know the component name should not be hard > (but IMO Bugzilla should just provide that link when viewing bugs for > a component). then Acked-by: Dmitry Vyukov <dvyukov@xxxxxxxxxx>
