From: "Thomas Schmitt" <scdbackup@gmx.net>
To: kernelnewbies@kernelnewbies.org
Cc: ebashinskii@mail.ru, valdis.kletnieks@vt.edu
Subject: Re: Kernel bug tracker
Date: Fri, 03 Sep 2021 13:00:55 +0200 [thread overview]
Message-ID: <888836222857155971@scdbackup.webframe.org> (raw)
In-Reply-To: <1630659351.685242253@f502.i.mail.ru>
Hi,
Adverg Ebashinskii wrote:
> The reason I looked for some bugs is that I’m not
> really interested in driver development and digging into details of a
> specific hardware. So I tried to get into some core subsystems like fs, net,
> cgroups, etc...
I could offer bugs of isofs with explanations and patch proposals:
- isofs: prevent file time rollover after year 2038
Change the return type of function iso_date() from int to time64_t.
- isofs: truncate oversized Rock Ridge names to 255 bytes
Do not discard all bytes of the NM field where the overflow occurs, but
rather append them to the accumulated name before truncating it to exactly
255 bytes.
Map trailing incomplete UTF-8 bytes to '_'.
- isofs: fix Oops with zisofs and large PAGE_SIZE
https://lore.kernel.org/linux-scsi/20201120140633.1673-1-scdbackup@gmx.net/T/#u
(No replies since 2020-11-20. I hope the tester of this patch still
has the machine to confirm that the patch is still good.)
What is obviously missing with my skills is ability to get attention of
kernel developers for isofs and their trust that the proposals don't make
things worse.
As developer of libisofs and libburn i can provide motivations and
facts from that experience. There would be 4 bugs in cdrom and sr to be
fixed, 2 wishlist changes for them, and 2 wishlist changes for isofs.
An example can be seen at
https://lore.kernel.org/linux-scsi/20201006094026.1730-1-scdbackup@gmx.net/T/#u
(My patch proposals were tested with kernels of a year ago. One of them
meanwhile needs rework due to the demise of the .readpages method:
isofs: Give zisofs a .readpages() method for use by mm/readahead
My kernel development machine from then meanwhile has a production job.)
Have a nice day :)
Thomas
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next parent reply other threads:[~2021-09-03 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1630659351.685242253@f502.i.mail.ru>
2021-09-03 11:00 ` Thomas Schmitt [this message]
2021-09-03 15:55 ` Kernel bug tracker Valdis Klētnieks
2021-09-03 16:58 ` Thomas Schmitt
2021-09-05 10:10 ` Re[2]: " Adverg Ebashinskii
2021-09-05 11:48 ` Thomas Schmitt
2021-09-05 12:08 ` Thomas Schmitt
2021-09-06 8:11 ` Re[2]: " Adverg Ebashinskii
2021-09-06 9:04 ` Thomas Schmitt
2021-09-05 11:57 ` Thomas Schmitt
[not found] <1630220663.155756289@f748.i.mail.ru>
2021-08-29 8:50 ` Anatoly Pugachev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=888836222857155971@scdbackup.webframe.org \
--to=scdbackup@gmx.net \
--cc=ebashinskii@mail.ru \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).